O/T: Wierd tracert results

  • Thread starter Thread starter Random Person
  • Start date Start date
R

Random Person

Has anyone ever tried tracert to a few IPs and turned up with "Request
Timed Out" hops in the process? Mine happens regardless of what IP I
use, and the first hop *always* times out.

Also, should I expect the response of each hop to be about the same
time as the ping to the hop? I'm getting pings of <50ms and yet it
takes a few seconds for the hop to be identified.

Any suggestions on what might be the matter?

Thanks.
 
Random said:
Has anyone ever tried tracert to a few IPs and turned up with "Request
Timed Out" hops in the process? Mine happens regardless of what IP I
use, and the first hop *always* times out.

Also, should I expect the response of each hop to be about the same
time as the ping to the hop? I'm getting pings of <50ms and yet it
takes a few seconds for the hop to be identified.

Any suggestions on what might be the matter?

Thanks.

Some servers to not respond to pings, simple as that.

Q
 
Has anyone ever tried tracert to a few IPs and turned up with "Request
Timed Out" hops in the process? Mine happens regardless of what IP I
use, and the first hop *always* times out.

First hop, as-in your or the ISP's router?
What IP #?
Without more info it's hard to say but seems like a network
problem.
 
Has anyone ever tried tracert to a few IPs and turned up with "Request
Timed Out" hops in the process? Mine happens regardless of what IP I
use, and the first hop *always* times out.

Also, should I expect the response of each hop to be about the same
time as the ping to the hop? I'm getting pings of <50ms and yet it
takes a few seconds for the hop to be identified.

Any suggestions on what might be the matter?

Thanks.

Are you possibly using some type of personal firewall that's blocking
your machine from responding with an ICMP TTL EXPIRED message. The
delay you're seeing is caused by traceroute trying to do a reverse DNS
lookup on each hop it identifies.
 
Back
Top