dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
702
Sillycatnip
join:2006-10-24

2 edits

Sillycatnip

Member

[Connectivity] Timed outs and major lag (2 weeks+)

Timed outs and major lag (2 weeks+)

I need some help trying to figure out what I can do. Spoke with a comcast supervisor who informed me because my tests that I just did (on the Phone) were showing ATT Telnet, there was nothing I could do except call ATT. Hmmmm... As you can see by some of my old results, it does not appear to be anyone but Comcast. I have tried everything I can do... I need some major help on what else I can do? Any recommendations?

I know I am a beginner... and I am sorry if I posted info that wasn't needed and didn't post info that was needed. I am going through all the help FAQ's now to see what else would help everyone.

PS: I know the number of calls was high, and I don't like being a pest, but my internet became a headache and due to work was unable to spend the time I would have liked online (until now)... RL issues

I am not a pro and a lot of this is new to me. I am doing what has been recommended so far by friends, techs, etc. I am not sure what else I can post.

I play a game online and for two weeks I was having massive lag spikes... every 10-20 minutes I would get 1, 2, 4, and very rarely a 5 count 100% packet loss (see bottom of post for example). This would cause me to disconnect from everything (Game, ICQ, AOL, ETC.) then it would reconnect me. This stayed constant no matter what time of day (I tried 6 am, 11 pm, 5pm-11 pm, 1-3 am). A Technician (2nd) came again and replaced a cable box and outside cables. This fixed the issue for 5 days and now it's back. This time I am not being disconnected, but I am getting large lag, and when I ping something now (6pm-current) I have 256 ms on average). To make sure, both then and now, it wasn't just my game I ping various servers, game and non game related.

I need any help anyone can provide.

Computer Specs:
Windows XP
AMD 3500+ ClawHammer
1 Gib Ram
128 GForce 6600GT
Asus A8N-Delux
Comcast Cable Internet
No Hub/Router

Last techician came out and changed the box and some internet cables. This seemed to solve the issue up until 3 days ago.

Three days ago my lag decided to show it's ugly head again.

The issue is when I play I am fine and then a sputter. I get a mini freeze, not like before. My computer freezes like a slow connection then resumes. Everyone around me runs perfectly fine, but my guy freezes up.

Since the lag has hit I have tried several differnt things.

1 - defrag
3 - virus scans (updated everyday)
14 - Spyware scans (updated everyday)
2 - test computers
2 - ethernet cords
2 - outlets
6 - ping -t (insert web url)
8 - UO traceroutes
3 - Comcast Technicians
1 - Comcast Supervisor
====================
Previous to this
14 (not sure on exact number) - days of stress tests using ping -t (insert website) as well as UO traceroute, and various other commands.
14 - Calls to Comcast Tech support (Trying to get them to run a line stress test on their end or ping me while I timed out).
2- Comcast Technicians (only one to ping and see connection lost)
3 - Cable Boxes (including one the technician switched out)
1 - New cables from outside box to inside outlets
3 - Differnt Test Computers
3 - Differnt Ethernet cords
2 - Differnt Cable outlets
1 - reformat
1 - defrag
All vireus scanners and firewalls disabled
No hub or routers used
==========================

A few test results from tonight.

------------------------------------------------
Ping www.yahoo.com
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 0.0.0.0 1 0ms
GE-2-4-ur01.denver.co.denver.comc68.86.104.185 2 8ms
10g-8-3-ar01.denver.co.denver.com68.86.103.1 3 11ms
* Unknown Host * 68.86.128.6 4 6ms
* Unknown Host * 12.125.159.89 5 180ms
tbr1-p013304.dvmco.ip.att.net 12.123.207.154 6 34ms
tbr2-cl31.sffca.ip.att.net 12.122.12.133 7 220ms
ggr3-ge90.sffca.ip.att.net 12.122.82.149 8 238ms
* Unknown Host * 192.205.33.78 9 224ms
* Unknown Host * 4.71.112.14 10 34ms
g-1-0-0-p161.msr1.sp1.yahoo.com 216.115.107.63 11 35ms
te-8-1.bas-a1.sp1.yahoo.com 209.131.32.17 12 241ms
f1.www.vip.sp1.yahoo.com 209.131.36.158 13 218ms
------------------------------------------------

