- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
05-14-2017 06:30 AM
Hi All,
I've one inquiry where the client used to have an issue where the GP users can reach the LAN users but not vice versa.
Users in LAN and GP are on the same zone (Trust) but only GP can ping the LAN.
The tunnel of the GP doesn't have an IP address by default, I've tried to add an IP address for the tunnel but its still not working.
Nothing is denied in the traffic logs also and since they are on the same zone everything should be allowed.
The traffic logs showing the end reason as 'Aged-out'.
Anybody have an idea about this?
Regards,
Sharief
05-14-2017 07:04 AM - edited 05-14-2017 07:04 AM
Hi,
Ping always will show you "aged-out" as it doesn't use any port and it is not even TCP or UDP protocol.
Can you make sure that the host you are trying to ping is simply responding for ping requests as well as try to initiate any other traffic from LAN > GP (web, ssl etc).
05-22-2017 03:01 AM
Hi @TranceforLife,
I tried the same setup in my lab with disabling the windows firewalls and everything was pingable.
It might be some kind of antivirus on the client machine that is blocking the ping request.
Thanks for your help.
Regards,
Sharief
05-22-2017 03:43 AM
Hence l did ask you to initiate any other traffic 😉
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!