Guess I have to UnSub, but I dont want to

Support Technical Support
1

Title says it all really…

After 4 tickets to support, with them basically saying that it is my fault that suddenly wow crashed loading between IPv4 and IPv6 zones, and essentily saying all the people in this post : Continuous issue of being stuck on loading screens [NEW TOPIC] had unrelated issues that are identical to mine, I have utterly exhausted all methods of trying to make it work.

Wow is THE ONLY program affected. Nothing else on my system disconnects like this, and I find it quite insulting that after many times repeating the same steps over and over by the ‘advice’ given from the so-called support staff, that it was insinuated that I am to blame for it suddenly stopping working after a hotfix.

Ive done tcpdumps, tracelogs, mtps, pings, uploaded system logs. The wow client handshake is being rejected by the battlenet servers, and the client is sending a disconnect request back to the bnet app between zones.

It has absolutly unrestricted access, and IPv6 and IPv4 is set up correctly. Ive had my ISP confirm this, ran multiple network tests and all is ok on my side.

I informed them of all of this, and obviously, I got the response to ‘check my connection’ , ‘reinstall’, and ‘check my firewalls’, which, if they had read previous tickets, they would have realised that I had done.

Now, I have a piece of software I cannot use. Sometimes (1 out of 50) times, I can log on to 1 or 2 characters, but they will disconnect and usually fall into a logged out limbo where they wont load.

Again, if I get a blue response, then I’m fairly sure that I will be asked to check my connection, reset UI, or disable addons, which seem to be the content of 90% of their support documents. Ive done this. I work as a software engineer. Im not stupid. Its on your side as the wow install IS THE ONLY THING THAT FAILS, and other peices of software which use IPv6 and IPv4 on various servers do not fail.

This is likely the reason VPNs sometimes work.

But again, its obviously our fault, as this error has been happening since November last year, and possibly before.

I really dont want to unsub. I really enjoy playing this game, but it just doesnt work, and the cookie cutter copy and paste responses regurgitating the same ‘advice’ is tedious to say the least.

I have never seen the stability of the game in such a poor state as now, which is a shame because SL is one of the best expansions ive ever played.

But it just doesnt work. I have tried absolutely everything.

1 Like
2

Have you tried disabling IPv6, or at least, force WoW onto an ipv4-only route?

(Yes, that’s at best a workaround, but if it makes WoW work…)

3

Same Problem We Had This Problem back In 8.3 They fixed it after 3-4m now we have this problem again since shadowlands launch day.i think they bought some cheap amazon servers.for high pop realms or something like that

1 Like
4

The opposite was true. I had IPv6 disabled to start, and suddenly atarted to get WOW5190019 error, it would only then allow me past the login screen if it was enabled. I could log on to some characters, but then I would start to get Transfer Aborted: Instance not found errors on zones that the character had not entered before. Once I changesd DNS to googles, the characters in some zones would then get a Word server is Down error.

Its without a doubt a problem on their side, judging by the massive tcpdump I ran, and the fact that anything sent via the program itself (not the launcher) is instantly rejected, forcing a disconnect.

5

Its always our fault, you didnt know that?

2 Likes
6

yeh. been a lost 2 weeks trying every possible system test. reinstalled OS twice, reinstalled wow quite a few times, power cycled, contacted ISP, ran network tests. Its not an issue on my side.

But yeh, according to them, it’s our fault they dont test things properly and rush out faulty software.

7

So… How do you explain the hudreds of thousands of players who play every day, without issue?

8

Because they probably bought extra cheap servers to deal with additional load from SL launch which don’t have complete dual stack IPv6, so they are not translating properly in some geographical areas, and Blizzard will not admit this because it makes them seem at fault. Easier to blame us than admit a mistake or, god forbid, pay extra money to have a more stable platform.

9

Spouting out random words really doesn’t make you look clever you know. Just refrain from commenting if this is all you can produce.

11

Cheap servers, geographical areas, POSSIBLE.

Just stop already.

12

Ok. I apologise if I came across harsh. Just very frustrated at the moment, with this being my only joy in covid lockdown in the uk.

13

During SL launch ive had a constant problem on getting DC/ED on a specific location and getting DC again when i log back in.

I completed every step they needed and at the end after me staying out of game because self service transport service was on cd, a while later it never occured again.

1 Like
14

Yeh Im kind of hoping that if I leave it for a while, then it’ll all be fixed. It just infuriates me, and I kind of lash out.