-
------------------------------------------------
ping www.ask.com
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 0.0.0.0 1 0ms
GE-2-4-ur01.denver.co.denver.comc68.86.104.185 2 7ms
10g-8-3-ar01.denver.co.denver.com68.86.103.1 3 7ms
* Unknown Host * 68.86.103.134 4 19ms
* Unknown Host * 12.116.159.13 5 9ms
tbr1013801.dvmco.ip.att.net 12.123.207.138 6 31ms
tbr2-cl31.sffca.ip.att.net 12.122.12.133 7 236ms
ggr2-p390.sffca.ip.att.net 12.123.13.185 8 202ms
br2-a340s1.attga.ip.att.net 192.205.33.198 9 34ms
0.so-2-0-0.XL2.SCL2.ALTER.NET 152.63.57.102 10 33ms
0.so-6-0-0.XL2.BOS4.ALTER.NET 152.63.16.130 11 78ms
0.so-7-0-0.XR2.BOS4.ALTER.NET 152.63.16.134 12 260ms
0.so-7-0-0.WR2.BOS6.ALTER.NET 152.63.29.221 13 81ms
so-1-0-0.ur2.bos6.web.wcom.net 63.111.123.34 14 282ms
* Unknown Host * 208.254.32.53 15 81ms
* Unknown Host * 65.214.32.81 16 293ms
webt.wc.ask.com 65.214.39.56 17 312ms
------------------------------------------------

------------------------------------------------
ping www.msn.com
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 0.0.0.0 1 0ms
GE-2-4-ur01.denver.co.denver.comc68.86.104.185 2 9ms
10g-8-3-ar01.denver.co.denver.com68.86.103.1 3 7ms
* Unknown Host * 68.86.128.6 4 7ms
* Unknown Host * 12.125.159.89 5 179ms
tbr1-p013704.dvmco.ip.att.net 12.123.207.146 6 217ms
tbr2-cl31.sffca.ip.att.net 12.122.12.133 7 199ms
* Unknown Host * 12.122.80.41 8 33ms
* Unknown Host * 12.126.40.6 9 35ms
ge-7-3-0-57.sjc-64cb-1b.ntwk.msn.207.46.37.201 10 268ms
pos6-1.tuk-76cb-1b.ntwk.msn.net 207.46.34.170 11 50ms
ten1-4.tuk-76c-1b.ntwk.msn.net 207.46.36.157 12 51ms
gig8-12.tuk-6nf-8a.ntwk.msn.net 207.46.38.158 13 223ms
------------------------------------------------

------------------------------------------------
ping lakeaustin.owo.com
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 0.0.0.0 1 0ms
GE-2-4-ur01.denver.co.denver.comc68.86.104.185 2 7ms
10g-8-3-ar01.denver.co.denver.com68.86.103.1 3 6ms
* Unknown Host * 68.86.103.146 4 14ms
* Unknown Host * 12.124.158.17 5 10ms
tbr1-p013302.dvmco.ip.att.net 12.123.207.162 6 223ms
tbr2-cl31.sffca.ip.att.net 12.122.12.133 7 211ms
* Unknown Host * 12.123.12.61 8 253ms
* Unknown Host * 0.0.0.0 9 0ms
* Unknown Host * 159.153.192.230 10 33ms
central-aw1.owo.com 159.153.209.6 11 222ms
------------------------------------------------

------------------------------------------------
ping pacific.owo.com
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 0.0.0.0 1 0ms
GE-2-4-ur01.denver.co.denver.comc68.86.104.185 2 19ms
10g-8-3-ar01.denver.co.denver.com68.86.103.1 3 6ms
* Unknown Host * 68.86.103.142 4 7ms
* Unknown Host * 12.116.159.13 5 9ms
tbr1013801.dvmco.ip.att.net 12.123.207.138 6 45ms
tbr2-cl31.sffca.ip.att.net 12.122.12.133 7 203ms
gar17-p370.sffca.ip.att.net 12.123.12.37 8 213ms
* Unknown Host * 0.0.0.0 9 0ms
* Unknown Host * 159.153.192.230 10 37ms
central-aw5.owo.com 159.153.209.54 11 229ms
------------------------------------------------

