Correct answers are available for this post.
Very Poor Connection to World of Warcraft servers
owleyes23
Enthusiast - Level 2
‎10-25-2012 11:46 AM

Hello out there,

I have recently restarted my WOW account and now am being faced with latency issues that are impossible to play with.  I used to play about 2 years ago and never had this issue before.  I have tried everything on my end to fix this (hardware reboots,  port forwarding, deleting port forwarding,  disabling AV software, firewalls,  the list goes on and on) all with no result.

I believe this issue is in the traceroute that I ran while in a very high latency situation in game.  The results are as follows:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>tracert 1991076168

Tracing route to node-kso.pool-118-173.dynamic.totbb.net [118.173.105.72]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  dslrouter.westell.com [192.168.1.1]
  2    28 ms    28 ms    27 ms  10.5.94.1
  3    28 ms    28 ms    27 ms  P0-3-1-0.CMDNNJ-LCR-21.verizon-gni.net [130.81.1
95.104]
  4    35 ms    97 ms    33 ms  xe-2-0-6-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
209.140]
  5    32 ms    32 ms    32 ms  0.xe-6-0-2.XL3.EWR6.ALTER.NET [152.63.5.29]
  6   118 ms   118 ms   118 ms  0.xe-11-1-0.XL3.LAX1.ALTER.NET [152.63.112.42]
  7   114 ms   115 ms   113 ms  GigabitEthernet6-0-0.IG2.LAX1.ALTER.NET [152.63.
112.125]
  8   117 ms   115 ms   128 ms  hgc.com-gw.customer.alter.net [152.179.103.18]
  9   307 ms   305 ms   306 ms  po4-0-0-knl-core-02.totiig.net [180.180.248.201]

 10   324 ms   324 ms   323 ms  ten-gi-8-2.kkm-ac-01.totiig.net [203.190.251.238
]
 11   323 ms   323 ms   324 ms  ten-gi-8-1.kkm-ac01.totiig.net [203.190.250.194]

 12   321 ms   320 ms   322 ms  po200-totisp-kkm-ac-01.totiig.net [203.190.250.1
74]
 13   338 ms   334 ms   334 ms  bun-eth-100.cwt-core-03.totisp.net [203.114.118.
6]
 14   334 ms   335 ms   333 ms  node-5i.203-114-118.static.totisp.net [203.114.1
18.198]
 15   331 ms   332 ms   331 ms  node-cl.118-174.static.totisp.net [118.174.225.1
97]
 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   370 ms   370 ms   388 ms  node-kso.pool-118-173.dynamic.totbb.net [118.173
.105.72]

Trace complete.

C:\Windows\system32>
C:\Windows\system32>

 
  

The thing is I know that all the 300+ ms hops are way to high, however I do not know how to fix that.  Any help would be greatly appriciated!!

Thanks So much for your time!

Jay~

Here is my router/transciever info:

Transceiver Statistics
Transceiver Revision A2pB020b3.d20h
Vendor ID Code 4D54
Line Mode ADSL_G.dmt
Data PathINTERLEAVED
 
Transceiver InformationDown Stream PathUp Stream Path
DSL Speed (Kbits/Sec)3360864
Margin (dB)25.111.0
Line Attenuation (dB)31.015.0
Transmit Power (dBm)8.2

11.9

0 Likes
Reply
6 Replies
Correct answers are available for this post.
Re: Very Poor Connection to World of Warcraft servers
owleyes23
Enthusiast - Level 2
‎10-25-2012 12:22 PM

Ok,  so a quick update.

Just ran another traceroute and this one is even worse.....

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Jay>tracert 1991076168

Tracing route to node-kso.pool-118-173.dynamic.totbb.net [118.173.105.72]
over a maximum of 30 hops:

  1     3 ms     1 ms     1 ms  dslrouter.westell.com [192.168.1.1]
  2    28 ms    26 ms    27 ms  10.5.94.1
  3    29 ms    28 ms    28 ms  P0-3-1-0.CMDNNJ-LCR-21.verizon-gni.net [130.81.1
95.104]
  4   102 ms    32 ms    32 ms  xe-2-0-6-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
209.140]
  5    33 ms    32 ms    49 ms  0.xe-6-0-2.XL3.EWR6.ALTER.NET [152.63.5.29]
  6   121 ms   118 ms   117 ms  0.xe-11-1-0.XL3.LAX1.ALTER.NET [152.63.112.42]
  7   115 ms   113 ms   114 ms  GigabitEthernet6-0-0.IG2.LAX1.ALTER.NET [152.63.
112.125]
  8   117 ms   116 ms   117 ms  hgc.com-gw.customer.alter.net [152.179.103.18]
  9   305 ms   304 ms   304 ms  po4-0-0-knl-core-02.totiig.net [180.180.248.201]

 10   624 ms   324 ms   578 ms  ten-gi-8-2.kkm-ac-01.totiig.net [203.190.251.238
]
 11   691 ms   454 ms   465 ms  ten-gi-8-1.kkm-ac01.totiig.net [203.190.250.194]

 12   321 ms   321 ms   321 ms  po200-totisp-kkm-ac-01.totiig.net [203.190.250.1
74]
 13   335 ms   340 ms   334 ms  bun-eth-100.cwt-core-03.totisp.net [203.114.118.
6]
 14   337 ms   334 ms   335 ms  node-5i.203-114-118.static.totisp.net [203.114.1
18.198]
 15   332 ms   332 ms   332 ms  node-cl.118-174.static.totisp.net [118.174.225.1
97]
 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   370 ms   370 ms   371 ms  node-kso.pool-118-173.dynamic.totbb.net [118.173
.105.72]

Trace complete.

C:\Users\Jay>

This is frustrating to say the least....

jay~

0 Likes
Reply
Correct answers are available for this post.
Re: Very Poor Connection to World of Warcraft servers
smith6612
Super User
Super User
‎10-26-2012 05:12 AM

Those don't look like official Blizzard servers to me. TOTBB is a Thailand Telecom company and what you're hitting is someone's connection. Are you sure you have the correct IP address for Blizzard's servers and are not instead playing on a Private server or going through a proxy?

Blizzard's servers are all found on AT&T's network, and as such you should be hopping onto AT&T's network in New Jersey or in New York City, and from there hitting the BattleNet East Coast servers, not going from Newark, New Jersey to Los Angeles, CA (Internet Exchange) to Thailand.

Reply
Correct answers are available for this post.
Re: Very Poor Connection to World of Warcraft servers
owleyes23
Enthusiast - Level 2
‎10-26-2012 10:57 AM

certainly not on a private server.  I got the ip address from them right off of WowWikia server datacenter info.  I play on Norganna (PVE) realm.

I was wondering the same thing though because the server name was supposed to have attens in it somewhere and I didnt see it there.

I guess I need to do some more digging for a bit.  Thanks for the reply!

0 Likes
Reply
Correct answers are available for this post.
Re: Very Poor Connection to World of Warcraft servers
smith6612
Super User
Super User
‎10-26-2012 09:09 PM

Sounds good. Definitely check for anything proxy related. That could include Tor, or Hotspot Shield if you have ever used that before. On Verizon, here's what a trace to that specific realm should look like:

Tracing route to 199.107.6.168 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.3.1
  2     6 ms     7 ms     7 ms  10.41.15.1
  3     7 ms     6 ms     7 ms  P2-0.BFLONY-LCR-01.verizon-gni.net [130.81.44.232]
  4    20 ms    19 ms    19 ms  P11-0-0.BFLONY-LCR-02.verizon-gni.net [130.81.27.63]
  5    20 ms    19 ms    31 ms  so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
  6    20 ms    20 ms    20 ms  ge-8-3-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.82]
  7    26 ms    20 ms    20 ms  0.ae1.BR2.NYC4.ALTER.NET [152.63.18.37]
  8    20 ms    20 ms    23 ms  192.205.36.57
  9    25 ms    22 ms    22 ms  cr2.n54ny.ip.att.net [12.122.86.10]
 10    21 ms    22 ms    21 ms  gar1.nw2nj.ip.att.net [12.122.131.81]
 11    22 ms    21 ms    24 ms  12.122.251.10
 12    37 ms    27 ms    22 ms  mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22]
 13     *        *        *     Request timed out.

As Blizzard doesn't allow ICMP Echo into their server network, that's as far as you'll really get.

Reply
Correct answers are available for this post.
Re: Very Poor Connection to World of Warcraft servers
owleyes23
Enthusiast - Level 2
‎10-27-2012 12:25 AM

I did not realize that the "."'s in the ip mattered that much.  When I put them in this is what I get:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>tracert 199.107.6.168

Tracing route to 199.107.6.168 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  dslrouter.westell.com [192.168.1.1]
  2    28 ms    28 ms    31 ms  10.5.94.1
  3    29 ms    28 ms    29 ms  P0-3-1-0.CMDNNJ-LCR-21.verizon-gni.net [130.81.1
95.104]
  4    40 ms    34 ms    32 ms  xe-2-0-6-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
209.140]
  5    45 ms    46 ms    45 ms  so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.8
1.17.6]
  6    45 ms    48 ms    94 ms  0.ae1.BR2.NYC4.ALTER.NET [152.63.18.37]
  7    56 ms    54 ms   110 ms  192.205.36.57
  8    39 ms    38 ms    53 ms  cr1.n54ny.ip.att.net [12.122.86.6]
  9    36 ms    34 ms    34 ms  gar1.nw2nj.ip.att.net [12.122.130.93]
 10    41 ms    38 ms    49 ms  12.122.251.10
 11    37 ms    36 ms    35 ms  mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.24
0.65.22]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *

So I guess maybe it's not the path to the WoW server now.  That leaves me back at square one with no idea where to start looking again =P 

Thanks for your help!!

0 Likes
Reply
Correct answers are available for this post.
Re: Very Poor Connection to World of Warcraft servers
smith6612
Super User
Super User
‎10-27-2012 09:05 PM

You're welcome! 🙂

What's interesting is the fact that 1991076168 even resolved for you. Hmm. Maybe Verizon's DNS servers if you're using them are that weird. Oh well I guess 😕

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\>nslookup 1991076168
Server:  resolver1.opendns.com
Address:  208.67.222.222

*** resolver1.opendns.com can't find 1991076168: Non-existent domain

Reply