Home / server / Questions / 203198
Accepted
radman
Asked: 2010-11-18 14:53:03 +0800 CST

why does tracert only report one hop on failure

  • 772

I've been having an issue with one host on my network not being able to ping or tracert machines on the internet while all other hosts can.

When I run a tracert from the machine I get the following output:

traceroute to host.to.trace.to (XXX.XXX.XXX.X), 30 hops max, 60 byte packets
1 (192.168.XXX.XXX) 0.173 ms 0.259 ms *

In this example 192.168.XXX.XXX is the machine I am tracerouting from. So it looks like something funky is going on as no other tracert I've seen includes the source IP.

I am also under the assumption that the tracert should at least be hitting my local router.

Can anyone explain this anomaly?

networking ping

2 Answers

  1. Best Answer

    Well I managed to pinpoint where the error was occurring and it turns out that peerguardian was assassinating all incoming packets to the host. I'm not exactly sure why the tracert looks like it does but it does explain why tracert was never getting any information.

    • 0

  2. I got a similar problem on OS X. I could ping but not traceroute to some sites (twitter.com for example) The error was "no route to host" The cure was to remove PeerGuardian. This program also blocked access to ntp timeservers.

    • 0