------------------------------------------------
ping legends.owo.com
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 0.0.0.0 1 0ms
GE-2-4-ur01.denver.co.denver.comc68.86.104.185 2 7ms
10g-8-3-ar01.denver.co.denver.com68.86.103.1 3 19ms
* Unknown Host * 68.86.103.134 4 9ms
* Unknown Host * 12.116.159.13 5 13ms
tbr2013801.dvmco.ip.att.net 12.123.207.142 6 264ms
tbr1-cl32.cgcil.ip.att.net 12.122.10.117 7 263ms
tbr1-cl14.n54ny.ip.att.net 12.122.10.1 8 72ms
tbr2-cl23.n54ny.ip.att.net 12.122.9.130 9 57ms
tbr2-cl15.wswdc.ip.att.net 12.122.10.54 10 256ms
gar1-p360.abnva.ip.att.net 12.123.8.45 11 254ms
* Unknown Host * 0.0.0.0 12 0ms
fert02.abn-iad.ea.com 159.153.224.11 13 56ms
* Unknown Host * 159.153.233.59 14 63ms
------------------------------------------------

------------------------------------------------
Using CMD;Dos, ping www.yahoo.com
f1.www.vip.sp1.yahoo.com 209.131.36.158 241ms

Using CMD;Dos, ping www.ask.com
webt.wc.ask.com 65.214.39.56 312ms

Using CMD;Dos, ping lakeaustin.owo.com
central-aw1.owo.com 159.153.209.6 242ms
==================================

Whois Report
68.86.104.185
Domain Name: COMCAST.NET
Registrar: NETWORK SOLUTIONS, LLC.
Whois Server: whois.networksolutions.com

12.123.207.162
Domain Name: ATT.NET
Registrar: NETWORK SOLUTIONS, LLC.
Whois Server: whois.networksolutions.com

159.153.209.6
Domain Name: OWO.COM
Registrar: NETWORK SOLUTIONS, LLC.
Whois Server: whois.networksolutions.com
================================

A Few Old Tests
---------------------------------------------------------

pinging www.yahoo.com while playing
9:30 - 9:50 PM
traceroute


Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 0.0.0.0 1 0ms
GE-2-4-ur01.denver.co.denver.comc68.86.104.185 2 8ms 8ms 1% 372 / 377 5ms / 26ms
10g-8-3-ar01.denver.co.denver.com68.86.103.1 3 8ms 8ms 0% 374 / 377 6ms / 44ms
* Unknown Host * 68.86.103.146 4 7ms 7ms 1% 373 / 377 5ms / 69ms
* Unknown Host * 12.116.159.13 5 7ms 8ms 0% 374 / 377 6ms / 57ms
tbr1013801.dvmco.ip.att.net 12.123.207.138 6 41ms 100% 0 / 377
tbr2-cl31.sffca.ip.att.net 12.122.12.133 7 34ms 100% 0 / 376
ggr3-ge90.sffca.ip.att.net 12.122.82.149 8 30ms 100% 0 / 376
* Unknown Host * 192.205.33.78 9 32ms 40ms 1% 369 / 376 31ms / 227ms
* Unknown Host * 4.71.112.14 10 32ms 34ms 1% 371 / 376 31ms / 77ms
g-1-0-0-p171.msr2.sp1.yahoo.com 216.115.107.87 11 36ms 36ms 1% 371 / 376 33ms / 91ms
te-8-1.bas-a1.sp1.yahoo.com 209.131.32.17 12 35ms 37ms 1% 370 / 376 33ms / 54ms
f1.www.vip.sp1.yahoo.com 209.131.36.158 13 34ms 35ms 1% 371 / 376 32ms / 101ms
----------------------------------------------------------

