Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What can I do when a ping times out whilst en route to its destination?

I have contacted the last IP address listed in the trace and they say it is timing out after it leaves their server.

I can't find out who owns the next server.

How do I resolve this?

share|improve this question
Diagnosing network problems is a skill that can't be explained in a few paragraphs. Are you sure this destination is supposed to respond to pings? – David Schwartz Apr 21 '12 at 20:38
@TomWijsman: I'm asking if the destination is supposed to respond to pings (as seen from the Internet). He's saying that the pings are leaving the last IP address listed in the trace. The behavior he is seeing is perfectly consistent with a destination host (or destination network) that does not respond to pings. – David Schwartz Apr 21 '12 at 21:45
@TomWijsman You've misunderstood the question. The packets are leaving the last IP address listed in the trace and continuing towards their destination. There's no evidence they're reaching the destination. – David Schwartz Apr 22 '12 at 20:25
@TomWijsman The last IP address listed in the trace isn't the destination. There's no evidence to suggest any packets reached the destination. – David Schwartz Apr 22 '12 at 22:16
@DavidSchwartz: The last IP in a trace is always the destination, else it wouldn't be a trace. The next server is that on the route back. There is no evidence that the destination is not receiving the packets, which is why he contacted the last IP address to verify. In any case, both ends have to perform a pathping to verify which hops are exactly the problem and contact those. Randomly contacting hops in between does not make much sense. And well, if an intermediary hop doesn't answer then it's probably for a reason. Let's wait for more detail from Vaughan... – Tom Wijsman Apr 22 '12 at 22:39

Simply put, not a lot!

ICMP Echo / Ping is one of the most basic network diagnostic tools out there, but can be hard to diagnose.... The most common cause of a time out is is simply that the target is blocking it in their firewall, or just configured servers not to respond.

If you are trying to diagnose something specific, I highly recommend you use some alternative tools. If you are using Windows, I recommend looking at both tracert and pathping which are both excellent networking tools.

share|improve this answer
pathping is indeed the tool to figure out where your pings drop. – Tom Wijsman Apr 21 '12 at 21:13

If it responds nothing to ping it says to you "none of your business, go away"

share|improve this answer
Exactly. Unless you have some agrement with the administrators of the destination machine or network to provide you with a ping reply service, they have no obligation to provide you with such a service. It should be no surprise that they don't provide a service they don't offer. – David Schwartz Apr 21 '12 at 21:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .