Nick Wolf
asked on
tracert: Significance of First Hop "Request Timed Out"
When running the command 'tracert' on a WinXP machine, what is the significance of a "Request Timed Out" result for the first hop, but successful subsequent hops? For example:
-----------------------
C:\Documents and Settings\Nick>tracert main
Tracing route to main.bw.local [172.21.1.4]
over a maximum of 30 hops:
1 * * * Request timed out.
2 28 ms 11 ms 11 ms 172.21.1.4
Trace complete.
-----------------------
"main"(172.21.1.4) is a server being reached remotely over a VPN connection.
Other public IPs (google.com, yahoo.com, etc.) were also previously failing on first hop of tracert, but then a few minutes later gave a "1ms 1ms <1ms 192.168.5.1" result for the local default gateway and continued on to the destination.
Does a Time Out on the first hop have any significance for troubleshooting a connection?
-----------------------
C:\Documents and Settings\Nick>tracert main
Tracing route to main.bw.local [172.21.1.4]
over a maximum of 30 hops:
1 * * * Request timed out.
2 28 ms 11 ms 11 ms 172.21.1.4
Trace complete.
-----------------------
"main"(172.21.1.4) is a server being reached remotely over a VPN connection.
Other public IPs (google.com, yahoo.com, etc.) were also previously failing on first hop of tracert, but then a few minutes later gave a "1ms 1ms <1ms 192.168.5.1" result for the local default gateway and continued on to the destination.
Does a Time Out on the first hop have any significance for troubleshooting a connection?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Rob