News Stay informed about the latest enterprise technology news and product updates.

From the Trenches, part three: Network troubleshooting with pathping

In the last installment of this three-part article, network administrator and IT consultant Tim Fenner will discuss the basic uses of pathping ways to use it more extensively.

If you've read parts one and two of this series, you've gotten your feet wet with the ping and tracert TCP/IP connection-testing utilities. Now you're ready to take the plunge into a much more complex utility, called pathping.

Pathping is a route-tracing tool that combines features of the ping and tracert commands with additional information-gathering features that neither of those commands provides. The pathping command sends packets to each router on the way to a final destination over a period of time and then computes results based on the packets returned from each hop. Since pathping shows the degree of packet loss at any given router or link, you can determine which routers or links might be causing network problems.

Again you say: "All right. You are very good at copying and pasting definitions, but what does all that mean to me?" What it means is this: using the pathping command is like picking up the phone and dialing a number to see whether it rings on the other side, whether it speaks the right language (TCP/IP in this case), how long it takes, how many operators the call had to cross, who the operators were, and what percentage of communication was lost. This last type of data illustrates where problems might exist.

To use pathping, type:

  • pathping
  • pathping
Sample output below:


Tracing route to [] over a maximum of 30 hops:
0 []
3 []
4 []
5 []
6 []
7 []
8 []
9 []
10 []
11 []
13 []

Computing statistics for 325 seconds...

Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 []
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0%
0/ 100 = 0% |

>> Editor's note: You get the picture. This code goes on for quite a ways.

Trace complete.

After running pathping, you first see the results for the route as it is tested for problems. This is the same path as that shown by the tracert command. The pathping command then displays a busy message for the next 325 seconds (this time varies by the hop count). During this time, pathping gathers information from all the routers previously listed and from the links among them. At the end of this period, it displays the test results.

The Node/Link, Lost/Sent=Pct and Address categories provide the most useful information. The link at hop 7 shows that 100% of the packets are being lost, showing there is a routing problem at the router, perhaps link congestion. Hop 12 shows that there is a 5% packet loss rate.

Again, as with the other utilities, there are many different options with this utility. To display them, type:

  • pathping | more
Once again, note that the | is not a lower case L or a number 1. On most systems, you can produce this symbol by pressing the shift key and the backslash key at the same time.

If you only need to check for connectivity between your system and another, then ping will work very quickly and effectively. But if you wish to determine where a network problem exists, use pathping. Pathping can determine where the issue actually resides.

There are many more network connectivity tools at your disposal within Windows, but these are a few of the more common tools used in network troubleshooting.

About the author: Tim Fenner is a network and systems administrator for a national industry association and an IT consultant for small businesses.


>> Return to part one: ping
>> Return to part two: tracert
>> Reference works for this article include

Dig Deeper on Enterprise infrastructure management

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.