The topology is as follows:
Linux as a router
Windows Server 2003 as a router
Ping test | IP Address from | Linux | Windows |
Client to Router’s internal interface | 20.10 to 20.254 | Reply from 192.168.20.254: bytes=32 time<10ms TTL=64 | Reply from 192.168.20.254: bytes=32 time<10ms TTL=128 |
Client to Router’s external interface | 20.10 to 30.254 | Reply from 192.168.30.254: bytes=32 time<10ms TTL=64 | Reply from 192.168.30.254: bytes=32 time<10ms TTL=128 |
Client to Server | 20.10 to 30.10 | Reply from 192.168.30.10: bytes=32 time<10ms TTL=127 | Request timed out |
Server to Router’s external interface | 30.10 to 30.254 | Reply from 192.168.30.254: bytes=32 time=10ms TTL=64 | Reply from 192.168.30.254: bytes=32 time<10ms TTL=128 |
Server to Router’s internal interface | 30.10 to 20.254 | Reply from 192.168.20.254: bytes=32 time<10ms TTL=64 | Reply from 192.168.20.254: bytes=32 time<10ms TTL=128 |
Server to Client | 30.10 to 20.10 | Reply from 192.168.20.10: bytes=32 time<10ms TTL=127 | Request timed out |
C:\>tracert 192.168.30.10Tracing route to WIN2KSVR-01 [192.168.30.10]over a maximum of 30 hops:1 <10 ms <10 ms <10 ms 192.168.20.2542 <10 ms <10 ms <10 ms WIN2KSVR-01 [192.168.30.10]
Trace complete. C:\> |
C:\>tracert 192.168.30.10Tracing route to 192.168.30.10 over a maximum of 30 hops1 * * * Request timed out.2 * * * Request timed out.3 * * * Request timed out. | ||
Routing | [cpmodule]# netstat -nrKernel IP routing tableDestination Gateway Genmask Flags MSS Window irtt Iface192.168.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.20.254 0.0.0.0 UG 0 0 0 eth0 [cpmodule]# |
C:\>netstat -nrIPv4 Route Table==================================================================Interface List0x1 ……………………… MS TCP Loopback interface
0x10003 …08 00 27 07 88 b7 …… AMD PCNET Family PCI Ethernet Adapter 0x10004 …08 00 27 21 58 df …… AMD PCNET Family PCI Ethernet Adapter #3 ================================================================== ================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.20.0 255.255.255.0 192.168.20.254 192.168.20.254 20 192.168.20.254 255.255.255.255 127.0.0.1 127.0.0.1 20 192.168.20.255 255.255.255.255 192.168.20.254 192.168.20.254 20 192.168.30.0 255.255.255.0 192.168.30.254 192.168.30.254 20 192.168.30.254 255.255.255.255 127.0.0.1 127.0.0.1 20 192.168.30.255 255.255.255.255 192.168.30.254 192.168.30.254 20 224.0.0.0 240.0.0.0 192.168.20.254 192.168.20.254 20 224.0.0.0 240.0.0.0 192.168.30.254 192.168.30.254 20 255.255.255.255 255.255.255.255 192.168.20.254 192.168.20.254 1 255.255.255.255 255.255.255.255 192.168.30.254 192.168.30.254 1 =========================================================================== Persistent Routes: None |
SUMMARY
I’m not sure how come windows unable to route the ICMP traffic even though the route is there. Linux has no issue to route this traffic. Seems like we have a winner here J
UPDATE [Apr 9, 2012]
I’ve asked around at the following forum to get help on this issue.
Windows 2003 server can’t route network traffic?
http://forums.techarena.in/windows-server-help/1460989.htm