ping pacific.owo.com
pinging while playing
10-05-06
8:30-9:05 PM


Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 0.0.0.0 1 0ms
GE-2-4-ur01.denver.co.denver.comc68.86.104.185 2 7ms 9ms 1% 596 / 603 5ms / 169ms
10g-8-3-ar01.denver.co.denver.com68.86.103.1 3 6ms 8ms 0% 598 / 603 5ms / 82ms
* Unknown Host * 68.86.103.150 4 6ms 8ms 0% 598 / 603 5ms / 40ms
* Unknown Host * 12.124.158.17 5 6ms 8ms 0% 597 / 603 6ms / 53ms
tbr1-p013302.dvmco.ip.att.net 12.123.207.162 6 35ms 100% 0 / 602
tbr2-cl31.sffca.ip.att.net 12.122.12.133 7 33ms 100% 0 / 602
* Unknown Host * 12.123.12.61 8 33ms 100% 0 / 602
* Unknown Host * 12.119.139.10 9 37ms 36ms 89% 66 / 602 31ms / 152ms
* Unknown Host * 159.153.192.230 10 37ms 36ms 1% 592 / 602 32ms / 183ms
central-aw5.owo.com 159.153.209.54 11 35ms 33ms 1% 595 / 602 31ms / 102ms

-------------------------------------------------------------


pinging while playing
10-05-06
8:30-9:05 PM

Reply from 209.131.36.158: bytes=32 time=34ms TTL=51
Reply from 209.131.36.158: bytes=32 time=35ms TTL=51
Reply from 209.131.36.158: bytes=32 time=33ms TTL=52
Reply from 209.131.36.158: bytes=32 time=33ms TTL=51
Reply from 209.131.36.158: bytes=32 time=34ms TTL=52
Reply from 209.131.36.158: bytes=32 time=34ms TTL=51
Reply from 209.131.36.158: bytes=32 time=34ms TTL=51
Reply from 209.131.36.158: bytes=32 time=34ms TTL=51
Request timed out.
Request timed out.
Request timed out.
Reply from 209.131.36.158: bytes=32 time=36ms TTL=51
Reply from 209.131.36.158: bytes=32 time=34ms TTL=51
Reply from 209.131.36.158: bytes=32 time=34ms TTL=51
Reply from 209.131.36.158: bytes=32 time=34ms TTL=52
Reply from 209.131.36.158: bytes=32 time=34ms TTL=50
Reply from 209.131.36.158: bytes=32 time=33ms TTL=51
Reply from 209.131.36.158: bytes=32 time=32ms TTL=52
Reply from 209.131.36.158: bytes=32 time=35ms TTL=51
Reply from 209.131.36.158: bytes=32 time=39ms TTL=52
Reply from 209.131.36.158: bytes=32 time=41ms TTL=50
Reply from 209.131.36.158: bytes=32 time=37ms TTL=52
Reply from 209.131.36.158: bytes=32 time=35ms TTL=51
Request timed out.
Request timed out.
Reply from 209.131.36.158: bytes=32 time=33ms TTL=52
Reply from 209.131.36.158: bytes=32 time=35ms TTL=51
Reply from 209.131.36.158: bytes=32 time=33ms TTL=51
Reply from 209.131.36.158: bytes=32 time=32ms TTL=52
Reply from 209.131.36.158: bytes=32 time=34ms TTL=51
Reply from 209.131.36.158: bytes=32 time=36ms TTL=50

Ping statistics for 209.131.36.158:
Packets: Sent = 3709, Received = 3672, Lost = 37 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 365ms, Average = 35ms

-----------------------------------------------

pinging while playing
10-01-06
6:30-6:35 PM


Pinging central-aw5.owo.com [159.153.209.54] with 32 bytes of data:

Request timed out.
Request timed out.
Reply from 159.153.209.54: bytes=32 time=33ms TTL=50
Reply from 159.153.209.54: bytes=32 time=37ms TTL=50

Ping statistics for 159.153.209.54:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 37ms, Average = 35ms

============================
Currently




gar187er
I DID this for a living
join:2006-06-24
Seattle, WA

gar187er

Member

how are your d/l speeds?

and I dont mean from a speedtest!

from the looks of it , it seems like you hitting a bad ATT hop...
Sillycatnip
join:2006-10-24

Sillycatnip

Member

It's average at best. Comcast is the only decent provider in my state... it's Comcast or Low speed DSL. I was told last night there is nothing they will do.

