Thursday, March 27, 2008

Lesson in PING

I found a way where you can trace a connection to a server more thoroughly than just tracert and ping...

in your command prompt, type: pathping -n (ip address)
eg. pathping -n 205.216.112.157

this will give you a technical result like:

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.102
21/ 100 = 21% |
1 2ms 25/ 100 = 25% 4/ 100 = 4% 192.168.1.10
0/ 100 = 0% |
2 324ms 25/ 100 = 25% 4/ 100 = 4% 218.186.176.1
0/ 100 = 0% |
3 302ms 28/ 100 = 28% 7/ 100 = 7% 172.20.12.65
0/ 100 = 0% |
4 244ms 23/ 100 = 23% 2/ 100 = 2% 172.26.12.1
0/ 100 = 0% |
5 293ms 28/ 100 = 28% 7/ 100 = 7% 172.20.8.137
0/ 100 = 0% |
6 287ms 25/ 100 = 25% 4/ 100 = 4% 203.116.9.101
0/ 100 = 0% |
7 248ms 26/ 100 = 26% 5/ 100 = 5% 203.118.3.228
0/ 100 = 0% |
8 452ms 21/ 100 = 21% 0/ 100 = 0% 157.130.211.153
0/ 100 = 0% |
9 476ms 28/ 100 = 28% 7/ 100 = 7% 152.63.48.246
0/ 100 = 0% |
10 557ms 22/ 100 = 22% 1/ 100 = 1% 152.63.21.110
0/ 100 = 0% |
11 559ms 24/ 100 = 24% 3/ 100 = 3% 152.63.24.69
0/ 100 = 0% |
12 551ms 21/ 100 = 21% 0/ 100 = 0% 157.130.24.238
1/ 100 = 1% |
13 528ms 27/ 100 = 27% 5/ 100 = 5% 205.216.112.82
0/ 100 = 0% |
14 535ms 22/ 100 = 22% 0/ 100 = 0% 205.216.112.157

Trace complete.

based on these results, i can see that there is definitely a connection problem!
on the average, 20% of my connection gets dropped and that affects connection stability.