Wolf_sd
join:2008-04-14
Spring Valley, CA
edit:
May 16th, @01:06PM
| reply to Dimp
Re: Bad Pings to a California Server (bad hops?)
I'm actually in the same boat here, and a new user here so my apologies upfront. I've had this problem since back in November with WoW and I'm located in San Diego, connecting to the Daggerspine server which is a west coast server. Also to note, I've tried other west coast servers and the same thing happens.
My problem, which seems to be occurring a lot recently is that I'll be playing fine, no spikes or anything, and then the game lags out and I disconnect. Then my internet just lags for a few seconds (can't web browse or reconnect to wow) and then bam, I'm connected again like nothing happened. Afterwards, one of two things happen. Either 1, I relog into wow and instantly lagout again, or 2, the game plays fine like nothing happened. This fit can go on and on over the period of the day, or sometimes happen only once. Regardless it's guaranteed to happen every day.
I've been in contact with both Blizzard tech reps and Cox tech reps via email and even had Cox send someone out to look at my lines. I've done tons of troubleshooting that Blizzard has suggested, and even picked up a new modem and still the problem persists. What's even worse is it seems to only be WoW that the disconnecting occurs. Recently, I sent Blizzard reps my tracerts and pathpings to see if they can troubleshoot better. Below is the data that I emailed to the Blizzard rep.
Tracing route to 12.129.233.88 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 5 ms 6 ms 10.157.0.1
3 14 ms 8 ms 7 ms 68.6.11.154
4 8 ms 7 ms 9 ms fed1dsrj01-ge500.0.rd.sd.cox.net [68.6.8.0]
5 7 ms 9 ms 8 ms te-3-1.car1.SanDiego1.Level3.net [4.79.32.113]
6 25 ms 18 ms 17 ms ae-5-5.ebr1.LosAngeles1.Level3.net [4.69.133.206]
7 14 ms 17 ms 17 ms ae-61-61.csw1.LosAngeles1.Level3.net [4.69.137.2]
8 15 ms 12 ms 9 ms ae-1-69.edge1.LosAngeles1.Level3.net [4.68.20.7]
9 13 ms 12 ms 10 ms 192.205.33.229
10 11 ms 13 ms 13 ms 12.127.3.218
11 15 ms 11 ms 11 ms 12.127.3.185
12 14 ms 13 ms 12 ms 12.122.255.74
13 10 ms 11 ms 20 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
Tracing route to 12.129.233.88 over a maximum of 30 hops
0 CHRIS-II [192.168.1.102]
1 192.168.1.1
2 10.157.0.1
3 68.6.11.154
4 fed1dsrj01-ge500.0.rd.sd.cox.net [68.6.8.0]
5 te-3-1.car1.SanDiego1.Level3.net [4.79.32.113]
6 ae-5-5.ebr1.LosAngeles1.Level3.net [4.69.133.206]
7 ae-61-61.csw1.LosAngeles1.Level3.net [4.69.137.2]
8 ae-1-69.edge1.LosAngeles1.Level3.net [4.68.20.7]
9 192.205.33.229
10 12.127.3.218
11 12.127.3.185
12 12.122.255.74
13 mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
14 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 CHRIS-II [192.168.1.102]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 7ms 13/ 100 = 13% 13/ 100 = 13% 10.157.0.1
0/ 100 = 0% |
3 10ms 1/ 100 = 1% 1/ 100 = 1% 68.6.11.154
0/ 100 = 0% |
4 9ms 1/ 100 = 1% 1/ 100 = 1% fed1dsrj01-ge500.0.rd.sd.cox.net [68.6.8.0]
0/ 100 = 0% |
5 16ms 1/ 100 = 1% 1/ 100 = 1% te-3-1.car1.SanDiego1.Level3.net [4.79.32.113]
0/ 100 = 0% |
6 16ms 1/ 100 = 1% 1/ 100 = 1% ae-5-5.ebr1.LosAngeles1.Level3.net [4.69.133.206]
0/ 100 = 0% |
7 17ms 1/ 100 = 1% 1/ 100 = 1% ae-61-61.csw1.LosAngeles1.Level3.net [4.69.137.2]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% ae-1-69.edge1.LosAngeles1.Level3.net [4.68.20.7]
0/ 100 = 0% |
9 11ms 0/ 100 = 0% 0/ 100 = 0% 192.205.33.229
1/ 100 = 1% |
10 --- 100/ 100 =100% 99/ 100 = 99% 12.127.3.218
0/ 100 = 0% |
11 --- 100/ 100 =100% 99/ 100 = 99% 12.127.3.185
0/ 100 = 0% |
12 --- 100/ 100 =100% 99/ 100 = 99% 12.122.255.74
0/ 100 = 0% |
13 20ms 1/ 100 = 1% 0/ 100 = 0% mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
99/ 100 = 99% |
14 --- 100/ 100 =100% 0/ 100 = 0% CHRIS-II [0.0.0.0]
Trace complete.
This is what a rep had to say:
Thank you for the update. Your traces do not appear to show any problems along the connection just as they did before. However, your ping tests show a complete loss of signal at hops 8 and 10-12. These hops appear to be in and after the Level3 network and are probably located in AT&T's net as well. However, you are a direct customer of Cox so you would need to contact them if your connection was experiencing any issues. They can forward the problem on to the other networks for investigation.
So I contacted Cox via email and they responded with:
Thank you for your e-mail. I understand you are having difficulties
with a trace route. I apologize for any inconvenience this may cause
you.
Unfortunately, We are not allowed to support this difficulty because we
do not have the license agreement to support it. I suggest you contact
the manufacturer for a further assistance regarding this difficulty.
I hope the information above was useful in resolving your difficulty. If
you would like to inquire about other information, do not hesitate to
contact us for further assistance.
I'm really at a loss here. I've tried just about everything I can think of. I've tweaked WoW settings, updated drivers, replaced NIC cards, replaced modem, reinstalled WoW, by passed router, and still nothing. Could anyone offer any insight? |
