When an IP address is accessible by one machine on one ISP but not another machine/ISP, how can you determine where along the path the issue lies?

Is it possible to determine whether it's the destination IP address/host who's the culprit, or the ISP, or some routing node along the way?

  • Please edit your question to include the output of pathping ipaddress from each computer.
    – DavidPostill
    Mar 24, 2015 at 7:54

1 Answer 1


Assuming Windows:

From the command line, on each computer, run 'tracert youripaddress' to see if the destination is reachable.

  • 2
    or pathping which is the same and with pinging.
    – Journeyman Geek
    Mar 24, 2015 at 2:27
  • Aggredo. 6 of one, half-dozen of the other for this I should think.
    – Junkiebev
    Mar 24, 2015 at 3:12
  • Pathping gives more useful info, for example how packets are being lost/dropped
    – DavidPostill
    Mar 24, 2015 at 7:52
  • @JourneymanGeek Interesting, had never heard of pathping. I've used and tried tracert, however, the destination isn't reachable -- there are 10+ entries of "No response" up until the end. Mar 24, 2015 at 17:04
  • @DavidPostill I'm assuming these commands basically show which node along the line is causing the problem? But sometimes nodes don't respond to the trace, even though they're working correctly, right? How can you tell whether a node is simply not providing info for the trace vs. not working entirely (or dropping the connection/packet)? Mar 24, 2015 at 17:06

You must log in to answer this question.

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