Large Packet Loss Issues

Scott Talsma

Honorable
Oct 14, 2013
11
0
10,510
Hello!

For the past week or so (~10days) I've been experience issues with my internet connection. After running various tests, I've found out that my latency and connectivity issues are due to large amounts of packet loss.

9i6be0.png

mh97vc.jpg

2cyfgwx.png



This has only been occurring on my PC from what I've been able to notice, other PCs (connected by wifi) have not been experiencing the same issues.

While trying to pinpoint the problem, I ran various pathping tests. The following show the results from:

A) My laptop connected by ethernet cable
B) My laptop connected by wireless internet
C) My PC connected by ethernet


(A) Laptop Ethernet
C:\Documents and Settings\Sxt>pathping 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 sxt-9bd0e9041.home.network [10.0.0.18]
1 10.0.0.1
2 98.250.192.1
3 xe-8-1-0-32767-sur02.royaloak.mi.michigan.comcast.net [68.85.49.237]
4 te-0-8-0-5-ar01.pontiac.mi.michigan.comcast.net [68.85.222.66]
5 he-4-4-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.113]
6 he-0-12-0-0-pe04.350ecermak.il.ibone.comcast.net [68.86.83.162]
7 192.205.37.21
8 cr1.cgcil.ip.att.net [12.122.133.106]
9 cr2.dvmco.ip.att.net [12.122.31.85]
10 cr1.slkut.ip.att.net [12.122.30.25]
11 cr2.la2ca.ip.att.net [12.122.30.30]
12 gar5.lsrca.ip.att.net [12.122.85.33]
13 12-122-254-226.attens.net [12.122.254.226]
14 206.16.68.42
15 paxonix-placeholder.lax1.attens.net [12.129.248.118]
16 12.129.209.68

Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 sxt-9bd0e9041.home.network [10.0
.0.18]
1/ 100 = 1% |
1 0ms 1/ 100 = 1% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 8ms 1/ 100 = 1% 0/ 100 = 0% 98.250.192.1
0/ 100 = 0% |
3 12ms 1/ 100 = 1% 0/ 100 = 0% xe-8-1-0-32767-sur02.royaloak.mi.m
ichigan.comcast.net [68.85.49.237]
0/ 100 = 0% |
4 12ms 1/ 100 = 1% 0/ 100 = 0% te-0-8-0-5-ar01.pontiac.mi.michiga
n.comcast.net [68.85.222.66]
0/ 100 = 0% |
5 18ms 1/ 100 = 1% 0/ 100 = 0% he-4-4-0-0-cr01.350ecermak.il.ibon
e.comcast.net [68.86.90.113]
0/ 100 = 0% |
6 16ms 1/ 100 = 1% 0/ 100 = 0% he-0-12-0-0-pe04.350ecermak.il.ibo
ne.comcast.net [68.86.83.162]
0/ 100 = 0% |
7 19ms 1/ 100 = 1% 0/ 100 = 0% 192.205.37.21
0/ 100 = 0% |
8 --- 100/ 100 =100% 99/ 100 = 99% cr1.cgcil.ip.att.net [12.122.133.1
06]
0/ 100 = 0% |
9 --- 100/ 100 =100% 99/ 100 = 99% cr2.dvmco.ip.att.net [12.122.31.85
]
0/ 100 = 0% |
10 --- 100/ 100 =100% 99/ 100 = 99% cr1.slkut.ip.att.net [12.122.30.25
]
0/ 100 = 0% |
11 --- 100/ 100 =100% 99/ 100 = 99% cr2.la2ca.ip.att.net [12.122.30.30
]
0/ 100 = 0% |
12 --- 100/ 100 =100% 99/ 100 = 99% gar5.lsrca.ip.att.net [12.122.85.3
3]
0/ 100 = 0% |
13 --- 100/ 100 =100% 99/ 100 = 99% 12-122-254-226.attens.net [12.122.
254.226]
0/ 100 = 0% |
14 --- 100/ 100 =100% 99/ 100 = 99% 206.16.68.42
0/ 100 = 0% |
15 --- 100/ 100 =100% 99/ 100 = 99% paxonix-placeholder.lax1.attens.ne
t [12.129.248.118]
0/ 100 = 0% |
16 69ms 1/ 100 = 1% 0/ 100 = 0% 12.129.209.68

