Topics > VPN > FAQ ID # 84

FAQ ID # 84
Last Update : 2012/02/22
Rating : Not Rated
Send FAQ by E-mail
Add to favorites
Print this FAQ

Social Bookmark this Article :

Question / Issue
Unable to ping through VPN

Answer / Solution

I am unable to ping devices other than the LAN-Cell after a VPN tunnel is established.

This can be caused by several issues:

  • Make sure that the addressing for the "local" network in the VPN network policy includes the IP addresses of the devices you need to communicate with.  A common error is to set the local network type to "subnet" but not give a correct starting IP address and subnet mask.  For the entire class-C subnet, the last octet of the starting address would be .0 and the subnet would be  This same addressing scheme must be used on your other VPN end-point as the "remote" VPN network address.

  • Make sure that all devices attached to the LAN-side of the LAN-Cell have the correct IP address, subnet and default gateway values set.  The default gateway will be the LAN IP address of the LAN-Cell in most cases.  If this value is not set correctly, then you may be able to ping "peer-to-peer" among LAN-attached devices, but they will not be able to properly respond to pings sent through the VPN tunnel.

  • Check the LAN-Cell's firewall settings to ensure that the necessary traffic is permitted through the VPN.  If your other VPN end-point (including stand-alone PCs) includes firewall functionality, ensure that these devices also permit the necessary traffic through the VPN tunnel.
  • If the LAN-Cell's WAN interface has a private IP address (e.g. 10.x.x.x), you may need to enble NAT-Traversal (NAT-T) on both the LAN-Cell and the other VPN end-point.

Direct Link to This FAQ

VPN GreenBow XP ICMP ping traffic response respond connect tunnel devices PLC NAT private IP
How would you rate this article?



Back to Top