I have Windows Server 2008 Routing and Remote Access set up as a NAT server. Clients drop occasional packets, and the server gives Destination Host Unreachable when I ping. I believe I have narrowed this problem down to the routing tables. It seems as though some old configurations are stuck in the Persistent Routes, and causing packet loss. I have restarted the server, but the persistent routes are still listed.
My network is configured like this:
Public IP
T1
10.8.1.1
|
10.8.1.2
Adtran TA600 Router
172.16.1.254
|
172.16.1.1
Windows Server 2008
192.168.1.2
|
192.168.1.x
Clients
This is what happens when I ping from the server:
ping google.com -n 10
Pinging google.com [209.85.171.100] with 32 bytes of data:
Reply from 192.168.1.2: Destination host unreachable.
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=93msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=95msTTL=244
Ping statistics for 209.85.171.100: Packets: Sent = 10,
Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 93ms, Maximum = 95ms, Average = 94ms
Notice the first reply, "Reply from 192.168.1.2: Destination host unreachable."
It looks like instead of using the external IP address to find google, it's trying the internal IP address.
My network is configured like this:
Public IP
T1
10.8.1.1
|
10.8.1.2
Adtran TA600 Router
172.16.1.254
|
172.16.1.1
Windows Server 2008
192.168.1.2
|
192.168.1.x
Clients
This is what happens when I ping from the server:
ping google.com -n 10
Pinging google.com [209.85.171.100] with 32 bytes of data:
Reply from 192.168.1.2: Destination host unreachable.
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=93msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=94msTTL=244
Reply from 209.85.171.100: bytes=32time=95msTTL=244
Ping statistics for 209.85.171.100: Packets: Sent = 10,
Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 93ms, Maximum = 95ms, Average = 94ms
Notice the first reply, "Reply from 192.168.1.2: Destination host unreachable."
It looks like instead of using the external IP address to find google, it's trying the internal IP address.