Tell me more ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
up vote 0 down vote favorite

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?

share|improve this question
A firewall on the host itself? The host using itself as the default gateway? – joeqwerty Nov 18 '10 at 0:40
Normally the first entry on traceroute would be the gateway. If the first entry is itself, then apparently the computer believes that it is the gateway (though it will print its own address if it gets a no route to host error for the first hop). Which could possibly be legit if it is running some kind of VPN. Can you post the results of ip route (or route -n) so we can see how it's routing things? – DerfK Nov 18 '10 at 0:55
unfortunately (in a manner of speaking) i fixed the issue I was having and so I can't get any further information. I did look at the output of route but couldn't see anything amiss. BTW the solution was to turn the machine off and on again, go figure. – radman Nov 18 '10 at 2:21

2 Answers

up vote 0 down vote accepted

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.

share|improve this answer
up vote 0 down vote

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.

share|improve this answer
This would be better as a comment – James Mohler Dec 5 '12 at 4:23

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.