Since the previous patch i’m randomly disconnecting, but not disconnecting for real - i stay logged on, chat continues on but i can’t take any actions, if there are PCs near by they are running in place and i cannot log off - i have to alt+f4.
It happens randomly on either account i’m running, never simultaneously, most often when i afk (but not limited to). It has happened on a different PC too but as far as this one is concerned i have reinstalled wow and reinstalled all add ons anew, i have ran winMTR and even though it did show a packet or two lost it was never at the same time as the weird disconnect. I kept waiting for it to resolve itself but am slowly getting annoyed by it. As a side note - im also one of the bunch that was getting frequent disconnects on D4, which also were not timed with the few packets i lost along the way. I’m really not sure what to try next.
I’m having this same issue, but I’ve been having it a while. It’s not very common, but sometimes it seems like the server has stopped responding but the client hasn’t noticed. And I can still use chat. And I have to shut down the client and relog to fix it.
Hey there!
Thanks for reaching out with these details. We’ll want to have you run a ‘WinMTR’ network test while the problem occurs in-game to see potential network-related issues between your computer and the game server. Here are the instructions:
- Download the tool from this page
- Enter the game IP into the “host” field. The IP address for our games are listed on the WinMTR instructions page
- Start the test and play the game for at least 15 minutes. Make sure that a disconnect occurs while the WinMTR test is running.
- After recording data for about 5 minutes, click Stop then click “export text” and save the WinMTR file in an easy to find location.
- Once you have that made, open the file. You’ll need to copy and paste the contents of the Text document into the post, and put four Tilde (~) marks above the WinMTR. It’ll look like this:
WinMTR goes here
If you have issues pasting here, please use Pastebin and post the link (ex: Pastebin (dot) com/123456).
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Home.Homenetwork - 0 | 599 | 599 | 0 | 0 | 12 | 0 |
| 100.64.8.2 - 0 | 599 | 599 | 2 | 3 | 34 | 2 |
| 10.65.0.2 - 0 | 599 | 599 | 1 | 2 | 30 | 2 |
| 208-92-185-133.scinternet.net - 0 | 599 | 599 | 2 | 3 | 33 | 3 |
| 216-241-204-181.as26253.net - 0 | 599 | 599 | 2 | 3 | 31 | 3 |
| 216-241-204-44.as26253.net - 0 | 599 | 599 | 7 | 8 | 48 | 8 |
| 216-241-204-80.as26253.net - 0 | 599 | 599 | 7 | 8 | 31 | 7 |
| 216-241-204-82.as26253.net - 0 | 599 | 599 | 7 | 8 | 33 | 8 |
|hu0-3-0-0.nr21.b023583-0.las02.atlas.cogentco.com - 0 | 599 | 599 | 7 | 8 | 48 | 8 |
| be2205.rcr21.las02.atlas.cogentco.com - 0 | 599 | 599 | 8 | 9 | 40 | 9 |
| be2536.ccr41.lax01.atlas.cogentco.com - 0 | 599 | 599 | 15 | 19 | 81 | 78 |
| be3271.ccr41.lax04.atlas.cogentco.com - 0 | 599 | 599 | 14 | 17 | 103 | 15 |
| lax-b22-link.ip.twelve99.net - 1 | 587 | 584 | 23 | 25 | 74 | 25 |
| blizzard-ic-348620.ip.twelve99-cust.net - 0 | 599 | 599 | 18 | 22 | 90 | 19 |
| ae1-br02-csla1.as57976.net - 0 | 599 | 599 | 23 | 30 | 161 | 38 |
| 137.221.65.235 - 0 | 599 | 599 | 24 | 30 | 135 | 24 |
| et-0-0-1-pe02-swlv10.as57976.net - 0 | 599 | 599 | 23 | 25 | 62 | 24 |
| las-swlv10-ia-bons-02.as57976.net - 0 | 599 | 599 | 24 | 25 | 49 | 26 |
| 137.221.105.2 - 0 | 599 | 599 | 23 | 25 | 53 | 24 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I just made a post about my router issues, but I’m having the same problems you describe. I’ll keep an eye on this thread for updates.
i finally managed to DC while remembering MTR, doesn’t seem to be a packet traffic issue (didnt think it was, like i said i would have a packet lost here and there but that never made me disconnect).
Maybe you will return if i fully follow the instructions 
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Home.Homenetwork - 0 | 599 | 599 | 0 | 0 | 12 | 0 |
| 100.64.8.2 - 0 | 599 | 599 | 2 | 3 | 34 | 2 |
| 10.65.0.2 - 0 | 599 | 599 | 1 | 2 | 30 | 2 |
| 208-92-185-133.scinternet.net - 0 | 599 | 599 | 2 | 3 | 33 | 3 |
| 216-241-204-181.as26253.net - 0 | 599 | 599 | 2 | 3 | 31 | 3 |
| 216-241-204-44.as26253.net - 0 | 599 | 599 | 7 | 8 | 48 | 8 |
| 216-241-204-80.as26253.net - 0 | 599 | 599 | 7 | 8 | 31 | 7 |
| 216-241-204-82.as26253.net - 0 | 599 | 599 | 7 | 8 | 33 | 8 |
|hu0-3-0-0.nr21.b023583-0.las02.atlas.cogentco.com - 0 | 599 | 599 | 7 | 8 | 48 | 8 |
| be2205.rcr21.las02.atlas.cogentco.com - 0 | 599 | 599 | 8 | 9 | 40 | 9 |
| be2536.ccr41.lax01.atlas.cogentco.com - 0 | 599 | 599 | 15 | 19 | 81 | 78 |
| be3271.ccr41.lax04.atlas.cogentco.com - 0 | 599 | 599 | 14 | 17 | 103 | 15 |
| lax-b22-link.ip.twelve99.net - 1 | 587 | 584 | 23 | 25 | 74 | 25 |
| blizzard-ic-348620.ip.twelve99-cust.net - 0 | 599 | 599 | 18 | 22 | 90 | 19 |
| ae1-br02-csla1.as57976.net - 0 | 599 | 599 | 23 | 30 | 161 | 38 |
| 137.221.65.235 - 0 | 599 | 599 | 24 | 30 | 135 | 24 |
| et-0-0-1-pe02-swlv10.as57976.net - 0 | 599 | 599 | 23 | 25 | 62 | 24 |
| las-swlv10-ia-bons-02.as57976.net - 0 | 599 | 599 | 24 | 25 | 49 | 26 |
| 137.221.105.2 - 0 | 599 | 599 | 23 | 25 | 53 | 24 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderHey there,
Looking over the WinMTR data, if you experienced the issue in game when this test was running, it doesn’t show up in the test. The connection looks good in this test. 0 packets lost, 599 packets sent/received the highest latency spike was 53ms.
WinMTR’s a live simultaneous test so any issues actively affecting one node would show up in every node after. if the destination looks good, then you can ignore any odd readings from specific nodes prior.
You technically have 2 connections to the service. Home and World. Home is a small channel used mostly for social functions like chat and some addon communication. World is what handles all the back and forth of interactions within the game world. Disconnecting from world but not home would cause what you are reporting.
Common causes of this would be a network/connection issue/instability which isn’t showing up in the test you provided (Doesn’t mean there isn’t an issue, we just don’t see it with the available data) or some sort of conflict on the system itself between the game client and other software competing for resources.
Give the following a shot and see if it helps here.
Try doing an extended power cycle on your system. Turn off all devices including the modem. Wait 30 minutes, turn on the modem, wait 5 minutes, turn on any network devices, wait 2 minutes, turn on your computer and try the game.
In some cases there is a corrupt or misconfigured setting within the router or modem. We cannot say what that might be offhand but the easiest way to resolve these conflicts would be to factory reset the router and/or modem.
You may need to look up your specific model for the steps on how to do this and in some rare cases you may need to have this done by the ISP. Feel free to reach out to them for assistance if necessary.
You can try using a VPN. This can help determine if the issue is routing based. Please note we do not support VPN usage though we do not prohibit its use with most of our games. Some countries around the world do restrict VPN usage so you will want to research these restrictions for your country before attempting to use a VPN.
Many VPNs offer a demo or trial version of their service to allow you test without commitment.
This is not meant to be the solution, just for testing but if it solves the issue and are comfortable using the VPN, you can continue to do so.
If you have any addon managers installed. They are fine programs but they have the tendency to prevent our troubleshooting steps from working. Please uninstall them and leave them off your system until we have solved the problem.
Once that is confirmed, we need to delete the temporary game files to attempt to eliminate any corrupt data that might be affecting the client or characters. Your game will rebuild them when you next login but this will remove all installed addons. Please do not reinstall any addons until we know the issue is resolved: https://battle.net/support/article/7549
Let’s reset the in game user options:
- Click the blue bnet icon on the bnet app.
- Choose settings, then game settings.
- Click the reset in game user options button under the correct game listing.
- Confirm the changes and close the window.
We will want to run the repair tool on the game client: https://battle.net/support/article/7655
Try running your system in selective startup mode: https://battle.net/support/article/200483
Create a new administrator account: https://battle.net/support/article/34550
Once the account is created, shut down the computer, wait 60 seconds, restart, log into the new profile and try the app/client.
If that doesn’t solve the issue, then I recommend submitting a ticket with an msinfo attached for further investigation. (instructions for collecting that msinfo report will be on the form.)
Click your name at the top right of this page, click support, click contact support.
It will ask for system files (instructions in the form) but I also recommend new connection tests. Try Pingplotter this time. 2 tests, 10 minutes long while recreating the issue. (Stop and restart the test while playing if the issue doesn’t happen within 10 minutes) One test from the normal connection, the other test while using the vpn. Should allow our agents to investigate this further with you.
Did you ever get it fixed? I’ve been having the same issues.
I don’t know if this will help you, I am on the east coast United States and we were having a similar problem and it turned out the fix was provided by the cable company. Our modem was a few years old and apparently their firmware was not updated on their end for our account, so they had us do a 5 minute shut down and reboot while they made changes to our service and it works great now. I think the problem was that they had a faster internet speed service and we still had the old slow firmware, so if you have cable , you might want to call them.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.