Is that something I can run for a few continuous days?
Hey Oromokos,
WinMTR can be run for as long as you’d like, but we generally recommend running it from 10 minutes to no more than 30 minutes at a time. The reason being is that when the test is run for a very long time (hours on end) the results may not be as accurate. Compared to if you just have it run for 10-20 minutes when the issue occurs.
Mainly WinMTR is used to help look for packet loss or high latency spikes anywhere in the connection between you and the game servers. If the disconnections are happening mostly in raids/dungeons then you may want to just start the WinMTR before your raid/dungeon starts. If the disconnect doesn’t happen within the first 20-30 minutes of the test running, stop the test and restart it. Then when you’ve captured a disconnect post the results.
The disconnections may not be happening due to an issue with your PC or home network, but may instead be due to an intermittent issue between your local ISP’s network and the WoW servers. The hope is that WinMTR would allow us to confirm that.
- Download WinMTR
- Right-click on the downloaded .zip folder and select “Extract All”, to extract the files to a new folder.
- Open the new folder that was created, then open the WinMTR_x64 folder.
- Right-click on the WinMTR application and select “Run as administrator”.
- Type the IP address 24.105.62.129 in the “Host” field.
- Click on “Start” and then launch the game. Allow the test to run for at least 10 minutes. Click on “Stop” after you have experienced the latency or connection issue.
- Click on “Copy Text to Clipboard”, paste the results here, then highlight everything and hit the </> button in the posting section so it will allow links.
1 Like
This sounds like a solid plan. I will do this and post back with the results!
Sounds good! Replying back so you can reply to this once you have the info.
So, This isn’t the same issue I’ve been having, but I am also getting a “You have Been Disconnected” error a LOT when changing characters. Does this offer any insight into things while I wait for raid night to try and capture that particular issue?
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 577 | 577 | 0 | 0 | 3 | 0 |
| 10.1.8.1 - 0 | 577 | 577 | 2 | 8 | 42 | 6 |
| 100.120.245.128 - 0 | 577 | 577 | 4 | 9 | 43 | 8 |
| 100.120.245.57 - 0 | 577 | 577 | 3 | 11 | 118 | 7 |
| nyrkbprj01-ae3.0.rd.ny.cox.net - 0 | 577 | 577 | 9 | 15 | 60 | 13 |
| 68.105.31.75 - 0 | 576 | 576 | 9 | 17 | 83 | 14 |
| ae1-br01-eqny8.as57976.net - 0 | 540 | 540 | 32 | 330 | 2701 | 212 |
| No response from host - 100 | 115 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-1-pe01-eqch2.as57976.net - 0 | 577 | 577 | 28 | 35 | 114 | 32 |
| 24.105.62.129 - 0 | 577 | 577 | 28 | 33 | 52 | 33 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderHonestly, that WinMTR looks fine and don’t show anything that would cause disconnects.
Disconnecting when changing characters can be a different cause than disconnecting while playing though. Sometimes character swap / realm swap disconnects can be due to UI corruption or corrupt game data. If you can reproduce the character swap disconnect it may be worth it to try temporarily resetting the UI and then test it again. Then if it does still happen, just rename/move the old folders back in to restore addons/settings.
Oh, oops, didn’t see Jambrix’s reply. I hope you can catch the problem in your WinMTR 
It recovered, but I hit a big spike while this was running. I haven’t fully dc’d since I started using the tool except for right after stopping it to save this one.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 98 | 98 | 0 | 0 | 0 | 0 |
| 10.1.8.1 - 3 | 90 | 88 | 2 | 8 | 15 | 8 |
| 100.120.245.128 - 3 | 90 | 88 | 5 | 8 | 15 | 9 |
| 100.120.245.57 - 3 | 90 | 88 | 5 | 11 | 38 | 6 |
| nyrkbprj01-ae3.0.rd.ny.cox.net - 3 | 90 | 88 | 11 | 15 | 43 | 13 |
| 68.105.31.75 - 3 | 90 | 88 | 8 | 18 | 95 | 15 |
| ae1-br01-eqny8.as57976.net - 2 | 88 | 87 | 32 | 296 | 2738 | 130 |
| No response from host - 100 | 19 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-1-pe01-eqch2.as57976.net - 3 | 90 | 88 | 27 | 35 | 114 | 31 |
| 24.105.62.129 - 3 | 90 | 88 | 30 | 34 | 41 | 32 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderThe 2nd line there (10.1.8.1) shows a spike in packet loss, to 3%. While the test wasn’t run for very long, that may be where the problem starts.
So you have your router/modem (192.168.1.1) which the connection to that looks fine, but when it makes the jump to the next device 10.1.8.1 that’s when the loss starts. Depending on how things are set up that may be a switch or an ISP device outside your home / down the street.
I’d probably recommend running the test again to see if you can capture another one just to confirm if the packet loss is happening at the same place. Then if it is still starting at 10.1.8.1 you may want to get in touch with the ISP so they can start investigating to find out what is causing the packet loss intermittently there.
Ok, so it finally happened proper tonight. I don’t see many dropped packets at all here.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 3923 | 3923 | 0 | 0 | 10 | 0 |
| 10.1.8.1 - 0 | 3922 | 3922 | 2 | 8 | 141 | 8 |
| 100.120.245.128 - 0 | 3922 | 3922 | 2 | 8 | 117 | 9 |
| 100.120.245.57 - 0 | 3922 | 3922 | 3 | 10 | 141 | 19 |
| nyrkbprj01-ae3.0.rd.ny.cox.net - 1 | 3915 | 3913 | 7 | 15 | 133 | 23 |
| 68.105.31.75 - 0 | 3922 | 3922 | 8 | 18 | 166 | 13 |
| ae1-br01-eqny8.as57976.net - 1 | 3658 | 3657 | 30 | 325 | 4396 | 175 |
| No response from host - 100 | 786 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-1-pe01-eqch2.as57976.net - 0 | 3923 | 3923 | 26 | 35 | 165 | 35 |
| 24.105.62.129 - 0 | 3923 | 3923 | 28 | 34 | 143 | 33 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderStarting to think you might be referring to the sticky from 10-11 days ago. I too am having the same issue and can barely play the game thanks to this.
1 Like
I have now replaced my internet service provider to try and correct this issue. Unfortunately, I still had the same random disconnect problem during raid last night.
Any further assistance based on the last winmtr data above?
If you changed services, you’ll likely want to gather a new WinMTR. But th
It’s pretty clear that it’s not an ISP issue. Nobody gave me any explanation of what the last WinMTR really meant, so I’m wondering if it’s obviously something completely different. Or, since I didn’t see any packet drops in the last one, I think it has nothing at all to do with my internet connection.
The last WinMTR showed some spikes throughout the tail end of the ISP network before connecting to Blizzard. It’s possible the area where you live has multiple ISPs using similar routes out of the state. Winter storms can affect those routes.
Another WinMTR will help compare. Additionally, only run the test for 5-10mins while trying to capture the problem.
Yeah, it’s difficult to capture a problem that happens every day or two in a five minute segment. Obviously, I’m running it during raid, but I can’t start and stop it during pulls. I’m trying to restart it between pulls though. M+ is harder
Understandable. Since you changed ISPs, did you also change routers/modems? I’m wondering if there’s a QoS setting on your NIC or those pieces of equipment causing this.
My router and switch are unchanged.
I have a ubiquity dream machine pro and a ubiquity 24 port switch. My house is wired for Ethernet in basically every room, and this system has been in place and unchanged for about a year (and no settings changes in a year).
Are there particular configuration settings I should look at? Short of something breaking, coincidently at the same time 9.0 dropped, it seems like it would have to be a client-side issue to me
Since you mention ubiquity, you may want to check this thread and see if it applies…
https://us.forums.blizzard.com/en/wow/t/screen-freeze-kinda/748101/24
1 Like
Oh wow, that might be it! The description of what’s happening is eerily similar—I’m going to dig into this tonight.
Thanks so much!!
Edit: I was able to check the IPS log from my phone, and sure enough, I think this is the issue. Now I need to figure out the best way to fix it without sacrificing overall network security…