I’ve just discovered a new windows command line utility called pathping today. I’m a bit of a purist and hate installing extra utilities to use from the command line so I was happy to see that this one was included with my Windows 7 Professional installation.
This command produces something similar to the output from both the ping and tracert commands but if you are prepared to wait for the data collection period it provides statistics of each node based on data collected over that time.
This is the output from pathping google.com:
Tracing route to google.com [66.102.11.104]
over a maximum of 30 hops:
0 ######### [192.168.0.5]
1 192.168.0.1
2 nexthop.wa.iinet.net.au [203.59.14.16]
3 te7-1.per-qv1-bdr1.iinet.net.au [203.215.4.18]
4 gi15-1-1.syd-ult-core1.iinet.net.au [203.215.20.4]
5 as15169.sydney.pipenetworks.com [218.100.2.97]
6 66.249.95.232
7 64.233.174.242
8 syd01s01-in-f104.1e100.net [66.102.11.104]Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 ######### [192.168.0.5]0/ 100 = 0% |
1 5ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 22ms 0/ 100 = 0% 0/ 100 = 0% nexthop.wa.iinet.net.au [203.59.14
.16]
0/ 100 = 0% |
3 20ms 0/ 100 = 0% 0/ 100 = 0% te7-1.per-qv1-bdr1.iinet.net.au [2
03.215.4.18]
0/ 100 = 0% |
4 81ms 1/ 100 = 1% 1/ 100 = 1% gi15-1-1.syd-ult-core1.iinet.net.a
u [203.215.20.4]
0/ 100 = 0% |
5 81ms 0/ 100 = 0% 0/ 100 = 0% as15169.sydney.pipenetworks.com [2
18.100.2.97]
0/ 100 = 0% |
6 76ms 0/ 100 = 0% 0/ 100 = 0% 66.249.95.232
0/ 100 = 0% |
7 79ms 0/ 100 = 0% 0/ 100 = 0% 64.233.174.242
0/ 100 = 0% |
8 82ms 0/ 100 = 0% 0/ 100 = 0% syd01s01-in-f104.1e100.net [66.102
.11.104]Trace complete.
I had to wait 200 seconds for these results but they are pretty comprehensive. The link looks pretty good – only one packet lost on the hop between Perth and Sydney.
No comments:
Post a Comment