Persistent disconnection issue WOW51900319

Support Technical Support
1

I get disconnected from the game (WoW Classic) with the following error: WOW51900319. I play in EU on EU Servers
I have the disconnection issue with WoW, only. On other game or program are affected.

I have now tried the following:

  • reinstalled wow classic and battle. net
  • updated drivers
  • used different chars and realms
  • ran the game with and without addons
  • port forwarded
  • priotized the computer in the routers settings
  • Flush DNS, reset TCP/IP
  • switched between LAN and WIFI
  • Different routers and DSL cables
  • had my ISP check connection stability
  • VPN and mobile hotspot tests
  • used a VPN
  • I have had all surrounding programs off and turned of most other devices
  • I had a security software on the old pc and disabled it. On my new computer I just use windows defender (Windows 11)
  • WoW Classic and Battle.net were added to the exceptions in the firewall
  • changed coumputer in the mean time (old: Intel CPU/Nvidia GPU; new: AMD CPU/AMD GPU)(setup from scratch)
2

Having the same issue here on retail, Will be able to log in but when I enter different zones like instances / hubs everyone else will freeze and I am not able to interact with any buttons, Dont even disconnect from the server I have to tab out to close wow down. All characters are effected.

3

Is anyone expiriencing the same issue or knows any remedy?

Any help is apprecciated

4

I have done the same steps, but no luck. Blizzard fix this! And i’ve got this problem with retail WoW.

5

Same problem on my side since 11.1.5, i have no idea why and it’s very frustrating

6

And the error is back again… What the hell is going on? How am i supposed to play the game normally with all this bullsht…

Cancelled my subscription yesterday…

7

I had this exact thing happen to me today… Re-launching the game fixed it for a while. And sometimes, upon relogging without disconnecting, a random couple characters will occasionally have their animations frozen, at the login screen.

8

Its a shame, really. I already did check through the whole list. And had two tickets opened over the course of now 5 months. And all blizz comes up with is to ask the community to solve theirs issues.
If it wasnt for the constant dcs I would have a blast in classic. But like this I dont know if I want to go on paying a monthly sub.

9

Today I quested in SV and noticed that the disconnects got a lot more frequent when i was diving under water. Has anybody had the same happen?

10

I have this since a long time.
So far without any solution and I have tried a lot. :triumph:
I know the frustration.

11

Same here. The only thing that really helps is the VPN, which makes me think it has something to do with the routes.
I would be so happy to go to my ISP and tell them to switch me somewhere if I only knew what endpoints I was trying to connect to.
Unfortunately, support couldn’t give me that information, so I’ll continue to use the VPN for the game. One day I’ll probably dig up the addresses out of the WoW process myself

12

Same here, Blizzard wake up!

13

I’ve been digging into the WOW51900319 a bit. The test took place on Firemaw

And here’s what I observed: wowclassic.exe opens two connections to Blizzard IPs in the 37.244.60-63.0/24 range (port 3724). There might be more subnets, but these are the ones I’ve seen so far.

  • One connection is stable: It stays open from the character select screen until I fully log out.
  • The other connection changes when moving zones: For example, 37.244.60.186 was Stormwind (Firemaw) during my tests.

I flew from Stormwind to Elwynn Forest and back a couple of times. On the second return to Stormwind (37.244.60.186 ), the connection to that specific IP failed to open. This led to the WOW51900319 error.

Below is an excerpt from a 1k probe MTR trace. Things go downhill once traffic leaves my ISP’s network and hits the Netherlands. The hop 137.221.78.176 (part of Blizzard’s AS57976) showed packet loss starting around 5%, peaking at 30%, and ending at 23%. I can’t say for sure if this alone is the root cause, so any insights from networking gurus are welcome!

Packet loss of 1% to 37.244.60.186 was present from the beginning but did not lead to any any visible inconveniences

|                         100.105.102.109 -    1 | 1008 | 1007 |   11 |   12 |   19 |   12 |
|                           80.249.208.83 -    1 |  996 |  992 |   51 |   55 |  132 |   64 |
|                          137.221.78.176 -   23 |  482 |  373 |   52 |  636 | 4982 |   91 |
|                      Request timed out. -  100 |  205 |    0 |    0 |    0 |    0 |    0 |
|         et-0-0-0-pe01-eqam3.as57976.net -    1 | 1008 | 1007 |   49 |   50 |   83 |   50 |
|                           137.221.66.41 -    0 | 1012 | 1012 |   46 |   47 |   75 |   48 |
|                      Request timed out. -  100 |  205 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |  205 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |  205 |    0 |    0 |    0 |    0 |    0 |
|                           37.244.60.186 -    1 | 1004 | 1002 |   49 |   51 |   61 |   52 |
14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.