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?
nicholasjwolfAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
rjwesleyConnect With a Mentor Commented:
Oooops, uhm should read these in their entirety. Well a router with ping connections disabled would give you the Request time outs but your problem is intermittent. Hmm, I guess I'd probably test that particular data line and possibly connect directly to the router to help pinpoint the problem.

Rob
0
 
rjwesleyCommented:
It could simply be that your router has ping connections disabled on it.

Rob
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.