aree
join:2008-05-26
Bronx, NY
1 edit | reply to ansky08
Re: Lag, Disconnecting in World of Warcraft
I been having this problem for about 3 months already; whenever I start to raid BlackTemple or Sunwell. My latency starts from 200ms to 20k ms then i just DC and lose all internet connection with my phone too which is VoIP. I first though it was my addon/UI or my computer; well I deleted all my addons/ WTF folder and that didnt work; so i reinstalled Wow and that didn't work. Then I though it could be my computer; so I rebuilded it again and that didn't work. At that point I call my ISP and told them my problem, I have had 6 Optimum Online techs come different times to my house and they couldn't find the problem with my internet. Until one of the higher level tech referred my problem to the engineers. They came 4 different times over to fix the problem; but I yet to see any improvements. After reading some of the other Wow players DC's problems on the forums, it looks like WoW doesn't like Motorola SBV5120, so every time I login I lose all internet and phone connection because of Wow. I already told my ISP about the game and what I found out about Motorola SBV5120 not liking WoW; said they are going to look in to it and contact blizz. This is just getting out of hand, blizz and Optimum Online needs together and fix this problem. Theirs alot of players with this problem, not only with type of modem but with DC'ing since the last few patchs.
ISP - Optimum Online/Cablevision
DSL/Cable Modem (and firmware if available) -Motorola SBV5120-2.10.1.7-SCM04-SHSF
Router (and firmware if available) - Dlink DGL-4100, but I don't use it since the dc'ing started
Any other intermediate network devices (hubs, switches, Power over Ethernet, etc) - No
Connection type - wired
Operating System -XP
Geographical Location - Bronx, NY
Tracert -
Tracing route to 206.16.23.128 over a maximum of 30 hops
1 6 ms 5 ms 6 ms 10.240.184.73
2 7 ms 5 ms 5 ms ool-4353e322.dyn.optonline.net [67.83.227.34]
3 * * * Request timed out.
4 8 ms 7 ms 8 ms rtr4-tg10-2.wan.whplny.cv.net [64.15.8.29]
5 * * * Request timed out.
6 * * * Request timed out.
7 10 ms 7 ms 7 ms po9-1.core01.jfk02.atlas.cogentco.com [154.54.2.129]
8 7 ms 8 ms 8 ms te3-2.mpd03.jfk02.atlas.cogentco.com [154.54.5.238]
9 15 ms 16 ms 14 ms te2-1.mpd01.dca01.atlas.cogentco.com [154.54.6.5]
10 16 ms 15 ms 15 ms vl3492.mpd01.dca02.atlas.cogentco.com [66.28.4.86]
11 16 ms 15 ms 15 ms vl3496.mpd01.iad01.atlas.cogentco.com [154.54.5.46]
12 16 ms 16 ms 15 ms 192.205.35.105
13 58 ms 57 ms 58 ms tbr1.wswdc.ip.att.net [12.123.8.130]
14 57 ms 57 ms 58 ms cr2.wswdc.ip.att.net [12.122.16.45]
15 65 ms 57 ms 57 ms cr1.attga.ip.att.net [12.122.1.173]
16 58 ms 57 ms 57 ms cr2.dlstx.ip.att.net [12.122.28.174]
17 58 ms 59 ms 57 ms tbr2.dlstx.ip.att.net [12.122.18.230]
18 59 ms 60 ms 59 ms br2.dlstx.ip.att.net [12.123.16.213]
19 58 ms 57 ms 57 ms mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
20 58 ms 57 ms 57 ms mdf002fbi8ks0001-eth-1-4.dal1.attens.net [63.241.192.126]
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete. |
|
Akka
@optonline.net
| I have the same issue, im playing normaly and all of a sudden my latency just shots up and i get disconected from wow (all my other stuff works fine... like teamspeak and browsing... it's just WoW)
Anyway here is my trace route
Tracing route to 63.241.255.47 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 8 ms 10 ms 10.82.64.1
3 10 ms 9 ms 22 ms dstswr1-vlan2.rh.cftnnj.cv.net [67.83.244.33]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 13 ms 12 ms 22 ms vl3491.ccr04.jfk02.atlas.cogentco.com [154.54.7.9]
9 40 ms 44 ms 39 ms te4-3.ccr02.ord01.atlas.cogentco.com [154.54.1.190]
10 51 ms 56 ms 52 ms te4-2.ccr02.mci01.atlas.cogentco.com [154.54.6.253]
11 58 ms 57 ms 61 ms te8-4.ccr02.dfw01.atlas.cogentco.com [154.54.5.169]
12 61 ms 60 ms 65 ms vl3490.ccr02.dfw03.atlas.cogentco.com [154.54.6.98]
13 69 ms 73 ms 61 ms gi2-0-0.core01.dfw03.atlas.cogentco.com [154.54.7.34]
14 63 ms 61 ms 62 ms 192.205.32.253
15 63 ms 60 ms 64 ms tbr2.dlstx.ip.att.net [12.123.16.206]
16 60 ms 61 ms 60 ms br2.dlstx.ip.att.net [12.123.16.213]
17 65 ms 61 ms 62 ms 12.122.255.226
18 62 ms 68 ms 65 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete. |
|
digi
@optonline.net
| Unfortunately, this problem is still a problem. The threads on blizzard's wow forums still have people reporting problems by the hour.
Tracert below, also please keep in mind that the problem is highly intermittent (in between lag events my in-game server latency is 150ms) and it's pretty unlikely that this tracert is illustrating any packet loss.
Tracing route to 206.17.111.123 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 11 ms 9 ms 8 ms 10.95.192.1
3 7 ms 9 ms 7 ms dstswr2-vlan2.rh.wrrnnj.cv.net [67.83.251.162]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 11 ms 13 ms 13 ms vl3491.ccr04.jfk02.atlas.cogentco.com [154.54.7.
9]
9 17 ms 21 ms 17 ms te8-2.ccr02.dca01.atlas.cogentco.com [66.28.4.12
6]
10 17 ms 17 ms 16 ms te7-3.mpd01.dca02.atlas.cogentco.com [154.54.6.2
6]
11 18 ms 15 ms 18 ms vl3497.mpd01.iad01.atlas.cogentco.com [154.54.5.
66]
12 19 ms 17 ms 19 ms 192.205.35.105
13 30 ms 32 ms 31 ms tbr1.wswdc.ip.att.net [12.122.80.58]
14 29 ms 28 ms 30 ms cr2.wswdc.ip.att.net [12.122.16.61]
15 31 ms 31 ms 30 ms cr2.n54ny.ip.att.net [12.122.3.37]
16 29 ms 32 ms 28 ms cr1.cb1ma.ip.att.net [12.122.31.126]
17 29 ms 30 ms 30 ms tbr1.cb1ma.ip.att.net [12.122.20.130]
18 30 ms 47 ms 34 ms 12.127.5.93
19 30 ms 31 ms 29 ms 12-122-254-14.attens.net [12.122.254.14]
20 176 ms 203 ms 200 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.13
0.0.170]
21 * * * Request timed out.
|
|
digi
@optonline.net
| I ran two simultaneous pings to two different destinations along my tracert above until I found a spot where packets continue to pass normally on one and are lost downstream on another. As you can (hopefully) see in the attachment, the packets are lost between 67.83.251.162 (hop 3) and 192.205.35.105 (hop 12). Unfortunately none of the intermediate hops (cogent's routers) respond to pings, so I can't run the same test to narrow it down. However, its obvious from this that the problem occurs *before* att and after ool. As you can see, the period of dropped packets is very short (3-4 seconds max) and the occurrence of these 'lag events' is few and far between (every 5 or 10 minutes), so it will be difficult to pick up on many diagnostic tools. |
|
