Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

High latency when playing WoW


  • Please log in to reply

#1
Flounderpounder

Flounderpounder

    New Member

  • Member
  • Pip
  • 4 posts
Hi, I've recently been encountering some terrible latency when trying to play World of Warcraft (latency of 2000ms - 8000ms). The tech support forum there instructed me to run a tracert to identify the problem. The numbers mean nothing to me, hopefully someone here can tell me what they mean.

Tracing route to us.logon.worldofwarcraft.com [12.129.232.112]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms c-68-58-176-14.hsd1.sc.comcast.net [68.58.176.14]
2 7 ms 7 ms 15 ms 73.30.136.1
3 9 ms 8 ms 10 ms 68.86.144.233
4 9 ms 9 ms 8 ms 10g-9-4-ar02.charleston.sc.chrlstn.comcast.net [68.86.144.85]
5 * 10 ms 8 ms 68.86.144.30
6 19 ms 18 ms 35 ms 12.117.176.53
7 69 ms 82 ms 65 ms tbr2-p013801.attga.ip.att.net [12.123.20.174]
8 * 61 ms 59 ms tbr1-cl13.dlstx.ip.att.net [12.122.2.89]
9 71 ms * 58 ms tbr1-cl20.la2ca.ip.att.net [12.122.10.50]
10 69 ms 58 ms 58 ms 12.123.222.89
11 60 ms 60 ms 70 ms mdf1-gsr12-1-pos-6-0.lax1.attens.net [12.122.255.102]
12 80 ms 74 ms 82 ms mdf1-bi8k-2-eth-2-4.lax1.attens.net [12.129.192.54]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
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.


I've run run several of these and the results are pretty consistent.
  • 0

Advertisements


#2
Dan

Dan

    Trusted Tech

  • Retired Staff
  • 1,771 posts
Hi Flounderpounder,

You're definitely losing packets. Please download PingPlotter. Run it and perform a search to us.logon.worldofwarcraft.com -- Once it is finished, click on 'Edit', and then select 'Copy as Text'. Paste the results here.

Please also try performing another tracert, but this time to Google.com. Is your computer on a network? If so, how many other computers are there? Please try to do a tracert from one of these other computers and post the results.

Please also try restarting your computer into Safe Mode with Networking, and then perfom the tracert (to the WoW Server) once again; post the results.

How to restart into Safe Mode with Networking
Please restart your computer and as soon as it starts booting up again continuously tap F8. A menu should come up where you will be given the option to enter Safe Mode, Safe Mode with Command Prompt and Safe Mode with Networking (along with a few others). Please tap the down key until you reach Safe Mode with Networking, and then press the Enter key. Your computer should now boot into Safe Mode with Networking.
  • 0

#3
Flounderpounder

Flounderpounder

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Thanks for the reply,

To answer your questions, I am networked with 3 computers though a router then to the cable modem. I have tried resetting both the modem and router with no improvement. I've also reset the modem and hooked directly to it with no improvement.

pingplotter:

Target Name: us.logon.worldofwarcraft.com
IP: 12.129.232.113
Date/Time: 6/19/2006 12:07:27 PM

1 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms c-68-58-176-14.hsd1.sc.comcast.net [68.58.176.14]
2 8 ms 9 ms 8 ms 39 ms 12 ms 15 ms 24 ms 17 ms 7 ms [73.30.136.1]
3 10 ms 16 ms 7 ms 13 ms 8 ms 9 ms 16 ms 18 ms 9 ms [68.86.144.233]
4 10 ms 7 ms 10 ms 10 ms 20 ms 12 ms 30 ms 32 ms 12 ms 10g-9-4-ar02.charleston.sc.chrlstn.comcast.net [68.86.144.85]
5 9 ms 8 ms 9 ms 13 ms 18 ms 9 ms 16 ms 29 ms 10 ms [68.86.144.30]
6 19 ms 19 ms 18 ms 28 ms 27 ms 21 ms 21 ms 34 ms 32 ms [12.118.120.21]
7 59 ms 59 ms 59 ms 75 ms 65 ms 60 ms 69 ms 72 ms * tbr2-p013901.attga.ip.att.net [12.123.20.182]
8 62 ms 59 ms 57 ms 74 ms 71 ms 64 ms 70 ms 67 ms 733 ms tbr1-cl13.dlstx.ip.att.net [12.122.2.89]
9 75 ms 57 ms 58 ms 71 ms 59 ms 67 ms 62 ms 59 ms * tbr1-cl20.la2ca.ip.att.net [12.122.10.50]
10 58 ms 56 ms 61 ms 60 ms 59 ms 61 ms 73 ms 58 ms * [12.123.222.89]
11 62 ms 57 ms 65 ms 61 ms 59 ms 71 ms 68 ms 65 ms 58 ms mdf1-gsr12-1-pos-6-0.lax1.attens.net [12.122.255.102]
12 * 58 ms 60 ms 60 ms * 71 ms 83 ms 58 ms * mdf1-bi8k-1-eth-1-1.lax1.attens.net [12.129.192.238]
13 * * * * * * * * * [-]

Here is a trace to google from my computer:

Tracing route to google.com [64.233.187.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms c-68-58-176-14.hsd1.sc.comcast.net [68.58.176.14]
2 6 ms 5 ms 7 ms 73.30.136.1
3 9 ms 8 ms 8 ms 68.86.144.245
4 12 ms 7 ms 8 ms 10g-8-2-ar01.charleston.sc.chrlstn.comcast.net [68.86.144.89]
5 49 ms 170 ms 8 ms 68.86.144.26
6 24 ms 19 ms 18 ms 12.117.176.53
7 21 ms 18 ms 18 ms tbr1-p013701.attga.ip.att.net [12.123.20.170]
8 19 ms 18 ms 17 ms 12.122.81.97
9 21 ms 23 ms 23 ms 192.205.33.38
10 34 ms 44 ms 35 ms 64.124.229.173.google.com [64.124.229.173]
11 49 ms 41 ms 34 ms 72.14.236.175
12 65 ms 43 ms 37 ms 216.239.49.226
13 35 ms 34 ms 35 ms 64.233.187.99
Trace complete.

I'll try restarting in safemode now and post those results and also a trace from another computer on the network.

Thanks
  • 0

#4
Flounderpounder

Flounderpounder

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Here are the tracert results when running in safemode:

Tracing route to us.logon.worldofwarcraft.com [12.129.232.116]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms c-68-58-176-14.hsd1.sc.comcast.net [68.58.176.14]
2 7 ms 6 ms 7 ms 73.30.136.1
3 9 ms 10 ms 9 ms 68.86.144.245
4 11 ms 9 ms 9 ms 10g-8-2-ar01.charleston.sc.chrlstn.comcast.net [68.86.144.89]
5 * 11 ms 7 ms 68.86.144.26
6 26 ms 19 ms 23 ms 12.118.120.21
7 60 ms 60 ms 61 ms tbr2-p013901.attga.ip.att.net [12.123.20.182]
8 62 ms 68 ms 62 ms tbr1-cl13.dlstx.ip.att.net [12.122.2.89]
9 63 ms 64 ms 76 ms tbr1-cl20.la2ca.ip.att.net [12.122.10.50]
10 59 ms 65 ms 69 ms 12.123.222.89
11 82 ms 74 ms 69 ms mdf1-gsr12-1-pos-6-0.lax1.attens.net [12.122.255.102]
12 89 ms 85 ms 90 ms mdf1-bi8k-2-eth-2-3.lax1.attens.net [12.129.192.118]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
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.

Tracing route to google.com [64.233.187.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms c-68-58-176-14.hsd1.sc.comcast.net [68.58.176.14]
2 15 ms 18 ms 21 ms 73.30.136.1
3 7 ms 14 ms 10 ms 68.86.144.245
4 8 ms 9 ms 9 ms 10g-8-2-ar01.charleston.sc.chrlstn.comcast.net [68.86.144.89]
5 10 ms 22 ms 8 ms 68.86.144.26
6 31 ms 33 ms 30 ms 12.117.176.53
7 19 ms 29 ms 24 ms tbr1-p013701.attga.ip.att.net [12.123.20.170]
8 28 ms 18 ms 26 ms 12.122.81.97
9 28 ms 32 ms 57 ms 192.205.33.38
10 * 48 ms 41 ms 64.124.229.173.google.com [64.124.229.173]
11 34 ms 33 ms 32 ms 72.14.236.175
12 50 ms 44 ms 42 ms 216.239.49.226
13 55 ms 43 ms 39 ms 64.233.187.99
Trace complete.

And this is the tracert from another computer on the network:

Tracing route to us.logon.worldofwarcraft.com [12.129.232.109]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms c-68-58-176-14.hsd1.sc.comcast.net
[68.58.176.14]
2 11 ms 8 ms 10 ms 73.30.136.1
3 16 ms 13 ms 16 ms 68.86.144.233
4 10 ms 11 ms 8 ms
10g-8-2-ar01.charleston.sc.chrlstn.comcast.net [68.86.144.89]
5 13 ms 10 ms 11 ms 68.86.144.26
6 24 ms 31 ms 25 ms 12.118.120.21
7 70 ms 65 ms 62 ms tbr2-p013901.attga.ip.att.net
[12.123.20.182]
8 60 ms 71 ms 60 ms tbr1-cl13.dlstx.ip.att.net
[12.122.2.89]
9 58 ms 59 ms 62 ms tbr1-cl20.la2ca.ip.att.net
[12.122.10.50]
10 69 ms 69 ms 70 ms 12.123.222.89
11 74 ms 66 ms 62 ms mdf1-gsr12-1-pos-6-0.lax1.attens.net
[12.122.255.102]
12 81 ms 85 ms 84 ms mdf1-bi8k-2-eth-2-3.lax1.attens.net
[12.129.192.118]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
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.

Tracing route to google.com [64.233.187.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms c-68-58-176-14.hsd1.sc.comcast.net
[68.58.176.14]
2 9 ms 10 ms 9 ms 73.30.136.1
3 22 ms 20 ms 24 ms 68.86.144.245
4 8 ms 8 ms 7 ms
10g-8-2-ar01.charleston.sc.chrlstn.comcast.net [68.86.144.89]
5 18 ms 42 ms 16 ms 68.86.144.26
6 39 ms 73 ms 54 ms 12.117.176.53
7 27 ms 24 ms 21 ms tbr1-p013701.attga.ip.att.net
[12.123.20.170]
8 22 ms 19 ms 18 ms 12.122.81.97
9 19 ms 23 ms 23 ms 192.205.33.38
10 36 ms 36 ms 39 ms 64.124.229.173.google.com
[64.124.229.173]
11 36 ms 33 ms 37 ms 72.14.236.175
12 45 ms 43 ms 37 ms 216.239.49.226
13 * 42 ms 46 ms 64.233.187.99
Trace complete.
  • 0

#5
Dan

Dan

    Trusted Tech

  • Retired Staff
  • 1,771 posts
Well, from what I can see there are no spikes in any of your jumps. What is the normal latency you usually receive when connected to WoW? From the looks of things it should really be well under 500.

The only problem with any of your traces is the dropped packets -- this happened on both computers and is therefore not specific to your computer. That suggests that it's either the hardware, or your ISP. I'd be inclined to say that it's your ISP, as the packets are all being dropped down the line. I'd suggest that you give your ISP a call and ask them to check your line; also tell them about the tracert's and the dropped packets (for your information, a * indicates a dropped packet). It also seems to drop packets at random addresses.

In my opinion, I feel that this is a ISP issue, but I could be wrong.. However it won't hurt to give them a call :whistling:
  • 0

#6
Flounderpounder

Flounderpounder

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Thanks again for the reply. I finally got an e-mail back from the World of Warcraft tech support and they came to the same conclussion after looking at the trace that it is a problem with my ISP. I gave comcast a call today and was told that they had no controll over my packet loss and that they don't support gamming. Now I'm frustrated and am wondering why I pay so much every month for Comcasts service D:

Anyway, nothing more I can do I suppose.
  • 0

#7
Dan

Dan

    Trusted Tech

  • Retired Staff
  • 1,771 posts
:whistling: Um.. Your ISP are morons. The dropped packets have absolutely nothing to do with gaming -- you dropped packets whilst connecting to GOOGLE. I'd give them another call and tell them that you're losing packets when connecting to the Internet; don't mention WoW. Just keep on bringing up Google. Unless of course, your ISP doesn't support the Internet..?

I think they're just trying to dodge a bullet on this one. You could at the very least ask them if they're doing any updates/maintanence anywhere that could be affecting your connection, or even ask if you can be put put on a different route, to see if it's specific locations causing the problem. They're just being slack and don't want to look into this.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP