[Shaw Canada] You've been disconnected. WOW51900328

So that’s weird. Was playing just fine last night. Go to bed. Wake up 8 hours later and come back to this.

It says “Connecting”
then “Retrieving realm list”
then “logging in to game server”… extended wait of about 30 seconds
then “You’ve been disconnected WOW51900328”

I checked server status. Shows every server is up and running and I can log into WoW retail and Wrath beta just fine.

How do I fix this?

2 Likes

Howdy Jetfuel,

Based on what you described, I’d recommend a UI reset as old/corrupted addons is a common cause for these errors. Security software like antivirus or firewalls can also block one version of WoW, so if you still have an issue I’d suggest double checking that each WoW client is allowed as an exception.

A post was split to a new topic: [Berretta] BLZ51901016

Having the same issue, retail and wotlk beta works fine but tbc classic won’t let me login.

Tried deleting everything and reinstalling but didn’t work.

Everything worked fine 12hrs ago.

1 Like

Would you be able to test another network like a mobile hotspot to see if there’s any change?

Same error when I use my phone as a personal hotspot for my computer.

I did the UI reset as well and no effect. Super weird cause I was playing last night. Shut off my computer, turned it on this morning and boom error. Literally did nothing the game or computer since the time it worked till the time it didnt work.

UPDATE: Okay I think I figured out the issue. I’m from NA and was on an oceanic realm testing latency (friend from Aussy and I are thinking about rolling on the same server for WOLTH fresh servers)

So just now I logged onto my retail character just fine, but then I changed to an oceanic server and boom, disconnected from there as well.

It’s definitely something to do with that.

Duck are you an NA player logged into an oceanic one?

Is there a way to change from Arugal auzzy server to an NA server without logging into the realm first?

Yeah I’m in Canada but play on Arugal. I agree seems to be an issues when only connecting to OCE servers from NA. Now have the same issue on retail, when I switched to an OCE server.

Hotspot does work for me so it seems to be an issue with my home internet provider which is Shaw.

1 Like

Yup, thats 100% what it is. I’m west coast Canada and was doing some tests on Arugal on oceanic server.

So how can we switch off Arugal without actually being able to get to Char select screen?

You could try adding this line to the config file in the WTF folder:
SET disableAutoRealmSelect “1”
This will be removed the next time you launch WoW though.

In the mean time, would y’all be able to provide a WinMTR test to the Oceanic servers so we can see what is happening?

  1. Download WinMTR
  2. Unzip the file to your desktop
  3. Run the WinMTR as Admin
  4. Type your server IP in “host”.
  5. Click “Start” and open the game. Let the MTR test run for at least 10 minutes to capture this issue occurring.
  6. Click “Copy text to clipboard”
  7. Type two sets of four squiggly lines and then paste the contents of the WinMTR test between:
    ~~~~ Paste WinMTR Test Results Here ~~~~

Note: If it’s not letting you post, break links by adding a space before .com/.net, so you can post them. You can also upload the MTR contents through Pastebin and post the link then highlight the link and press the ˂/˃ button.

1 Like

I’m guessing there is an issue between here and Australia. The thing to reset realm also didnt work. SET disableAutoRealmSelect “1” in the wtf config didnt take me to the realm selection. I’m off to work now. Im sure it’ll be fixed when I get home (hopefully)

To clarify, is your hotspot using a different provider than Shaw? If they are both using Shaw then there may not be any change. You could try powercycling the modem by turning it off for 30 seconds or 30 minutes if that doesn’t help. This can sometimes help clear out old data in the modem that prevents connecting to certain realms or regions.

Never done this so not sure if I did it correctly but here goes ~~~~|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
hitronhub.home - 0 56 56 1 11 24 11
24.80.0.1 - 0 56 56 10 11 24 11
64.59.145.233 - 5 49 47 0 11 18 11
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider~~~~

My phone is with bell which is working.

You need to run the WinMTR for 5 to 10 minutes in the background while you are experiencing issues within the game. Starting then immediately stopping it doesn’t show anything as not enough packets are sent.

Ah okay. At work now but if the issue is still happening when I get home I’ll do that

I have the same problem and i’m connecting from EU to the US.
It started a 2-3 days ago. I usually cant login. , i get disconnected. After trying again several times the game logs on.

I also experience weird lagging / phasing errors ingame etc sometimes.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.0.1 - 0 497 497 0 0 2 0
gw11.A213.priv.bahnhof.se - 0 497 497 0 0 5 0
172.22.82.126 - 0 497 497 0 5 179 23
a213-gw-c.bahnhof.net - 0 497 497 0 19 257 1
a213-gw.bahnhof.net - 0 497 497 1 6 250 1
sto-kn5-dr1.sto-kn4-dr1.bahnhof.net - 0 497 497 1 5 247 10
sto-kn4-dr1.sto-cr1.bahnhof.net - 0 497 497 1 1 8 2
ae51.edge4.Stockholm2.Level3.net - 0 497 497 1 3 25 1
ae2.3608.ear7.Chicago2.level3.net - 100 101 1 0 120 120 120
BLIZZARD-EN.ear7.Chicago2.Level3.net - 0 496 496 120 124 197 121
No response from host - 100 100 0 0 0 0 0
No response from host - 100 100 0 0 0 0 0
et-0-0-0-pe01-swlv10.as57976.net - 0 496 496 162 162 188 162
137.221.105.2 - 0 496 496 163 163 165 163
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Did a trace route as well.
1 <1 ms <1 ms <1 ms 192.168.0.1
2 <1 ms <1 ms <1 ms gw11.A213.priv.bahnhof.se [46.59.60.1]
3 1 ms 1 ms 1 ms 172.22.82.126
4 1 ms 1 ms 1 ms a213-gw-c.bahnhof.net [46.59.116.94]
5 1 ms 1 ms 2 ms a213-gw.bahnhof.net [46.59.116.93]
6 1 ms 1 ms 1 ms sto-kn5-dr1.sto-kn4-dr1.bahnhof.net [176.10.181.41]
7 2 ms 2 ms 2 ms sto-kn4-dr1.sto-cr1.bahnhof.net [46.59.112.246]
8 4 ms 2 ms 2 ms ae51.edge4.Stockholm2.Level3.net [213.249.107.93]
9 * * * Request timed out.
10 145 ms 122 ms 122 ms BLIZZARD-EN.ear7.Chicago2.Level3.net [4.7.196.134]
11 * * * Request timed out.
12 * * * Request timed out.
13 162 ms 162 ms 162 ms et-0-0-0-pe01-swlv10.as57976.net [137.221.83.81]
14 163 ms 163 ms 163 ms 137.221.105.2

Something looks weird on both tracer commands when it comes to your cluster ae2.3608.ear7.Chicago2.Level3.net in Chicago? ( that’s the number 9 on that list ) Or perhaps there is something messed up with the uplink to US from outside areas?

Some servers don’t respond to certain types of ping requests.

Looks like the majority of the lag is happening before leaving the continent.

1 Like

So the problem still persists but I was able to find a work around.

I downloaded a free VPN. Changed my IP address to a location in Europe. I then was able to log into the Oceanic server/ I then changed my server to wesy coast server. Then I disabled the VPN and can now log in and out. I’ll make sure to stay far away from the Oceanic servers now.

The free VPN i used is called ProtonVPN. Downloaded and installed it in minutes. Then just hit “quick connect” and then logged into wow. Was simple.

I ran that WinMTR thing for several minutes. Here is is

|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          hitronhub.home -    0 |  148 |  148 |    6 |   11 |   24 |   12 |
|                               24.80.0.1 -    0 |  148 |  148 |   10 |   11 |   20 |   11 |
|                           64.59.145.233 -    1 |  144 |  143 |   11 |   12 |   20 |   12 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider~~~~

You didn’t run the WinMTR nearly long enough, as you only sent 148 packets. You also are showing bad latency with a best of 6ms and worst of 24ms on your connection itself. Reboot your connection with the power removed for at least 1 minute before plugging it back in to reconnect. If the problem still persists afterwards, contact your ISP as it seems they might be blocking traffic.