06-28-2012 11:47 AM
I have configured a VPN tunnel between two remote locations using static IP addresses on two RV042 routers. The tunnel seems to work but the problem is that when the two hosts attempt to ping each other only one can successfully ping. One PC with IP address 192.168.1.100 can ping across the network but the second PC with IP address 192.168.2.100 cannot. These are laptops seperate from the intranet used to test the tunnel. Someone had suggested NAT may be the issue so I enabled NAT Transversal on the routers but still no luck. The following is the results from a ping test.
PC 1
ping 192.168.2.1
Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time=116ms TTL=63
Reply from 192.168.2.1: bytes=32 time=123ms TTL=63
Reply from 192.168.2.1: bytes=32 time=127ms TTL=63
Reply from 192.168.2.1: bytes=32 time=131ms TTL=63
Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 116ms, Maximum = 131ms, Average = 124ms
ping 192.168.2.100
Pinging 192.168.2.100 with 32 bytes of data:
Reply from 192.168.2.100: bytes=32 time=138ms TTL=126
Reply from 192.168.2.100: bytes=32 time=133ms TTL=126
Reply from 192.168.2.100: bytes=32 time=135ms TTL=126
Reply from 192.168.2.100: bytes=32 time=142ms TTL=126
Ping statistics for 192.168.2.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 133ms, Maximum = 142ms, Average = 137ms
PC 2
ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=200ms TTL=63
Reply from 192.168.1.1: bytes=32 time=203ms TTL=63
Reply from 192.168.1.1: bytes=32 time=177ms TTL=63
Reply from 192.168.1.1: bytes=32 time=97ms TTL=63
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 203ms, Average = 169ms
ping 192.168.1.100
Pinging 192.168.1.100 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Anyone has any clue as to why this is occurring?
06-30-2012 04:22 PM
Since PC2 can ping the remote router's LAN IP 192.168.1.1, it showed the tunnel is up.
The ping failure from 192.168.2.100 to 192.168.1.100 could be caused by the firewall running on 192.168.1.100.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide