Comcast Intermittent drops WOW and Voice Comms

[Skubuh]

So I have been having issues with Comcast since October of last year. I get random dc's from both WoW and Mumble/Ventrilo voice comms. It can happen any time of day with varying degrees of frequency. My husband gets that same issues as well but when we play together we don't always dc at the same time though often we do. I have gone through 3 different modems and have had techs check cabling in my house and from the house to the street. I have run WinMTR at four different randoms times over the last day. The results are below. Am I wrong or does the issue seem to be in the Comcast network? If yes, what can i do about it?

| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 25 | 618 | 466 | 1 | 10 | 154 | 15 |
| 68.54.244.1 - 0 | 1221 | 1221 | 13 | 42 | 1764 | 29 |
|xe-4-1-0-32767-sur01.howardcounty.md.bad.comcast.net - 0 | 1223 | 1223 | 9 | 23 | 194 | 12 |
|xe-2-1-2-0-ar04.capitolhghts.md.bad.comcast.net - 0 | 1223 | 1223 | 11 | 23 | 155 | 17 |
| 68.86.90.65 - 0 | 1223 | 1223 | 12 | 25 | 159 | 19 |
|be-10001-cr01.ashburn.va.ibone.comcast.net - 0 | 1223 | 1223 | 12 | 24 | 162 | 20 |
|he-0-10-0-1-pe07.ashburn.va.ibone.comcast.net - 0 | 1223 | 1223 | 13 | 23 | 157 | 23 |
| 192.205.37.41 - 0 | 1223 | 1223 | 15 | 27 | 158 | 30 |
| cr1.wswdc.ip.att.net - 0 | 1223 | 1223 | 14 | 26 | 155 | 18 |
| 12.122.93.133 - 0 | 1223 | 1223 | 13 | 24 | 160 | 20 |


|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 9 | 1140 | 1047 | 1 | 7 | 157 | 4 |
| 68.54.244.1 - 0 | 1509 | 1509 | 12 | 41 | 2415 | 36 |
|xe-4-1-0-32767-sur01.howardcounty.md.bad.comcast.net - 0 | 1511 | 1511 | 9 | 24 | 292 | 18 |
|xe-2-1-2-0-ar04.capitolhghts.md.bad.comcast.net - 0 | 1511 | 1511 | 11 | 25 | 318 | 16 |
|he-0-1-0-1-cr02.ashburn.va.ibone.comcast.net - 0 | 1511 | 1511 | 13 | 26 | 319 | 21 |
|be-10001-cr01.ashburn.va.ibone.comcast.net - 0 | 1511 | 1511 | 13 | 26 | 317 | 21 |
|he-0-10-0-1-pe07.ashburn.va.ibone.comcast.net - 0 | 1511 | 1511 | 12 | 24 | 319 | 19 |
| 192.205.37.41 - 0 | 1511 | 1511 | 15 | 28 | 322 | 20 |
| cr2.wswdc.ip.att.net - 0 | 1511 | 1511 | 14 | 27 | 308 | 28 |
| 12.123.250.113 - 0 | 1511 | 1511 | 13 | 26 | 314 | 23 |


|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 6 | 2101 | 1981 | 0 | 8 | 868 | 2 |
| 68.54.244.1 - 0 | 2574 | 2574 | 10 | 47 | 2391 | 36 |
|xe-4-1-0-32767-sur01.howardcounty.md.bad.comcast.net - 0 | 2581 | 2581 | 9 | 25 | 1107 | 13 |
|xe-2-1-2-0-ar04.capitolhghts.md.bad.comcast.net - 0 | 2581 | 2581 | 11 | 26 | 1112 | 14 |
|he-0-1-0-1-cr02.ashburn.va.ibone.comcast.net - 0 | 2581 | 2581 | 13 | 27 | 1112 | 18 |
|be-10001-cr01.ashburn.va.ibone.comcast.net - 0 | 2581 | 2581 | 13 | 28 | 1111 | 18 |
|he-0-10-0-1-pe07.ashburn.va.ibone.comcast.net - 0 | 2581 | 2581 | 12 | 25 | 1113 |13 |
|192.205.37.41 - 0 | 2581 | 2581 | 15 | 30 | 1109 | 25 |
| cr2.wswdc.ip.att.net - 0 | 2581 | 2581 | 14 | 29 | 1121 | 21 |
| 12.123.250.113 - 0 | 2581 | 2581 | 13 | 27 | 1112 | 21 |


|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 17 | 889 | 742 | 1 | 6 | 218 | 3 |
| 68.54.244.1 - 0 | 1477 | 1477 | 13 | 40 | 2119 | 15 |
|xe-4-1-0-32767-sur01.howardcounty.md.bad.comcast.net - 0 | 1480 | 1480 | 10 | 23 | 1103 | 13 |
|ae-1-0-sur01.howardcounty.md.bad.comcast.net - 0 | 1480 | 1480 | 10 | 24 | 1422 | 17 |
|he-3-5-0-0-cr01.newyork.ny.ibone.comcast.net - 0 | 1480 | 1480 | 16 | 27 | 1216 | 26 |

 

[bill001g]

What do you think represents a issue here. These all look pretty good.

The only one that shows a issue is your router....ie 10.0.0.1 and that likely is a false positive because you only get loss to the first hop and no loss past there. That just means the router is too busy to talk to you because it is busy passing traffic. The traffic that goes thought the router is never dropped.

You have some jitter but I suspect that is because you are running on a wireless connection. Jitter does not cause disconnects it causes lag spikes or slight distortions in speech on a voice call.

What you are going to have to do is catch it when it fails. You need to open a number of cmd windows and leave ping commands run to a number of the hops in the trace. When you detect a failure you need to go quickly to these cmd windows and see which if any shows a error.

 

[Skubuh]

no this is not a wireless connection at all my concern is on hop 2 that the latency jumps to 1764, 2415, 2391 and 2119 and could that be enough to dc a voice comm connection or game connection

 

[bill001g]

You will always get some high ping numbers like that. If the router is busy doing other stuff it will always prefer to forward traffic for users than to respond to ping. Sometimes it will even not respond at all but that does not mean there is a network issue it just means the router choose not to respond.

The number that is most important is the average and its relationship to the best and worst. Your average is much closer to the best value. You are getting no packet loss and since the average is very low you likely getting even very little jitter. You would not even see studdering in a live video that can tolerate almost no loss or jitter.

To actually drop a tcp session you would have to have massive packet loss or completely loss for a couple of seconds.

All this really means is the problem did not occur when you were running this tool