HiWe have an odd issue which I am struggling to explain.From any of the core windows servers within our organisation we do not get any results when doing a tracertserver is windows 2003r2 sp2the output isTracing routeto XXXX [10.33.0.29]over a maximum of 30 hopsPathping returns even less informationPing returns a time and no packet loss is seenIp details of the server doing the tracert IP 10.36.1.104Subnet 255.255.0.0Default Gateway 10.36.1.254 Active Routes:Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.36.1.254 10.36.1.104 10 10.36.0.0 255.255.0.0 10.36.1.104 10.36.1.104 10 10.36.1.104 255.255.255.255 127.0.0.1 127.0.0.1 10 10.255.255.255 255.255.255.255 10.36.1.104 10.36.1.104 10 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 240.0.0.0 10.36.1.104 10.36.1.104 10 255.255.255.255 255.255.255.255 10.36.1.104 10.36.1.104 1Default Gateway: 10.36.1.254===========================================================================Persistent Routes: None I have talked to our comms guys and the tracert works for the switches that these servers are plugged into. There are also no firewalls in the wayIf possible can someone point me in the right directionThanks in advancePaul

Hello, Thanks for your post here. From the description, when you TRACERT an IP address all nodes return "Request timed out" error. Am I right? Could you please provide more information for investigations? 1. What does the network topology look like? How many hops between the local network segment and the 10.33.0.0/16? 2. How it works if you manually PING the every node such as 10.36.1.254 (local gateway), remote gateway (10.33.0.254?) and the 10.33.0.29 (remote device)? 3. Please try to capture the network trace on the server identify what happens on the ICMP requests. You can get the network monitor from the following link and install it on the SBS server. Download the NetMon3.3 from the following link: http://www.microsoft.com/downloads/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en 1) Install the network monitor on the server. 2) Start the capture and try to TRACERT the remote client. 2) Once all 30 nodes returns time out, stop the captures and save the network trace files to verify what happen on the ICMP requests. You can also send the trace log to me at v-mileli@microsoft.com for further investigation. If you have any questions or concerns, please do not hesitate to let me know.

HiThis is teh info requested above I have also put it into the mail with the capture. from PC to server to show hops C:\Program Files\Support Tools>tracert serverXXX Tracing route to serverXXX [10.36.2.16]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.33.0.254 2 <1 ms <1 ms <1 ms 192.168.22.217 3 2 ms <1 ms <1 ms 192.168.22.202 4 1 ms 1 ms 1 ms serverXXX [10.36.2.16] Trace complete. C:\Documents and Settings\Administrator>ping 10.36.1.254 Pinging 10.36.1.254 with 32 bytes of data: Reply from 10.36.1.254: bytes=32 time<1ms TTL=255Reply from 10.36.1.254: bytes=32 time=5ms TTL=255Reply from 10.36.1.254: bytes=32 time<1ms TTL=255Reply from 10.36.1.254: bytes=32 time<1ms TTL=255 Ping statistics for 10.36.1.254: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 5ms, Average = 1ms C:\Documents and Settings\Administrator>ping 192.168.22. Pinging 192.168.22.202 with 32 bytes of data: Reply from 192.168.22.202: bytes=32 time=1ms TTL=255Reply from 192.168.22.202: bytes=32 time=2ms TTL=255Reply from 192.168.22.202: bytes=32 time=2ms TTL=255Reply from 192.168.22.202: bytes=32 time=2ms TTL=255 Ping statistics for 192.168.22.202: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 2ms, Average = 1ms C:\Documents and Settings\Administrator>ping 192.168.22. Pinging 192.168.22.217 with 32 bytes of data: Reply from 192.168.22.217: bytes=32 time=1ms TTL=254Reply from 192.168.22.217: bytes=32 time=1ms TTL=254Reply from 192.168.22.217: bytes=32 time=1ms TTL=254Reply from 192.168.22.217: bytes=32 time<1ms TTL=254 Ping statistics for 192.168.22.217: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms C:\Documents and Settings\Administrator>ping 10.33.0.254 Pinging 10.33.0.254 with 32 bytes of data: Reply from 10.33.0.254: bytes=32 time=5ms TTL=253Reply from 10.33.0.254: bytes=32 time=2ms TTL=253Reply from 10.33.0.254: bytes=32 time=6ms TTL=253Reply from 10.33.0.254: bytes=32 time=1ms TTL=253 Ping statistics for 10.33.0.254: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 6ms, Average = 3ms C:\Documents and Settings\Administrator>ping 10.33.0.29 Pinging 10.33.0.29 with 32 bytes of data: Reply from 10.33.0.29: bytes=32 time=3ms TTL=125Reply from 10.33.0.29: bytes=32 time=3ms TTL=125Reply from 10.33.0.29: bytes=32 time=2ms TTL=125Reply from 10.33.0.29: bytes=32 time=7ms TTL=125 Ping statistics for 10.33.0.29: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 2ms, Maximum = 7ms, Average = 3msThanksPaul

Hello Paul, Thanks for the update. From the description, you can PING all remote node from the 10.36.0.0/16. You can TRACERT the IP addresses in 10.36.0.0/16 from 10.33.0.0/16. However, TRACERT from 10.36.0.0/16 to 10.33.0.0/16 displays nothing. Am I right? 228 -3557.750625 10.36.2.16 10.33.0.29 ICMP Echo (ping) request 229 -3557.750625 10.33.0.29 10.36.2.16 ICMP Echo (ping) reply According to the network trace, 10.33.0.29 does reply the ICMP request from the 10.36.2.16. It indicates the network connectivity is OK. Could you please paste the IPconfig /all from the problematic computer in 10.36.0.0/16 and explain more about your network topology? If you have any questions or concerns, please do not hesitate to let me know.

HiYes that is correct. This occurs with all the MS windows servers in that subnet, teh switches and unix hosts can all do it without any issues.I have e-mailed you all the info you have requested, please let me what else you need to know in respect of the network.Thankspaul

Hi Paul, Thanks for the update. In the network trace, I found lots of invalid packets because of the checksum incorrect. From your description that you run the Windows Server 2003, you may check how it works if you turn off default SNP features on Windows Server 2003 server. An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers http://support.microsoft.com/kb/948496 If you have any questions or concerns, please do not hesitate to let me know.

Hi MilesI have applied the patch as suggested and restarted the server. The tracert still does the same no results. I have also checked the sevrer has a teamed NIC but we have disabled one NIC whilst these tests are being carried out.Thankspaul

Hi Paul,Now weneed toconfirm the following points:1.Can you use tracert tool properly from a computer in the 10.36.0.0/16 network to a computer in the 10.33.0.0/16 subnet? If possible, please use computers with single NIC to do the test to isolate the influence of teaming and multi-home.2.Does it work if using other trace route tools, such as WFTRACE and VisualRoute?3.Please collect the latest Network Monitor trace when this problem is reproduced.

Hi Paul,Please feel free to let me know if there is any update on this issue.Thanks,Miles