Stuck at "Logging in to game server"

80 Blood Elf Mage
2675
Hey there, I'm getting stuck at "logging in to game server" no matter what realm I pick.

I did a traceroute for the server i would like to be on, Azuremyst.

traceroute to 199.107.24.252 (199.107.24.252), 64 hops max, 52 byte packets
1 10.60.0.1 (10.60.0.1) 10.383 ms 7.386 ms 6.602 ms
2 192.168.200.1 (192.168.200.1) 8.633 ms 22.750 ms 8.888 ms
3 24.139.16.157 (24.139.16.157) 17.471 ms 18.919 ms 22.494 ms
4 24.139.7.77 (24.139.7.77) 31.657 ms 31.733 ms 32.499 ms
5 dyn1-natblk1.personainc.net (24.139.5.1) 48.892 ms 56.604 ms 55.105 ms
6 24.139.5.2 (24.139.5.2) 35.896 ms 34.374 ms 35.638 ms
7 dyn1-natblk1.personainc.net (24.139.5.1) 51.788 ms 54.991 ms *
8 24.139.5.2 (24.139.5.2) 39.157 ms 51.315 ms 32.147 ms
9 dyn1-natblk1.personainc.net (24.139.5.1) 55.218 ms 60.333 ms 51.409 ms
10 24.139.5.2 (24.139.5.2) 40.518 ms 34.050 ms 44.926 ms
11 dyn1-natblk1.personainc.net (24.139.5.1) 48.967 ms * 50.568 ms
12 * 24.139.5.2 (24.139.5.2) 31.247 ms 33.215 ms
13 dyn1-natblk1.personainc.net (24.139.5.1) 48.860 ms * *
14 24.139.5.2 (24.139.5.2) 32.234 ms 33.173 ms 35.383 ms
15 * dyn1-natblk1.personainc.net (24.139.5.1) 47.288 ms 49.562 ms
16 24.139.5.2 (24.139.5.2) 35.438 ms * 33.697 ms
17 dyn1-natblk1.personainc.net (24.139.5.1) 47.876 ms * 56.540 ms
18 * 24.139.5.2 (24.139.5.2) 33.594 ms 34.586 ms
19 dyn1-natblk1.personainc.net (24.139.5.1) 57.843 ms 50.010 ms 67.148 ms
20 24.139.5.2 (24.139.5.2) 34.724 ms 32.562 ms 32.398 ms
21 dyn1-natblk1.personainc.net (24.139.5.1) 55.016 ms * *
22 * 24.139.5.2 (24.139.5.2) 34.440 ms *
23 dyn1-natblk1.personainc.net (24.139.5.1) 57.690 ms * *
24 * * 24.139.5.2 (24.139.5.2) 39.579 ms
25 * * *
26 * * *
27 * * *
28 24.139.5.2 (24.139.5.2) 40.442 ms 33.167 ms *
29 * dyn1-natblk1.personainc.net (24.139.5.1) 49.986 ms 66.104 ms
30 24.139.5.2 (24.139.5.2) 35.154 ms 35.125 ms

Any help would be great :)

edit:
did a traceroute on us.logon.battle.net, readout is below

traceroute to us.logon.battle.net (12.129.206.130), 64 hops max, 52 byte packets
1 10.60.0.1 (10.60.0.1) 6.027 ms 6.603 ms 8.815 ms
2 192.168.200.1 (192.168.200.1) 6.986 ms 6.652 ms 6.489 ms
3 208.76.108.21 (208.76.108.21) 14.206 ms 14.536 ms 13.609 ms
4 217.243.218.237 (217.243.218.237) 15.161 ms 15.355 ms 13.706 ms
5 217.239.40.209 (217.239.40.209) 53.836 ms 39.769 ms 40.737 ms
6 192.205.35.177 (192.205.35.177) 28.214 ms 28.082 ms 26.868 ms
7 cr1.cgcil.ip.att.net (12.122.133.18) 93.361 ms 92.121 ms 93.538 ms
8 cr2.dvmco.ip.att.net (12.122.31.85) 92.220 ms 93.056 ms 92.995 ms
9 cr1.slkut.ip.att.net (12.122.30.25) 91.204 ms 92.687 ms 91.959 ms
10 cr2.la2ca.ip.att.net (12.122.30.30) 104.111 ms 91.663 ms 93.525 ms
11 cr84.la2ca.ip.att.net (12.123.30.249) 92.659 ms 93.463 ms 93.317 ms
12 gar5.la2ca.ip.att.net (12.122.129.25) 92.868 ms 91.691 ms 96.260 ms
13 12.122.255.74 (12.122.255.74) 93.020 ms 91.497 ms 92.568 ms
14 mdf001c7613r0003-gig-10-1.lax1.attens.net (12.129.193.242) 92.866 ms
mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246) 93.358 ms 93.563 ms
15 * 12.129.211.38 (12.129.211.38) 97.800 ms !X *
16 12.129.211.38 (12.129.211.38) 94.877 ms !X * 92.376 ms !X
Edited by Polkaroo on 11/27/2010 7:58 AM PST
Reply Quote
Support Forum Agent
What game version are you on?

-Open the Launcher and hit "Play"
-At the login screen, bottom left corner, it should have the game patch/version. It should read "4.0.3 (13329)". If this says anything else, WoW fails to recognize there is a patch update, and you will need to uninstall/reinstall to fix this.
________________________________________________
Account and Technical Services || Mac Tech Support
Tue-Sat 9 AM - 5 PM CST
Can't find a resolution on the forums, contact a Support Rep directly: http://us.blizzard.com/en-us/company/about/contact.html
Do you love Boomkins? Sure, we all do!
Wait I mean, take a moment to let me know how I am doing. http://www.surveymk.com/s/RF8K3KG
Reply Quote
80 Blood Elf Mage
2675
it reads:
Version 4.0.3 (13329) (Release)
Nov 17 2010

edit: just found out that the launcher can't connect to the news server either
Edited by Polkaroo on 11/27/2010 8:21 AM PST
Reply Quote
80 Undead Priest
2270
I'm having similar issues, Polkaroo. The News server didn't connect. I did manage to log on after letting the loading page sit for 10 minutes but when I logged on one character to attempt to log on to another it disconnected me. So, I went back to the Launcher and let it tell me the News Server couldn't connect. I let it sit and load rather than just hitting play and eventually the launcher panel populated with the patch notes. The download bar showed I needed to still download 380mb of something or the other. I'm currently watching the bar chug on the last MB of patch I guess it missed.

@tonyM: 133329 is the version I'm running as well.

ETA: After allowing the 380MB of patch(or whatever) to download I'm experiencing the same issues as outlined before.

Edited by Bsnss on 11/27/2010 9:03 AM PST
Reply Quote
MVP - Technical Support
100 Draenei Mage
7170
If that first traceroute is really to your realm server you have some issues my friend.

It's never even getting near the data center or any AT & T hops in fact (AT& T is the ISP blizzard uses)

According to http://www.wowpedia.org/US_realm_list_by_datacenter either 63.240.65.10 or 63.240.65.14 should be the last hop on your journey.

It's hitting 24.139.5.2 and just continually sending it back and forth between that IP and 24.139.5.1

The traffic that's meant to be going to your realm server is neither actually leaving your ISP :(
Reply Quote
80 Blood Elf Mage
2675
If that first traceroute is really to your realm server you have some issues my friend.

It's never even getting near the data center or any AT & T hops in fact (AT& T is the ISP blizzard uses)

According to http://www.wowpedia.org/US_realm_list_by_datacenter either 63.240.65.10 or 63.240.65.14 should be the last hop on your journey.

It's hitting 24.139.5.2 and just continually sending it back and forth between that IP and 24.139.5.1

The traffic that's meant to be going to your realm server is neither actually leaving your ISP :(


It's odd that only WoW is being effected. Does this mean I have to phone up my ISP and take on the role of an irate customer?
Reply Quote
Support Forum Agent
^^ Blu said what I was going to say before I finished typing it.

The first hop is really high, should not be over 1 most times (anything above 1 but below 10 is pushing it).

I was also asking version number because this issue can also be related to WoW not knowing theres a new patch, and it let's you login but won't do realms due to not correct version.
________________________________________________
Account and Technical Services || Mac Tech Support
Tue-Sat 9 AM - 5 PM CST
Can't find a resolution on the forums, contact a Support Rep directly: http://us.blizzard.com/en-us/company/about/contact.html
Do you love Boomkins? Sure, we all do!
Wait I mean, take a moment to let me know how I am doing. http://www.surveymk.com/s/RF8K3KG
Reply Quote
80 Undead Priest
2270
Here is my traceroute fun:

traceroute to 199.107.24.252 (199.107.24.252), 64 hops max, 52 byte packets
1 199.107.24.252 (199.107.24.252) 6.220 ms 1.623 ms 1.530 ms
2 70.67.44.1 (70.67.44.1) 12.146 ms 10.924 ms 11.728 ms
3 rd1cv-ge5-0-0-2.gv.shawcable.net (64.59.166.66) 12.939 ms 23.069 ms 11.658 ms
4 rd2cv-pos1-0.gv.shawcable.net (66.163.72.6) 12.021 ms 11.843 ms 12.094 ms
5 66.163.78.94 (66.163.78.94) 14.421 ms 15.695 ms 14.470 ms
6 if-2-0-0.core2.s00-seattle.as6453.net (66.110.25.21) 38.419 ms 46.547 ms 46.891 ms
7 if-4-0.mcore4.pdi-paloalto.as6453.net (207.45.196.85) 319.571 ms 58.185 ms 212.808 ms
8 if-8-0-0-0.tcore1.lvw-losangeles.as6453.net (216.6.86.10) 51.853 ms 49.323 ms 47.881 ms
9 192.205.35.129 (192.205.35.129) 47.903 ms 50.538 ms 67.942 ms
10 cr2.la2ca.ip.att.net (12.122.129.34) 102.264 ms 104.363 ms 107.978 ms
11 cr1.slkut.ip.att.net (12.122.30.29) 98.945 ms 99.048 ms 100.564 ms
12 cr2.dvmco.ip.att.net (12.122.30.26) 106.268 ms 100.363 ms 112.446 ms
13 cr1.cgcil.ip.att.net (12.122.31.86) 124.437 ms 99.556 ms 118.500 ms
14 cr2.cgcil.ip.att.net (12.122.2.54) 103.137 ms 117.441 ms 99.995 ms
15 cr1.n54ny.ip.att.net (12.122.1.1) 96.255 ms 101.623 ms 97.911 ms
16 cr83.n54ny.ip.att.net (12.122.105.50) 97.443 ms 98.508 ms 100.415 ms
17 gar20.n54ny.ip.att.net (12.122.131.249) 99.792 ms 102.101 ms 107.202 ms
18 12-122-254-114.attens.net (12.122.254.114) 98.936 ms 100.701 ms 128.504 ms
19 mdf001c7613r0004-gig-12-1.nyc3.attens.net (63.240.65.14) 137.760 ms
mdf001c7613r0003-gig-10-1.nyc3.attens.net (63.240.65.10) 100.981 ms
mdf001c7613r0004-gig-12-1.nyc3.attens.net (63.240.65.14) 97.365 ms
20 * * *

I should note, again, I just let things load over time and I managed to get on to another toon. However, it took about 30 minutes to get logged on after everything loaded.

TonyM: what is your suggestion if the version number is up to date? Both of us seem to have the right version running.
Reply Quote
93 Human Paladin
5870
Having the same problem here. Can't log in to the game server.
Reply Quote
80 Blood Elf Mage
2675
Having the same problem here. Can't log in to the game server.


could you post a traceroute?
sticky details how to do it
link: http://us.battle.net/wow/en/forum/topic/1083748904
Reply Quote
80 Blood Elf Mage
2675
it appears to have fixed itself?
odd.
i can connect to realms easily now!

Reply Quote
Support Forum Agent
It seems like there was a few hiccups on Battle.net that were affecting WoW. All should be clear now.
________________________________________________
Account and Technical Services || Mac Tech Support
Tue-Sat 9 AM - 5 PM CST
Can't find a resolution on the forums, contact a Support Rep directly: http://us.blizzard.com/en-us/company/about/contact.html
Do you love Boomkins? Sure, we all do!
Wait I mean, take a moment to let me know how I am doing. http://www.surveymk.com/s/RF8K3KG
Reply Quote
80 Undead Priest
2270
Things aren't cleared up. I still have the same issues as described above.
Reply Quote
Support Forum Agent
Let's try clearing your DNS to see if it isn't saving a bad one from these incidents.

You'll need to flush the DNS.
1. Navigate to /Applications/Utilities/ and launch Terminal.
2. Copy/Paste the following:
For Leopard (10.5) & Snow Leopard (10.6):
dscacheutil -flushcache

3. Press return.
**NOTE: You will not get any feedback from Terminal if this is done correctly on any OS.
4. Test WoW.
________________________________________________
Account and Technical Services || Mac Tech Support
Tue-Sat 9 AM - 5 PM CST
Can't find a resolution on the forums, contact a Support Rep directly: http://us.blizzard.com/en-us/company/about/contact.html
Do you love Boomkins? Sure, we all do!
Wait I mean, take a moment to let me know how I am doing. http://www.surveymk.com/s/RF8K3KG
Reply Quote
80 Undead Priest
2270
I cleared and tested wow and it hadn't changed. Only after I restarted did it manage to take.

Things are still a little slow to get connected than usual but I have managed to get back online.

Thank you for the help.
Reply Quote
93 Human Paladin
5870
it appears to have fixed itself?
odd.
i can connect to realms easily now!

Mine fixed itself too.
Edited by Kellea on 11/27/2010 1:12 PM PST
Reply Quote
85 Draenei Mage
3700
***Just noticed this is Mac tech support - moving it to PC** sorry :P

I am having the same problem after downloading the latest 'hotfix' for patch 4.0.3. Game worked fine for me last night, then today - fail.

I have deleted, WTF, Cache, and interface, flushed out DNS, rebooted many times, and I still get stuck on the realm screen. It lets me view the lists of realms, I select a realm, get a dialog box saying "loading server" after about 15 secs, the box disappears and leaves me looking at the realm screen again. I have tried logging on to different realms, both US, Oceanic, but still have the same problem.

I am now sitting here with my 3 WoW disks ready to do a complete re-install, unless somebody has another suggestion?

Edit: I have also gone to the WoW folder and checked it is run as admin, and I am running Version 4.0.3 (13329)

here is the trace route, I notice it is not reaching the destination, so is that my IP network, or Blizzards network?

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


C:\Windows\system32>tracert us.logon.battle.net

Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 38 ms 20 ms 23 ms rdl801.ba.optusnet.com.au [198.142.130.27]
3 21 ms 21 ms 22 ms rdl2-ge12-0.gw.optusnet.com.au [198.142.144.161]

4 37 ms 42 ms 40 ms mas2-ge10-1-0-904.gw.optusnet.com.au [211.29.125
.138]
5 36 ms 41 ms 40 ms mas3-ge11-0.gw.optusnet.com.au [211.29.125.241]

6 201 ms 196 ms 275 ms 203.208.148.97
7 195 ms 196 ms 195 ms xe-10-0-0.edge5.LosAngeles1.Level3.net [4.59.48.
57]
8 197 ms 198 ms 197 ms ae-3-80.edge2.LosAngeles9.Level3.net [4.69.144.1
43]
9 195 ms 194 ms 195 ms 192.205.37.145
10 197 ms 199 ms 198 ms cr1.la2ca.ip.att.net [12.122.84.202]
11 199 ms 202 ms 198 ms cr83.la2ca.ip.att.net [12.123.30.109]
12 196 ms 200 ms 199 ms gar5.la2ca.ip.att.net [12.122.129.25]
13 202 ms 198 ms 199 ms 12.122.255.74
14 196 ms 199 ms 199 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]
15 12.129.211.38 reports: Destination net unreachable.

Trace complete.

C:\Windows\system32>tracert 12.129.206.130

Tracing route to 12.129.206.130 over a maximum of 30 hops

1 2 ms 2 ms 1 ms 192.168.1.1
2 23 ms 22 ms 23 ms rdl801.ba.optusnet.com.au [198.142.130.27]
3 20 ms 20 ms 20 ms rdl2-ge12-0.gw.optusnet.com.au [198.142.144.161]

4 40 ms 39 ms 39 ms mas2-ge10-1-0-904.gw.optusnet.com.au [211.29.125
.138]
5 41 ms 40 ms 38 ms mas3-ge11-0.gw.optusnet.com.au [211.29.125.241]

6 194 ms 208 ms 197 ms 203.208.148.97
7 197 ms 194 ms 196 ms xe-10-0-0.edge5.LosAngeles1.Level3.net [4.59.48.
57]
8 197 ms 194 ms 194 ms ae-3-80.edge2.LosAngeles9.Level3.net [4.69.144.1
43]
9 196 ms 196 ms 197 ms 192.205.37.145
10 200 ms 196 ms 200 ms cr2.la2ca.ip.att.net [12.122.84.218]
11 197 ms 196 ms 197 ms cr83.la2ca.ip.att.net [12.123.30.109]
12 198 ms 205 ms 198 ms gar5.la2ca.ip.att.net [12.122.128.25]
13 200 ms 200 ms 205 ms 12.122.255.74
14 197 ms 202 ms 196 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]
15 12.129.211.38 reports: Destination net unreachable.

Trace complete.

Edited by Zyara on 11/30/2010 1:34 AM PST
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]