Trace complete.

---------

(B) Laptop WIreless

C:\Documents and Settings\Sxt>pathping 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 sxt-9bd0e9041.home.network [10.0.0.15]
1 10.0.0.1
2 98.250.192.1
3 xe-8-1-0-32767-sur02.royaloak.mi.michigan.comcast.net [68.85.49.237]
4 te-0-8-0-5-ar01.pontiac.mi.michigan.comcast.net [68.85.222.66]
5 he-4-4-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.113]
6 he-0-12-0-0-pe04.350ecermak.il.ibone.comcast.net [68.86.83.162]
7 192.205.37.21
8 cr1.cgcil.ip.att.net [12.122.133.106]
9 cr2.dvmco.ip.att.net [12.122.31.85]
10 cr1.slkut.ip.att.net [12.122.30.25]
11 cr2.la2ca.ip.att.net [12.122.30.30]
12 gar5.lsrca.ip.att.net [12.122.85.33]
13 12-122-254-226.attens.net [12.122.254.226]
14 206.16.68.42
15 paxonix-placeholder.lax1.attens.net [12.129.248.118]
16 12.129.209.68

Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 sxt-9bd0e9041.home.network [10.0
.0.15]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 15ms 0/ 100 = 0% 0/ 100 = 0% 98.250.192.1
0/ 100 = 0% |
3 17ms 0/ 100 = 0% 0/ 100 = 0% xe-8-1-0-32767-sur02.royaloak.mi.m
ichigan.comcast.net [68.85.49.237]
0/ 100 = 0% |
4 15ms 1/ 100 = 1% 1/ 100 = 1% te-0-8-0-5-ar01.pontiac.mi.michiga
n.comcast.net [68.85.222.66]
0/ 100 = 0% |
5 22ms 0/ 100 = 0% 0/ 100 = 0% he-4-4-0-0-cr01.350ecermak.il.ibon
e.comcast.net [68.86.90.113]
0/ 100 = 0% |
6 22ms 0/ 100 = 0% 0/ 100 = 0% he-0-12-0-0-pe04.350ecermak.il.ibo
ne.comcast.net [68.86.83.162]
0/ 100 = 0% |
7 24ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.21
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% cr1.cgcil.ip.att.net [12.122.133.1
06]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% cr2.dvmco.ip.att.net [12.122.31.85
]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% cr1.slkut.ip.att.net [12.122.30.25
]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% cr2.la2ca.ip.att.net [12.122.30.30
]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% gar5.lsrca.ip.att.net [12.122.85.3
3]
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% 12-122-254-226.attens.net [12.122.
254.226]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% 206.16.68.42
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% paxonix-placeholder.lax1.attens.ne
t [12.129.248.118]
0/ 100 = 0% |
16 77ms 0/ 100 = 0% 0/ 100 = 0% 12.129.209.68

Trace complete.



-----
(C) PC Ethernet

C:\Windows\System32>pathping 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Sxter.home.network [10.0.0.8]
1 10.0.0.1
2 98.250.192.1
3 xe-8-1-0-32767-sur02.royaloak.mi.michigan.comcast.net [68.85.49.237]
4 te-0-8-0-5-ar01.pontiac.mi.michigan.comcast.net [68.85.222.66]
5 he-4-4-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.113]
6 he-0-12-0-0-pe04.350ecermak.il.ibone.comcast.net [68.86.83.162]
7 192.205.37.21
8 cr1.cgcil.ip.att.net [12.122.133.106]
9 cr2.dvmco.ip.att.net [12.122.31.85]
10 cr1.slkut.ip.att.net [12.122.30.25]
11 cr2.la2ca.ip.att.net [12.122.30.30]
12 gar5.lsrca.ip.att.net [12.122.85.33]
13 12-122-254-226.attens.net [12.122.254.226]
14 206.16.68.42
15 paxonix-placeholder.lax1.attens.net [12.129.248.118]
16 12.129.209.68

Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Sxter.home.network [10.0.0.8
]
8/ 100 = 8% |
1 0ms 8/ 100 = 8% 0/ 100 = 0% 10.0.0.1
1/ 100 = 1% |
2 9ms 9/ 100 = 9% 0/ 100 = 0% 98.250.192.1
3/ 100 = 3% |
3 11ms 13/ 100 = 13% 1/ 100 = 1% xe-8-1-0-32767-sur02.royaloak.mi.m
ichigan.comcast.net [68.85.49.237]
0/ 100 = 0% |
4 11ms 13/ 100 = 13% 1/ 100 = 1% te-0-8-0-5-ar01.pontiac.mi.michiga
n.comcast.net [68.85.222.66]
0/ 100 = 0% |
5 18ms 15/ 100 = 15% 3/ 100 = 3% he-4-4-0-0-cr01.350ecermak.il.ibon
e.comcast.net [68.86.90.113]
0/ 100 = 0% |
6 17ms 12/ 100 = 12% 0/ 100 = 0% he-0-12-0-0-pe04.350ecermak.il.ibo
ne.comcast.net [68.86.83.162]
2/ 100 = 2% |
7 20ms 14/ 100 = 14% 0/ 100 = 0% 192.205.37.21
2/ 100 = 2% |
8 --- 100/ 100 =100% 84/ 100 = 84% cr1.cgcil.ip.att.net [12.122.133.1
06]
0/ 100 = 0% |
9 --- 100/ 100 =100% 84/ 100 = 84% cr2.dvmco.ip.att.net [12.122.31.85
]
0/ 100 = 0% |
10 --- 100/ 100 =100% 84/ 100 = 84% cr1.slkut.ip.att.net [12.122.30.25
]
0/ 100 = 0% |
11 --- 100/ 100 =100% 84/ 100 = 84% cr2.la2ca.ip.att.net [12.122.30.30
]
0/ 100 = 0% |
12 --- 100/ 100 =100% 84/ 100 = 84% gar5.lsrca.ip.att.net [12.122.85.3
3]
0/ 100 = 0% |
13 --- 100/ 100 =100% 84/ 100 = 84% 12-122-254-226.attens.net [12.122.
254.226]
0/ 100 = 0% |
14 --- 100/ 100 =100% 84/ 100 = 84% 206.16.68.42
0/ 100 = 0% |
15 --- 100/ 100 =100% 84/ 100 = 84% paxonix-placeholder.lax1.attens.ne
t [12.129.248.118]
0/ 100 = 0% |
16 69ms 16/ 100 = 16% 0/ 100 = 0% 12.129.209.68

Trace complete.


I can see that there is a lot more issue coming from my PC. Now my question is this:

What is causing my packet loss (Modem, Router, Ethernet Cables, Network Card, Certain Drivers on my Computer)? Can it be discerned from the data provided? If it seems like it may be a network card issue, is there some sort of software or program that I can use to double check the state of my network card?

Thank you for taking the time to read this.
 
Solution
Can you perform the tests one more time? Now that a little time has passed, it is good to get a second reference for the results. It looks like the majority of the packet loss is coming from a few particular sources. Also, can you perform the pingtest both wired and wireless? That way if it is a particular interface, we can discern from the data.

It seems the paths remain the same for the trace routes, but if the problem only appears on one computer we can be fairly certain these shouldn't matter as we are looking at a local problem. The router should not be the source of the problem as long as you have tried the wired connection under multiple ports. The modem should be good to go as well based on the same assumptions that other...
Can you perform the tests one more time? Now that a little time has passed, it is good to get a second reference for the results. It looks like the majority of the packet loss is coming from a few particular sources. Also, can you perform the pingtest both wired and wireless? That way if it is a particular interface, we can discern from the data.

It seems the paths remain the same for the trace routes, but if the problem only appears on one computer we can be fairly certain these shouldn't matter as we are looking at a local problem. The router should not be the source of the problem as long as you have tried the wired connection under multiple ports. The modem should be good to go as well based on the same assumptions that other devices are running fine on the network.

Have you tried re-installing the device drivers for your network interfaces? I suppose packets could be getting dropped on the PC, but according to the Pingtest, the packet loss is happening while in transit. My best advice at this point beyond reinstalling the drivers would be to run the ping test on multiple servers several times over the next few days. Best of luck to ya and look forward to a response - Sub
 
Solution
I've done the tests multiple times over the past 4 or 5 days. They all show very similar results to the ones posted. I cannot perform the test wirelessly from my PC as it can only connect through ethernet (no wireless). I suppose I'm just going to assume that it is the network card for now and maybe try out a different card or wireless usb to see if anything gets fixed.

Thank you for your time.