I went to the comcast forums and someone in a differnt city was having the same issues at the same hop (5).

I was under the impression that ATT owned comcast and was contracted to use the same NODs (towers)... is this not true?

If it is a problem with ATT, what can I do?
Sillycatnip

Sillycatnip

Member

Not sure if this will help, but here are a few other related posts

A post made on 10/16/06 on Comcast.net forums
==============================
If you look closely the tracert's shows a split AFTER tbr2-p013702.dvmco.ip.att.net [12.123.207.150] , this is AT&T...which is under comcast control. Clearly COMCAST has the ability to correct this issue....so my question is WHY is everyone in Colorado routing through California to go EAST? Please look into this issue and correct the routing problem and explain why the fastest way to a server results in a higher ping....

Thanks
Mike

Tracert from 9/16/06 and today:
Tracing route to 8.6.74.182 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 23 ms * 11 ms 68.86.105.137
4 * 13 ms * 10g-9-3-ur02.wheatridge.co.denver.comcast.net [6
8.86.103.65]
5 12 ms * 15 ms 10g-9-1-ur01.wheatridge.co.denver.comcast.net [6
8.86.103.117]
6 14 ms 12 ms 11 ms 10g-9-3-ar01.denver.co.denver.comcast.net [68.86
.103.17]
7 10 ms 14 ms 24 ms 68.86.103.146
8 11 ms 26 ms 12 ms 12.125.159.89
9 37 ms 35 ms 35 ms tbr1-p013704.dvmco.ip.att.net [12.123.207.146]
10 39 ms 38 ms 50 ms tbr2-cl31.sffca.ip.att.net [12.122.12.133]
11 39 ms 40 ms 37 ms ggr2-p3140.sffca.ip.att.net [12.123.12.30]
12 47 ms 37 ms 38 ms so-8-1.car3.SanJose1.Level3.net [209.0.227.29]
13 51 ms 39 ms 38 ms ae-1-55.bbr1.SanJose1.Level3.net [4.68.123.129]

14 72 ms 74 ms 72 ms so-0-0-0.mp1.StLouis1.Level3.net [64.159.0.53]
15 86 ms 84 ms * ge-7-2.hsa1.StLouis1.Level3.net [64.159.4.142]
16 283 ms 90 ms 74 ms 8.6.74.182
=======================================

A different poster

Tracert:
Tracing route to www.comcast.net [204.127.205.8]
over a maximum of 30 hops:
1 * * * Request timed out.
2 7 ms * 8 ms ge-2-5-ur01.arvada.co.denver.comcast.net [68.86.105.33]
3 * * 7 ms 10g-9-1-ur02.arvada.co.denver.comcast.net [68.86.103.126]
4 8 ms 8 ms 23 ms 10g-8-2-ar01.aurora.co.denver.comcast.net [68.86.103.41]
5 7 ms 9 ms 7 ms 68.86.103.178
6 176 ms 192 ms 189 ms 12.116.47.209
7 221 ms 217 ms 230 ms tbr2013801.dvmco.ip.att.net [12.123.207.142]
8 47 ms 48 ms 48 ms tbr1-cl32.cgcil.ip.att.net [12.122.10.117]
9 45 ms 47 ms 46 ms tbr1-cl14.n54ny.ip.att.net [12.122.10.1]
10 226 ms 234 ms 216 ms 12.122.81.245
11 49 ms 47 ms 47 ms mdf1-gsr12-2-pos-6-0.nyc3.attens.net [12.122.255.130]
12 49 ms 48 ms 50 ms 63.240.64.102
13 * * * Request timed out.
14 * * * Request timed out.
15 48 ms 46 ms 48 ms www.comcast.net [204.127.205.8]
Trace complete.
Sillycatnip

Sillycatnip

Member

anyone have any ideas?
bora9
join:2006-10-29
Littleton, CO

bora9

Member

I have the same issue... I live in Littleton. We had a gaming server in Chicago and I too was routed from Denver to San Jose CA, back to Denver, then to Chicago. Dallas servers I'm routed directly to them. But as of the last week, I'm getting massive lag due to the ATT router issue.

I know that doesn't help ya but I'm in the same boat