*NEW DATA*: internet d/c'ing when at loading screen

I have had 3 straight days of the same issue that is not getting better on its own.

Description of the problem: While at home, when I try to log into a character from my select screen, the loading bar gets to ~90%, gets stuck, then I disconnect (WOW51900319). After this happens, my internet completely disconnects, and I cannot locate any WiFi to connect to for 1-2 minutes. This happens mainly at night; in the morning, I can sometimes log in but it is very laggy and delayed. It’s important to note this is just at home (I have used internet from other locations outside of home and it works just fine), so this suggests it’s my home internet that’s the problem, right? Odd part is, I never made any new changes to my home internet or changed plans. I can otherwise use the internet just fine. It’s reproducible in that only trying to log onto my toon from the character select screen causes this problem. Other games, streaming websites, etc. all work fine.

What I have tried:

  • Power cycling my modem and router

  • Updated all drivers for my computer

  • Uninstalling WoW and re-installing it

None of these above interventions have fixed the problem. I called my ISP and they said I have more than enough bandwidth to properly play/steam content.

Does anyone have any suggestions? I am desperate :confounded:

EDIT
Did a WinMTR test just now:

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

Host - % Sent Recv Best Avrg Wrst Last
DeviceDHCP.Home - 100 514047 97 1 4 45 1
No response from host - 100 492401 0 0 0 0 0
ae2.182.aggr01.wacotx.grandecom. net - 100 512150 101 9 14 53 25
ae1.0.core01.gf01.dllstx.grandecom. net - 100 512209 97 11 20 206 13
ae0.0.core02.gf01.dllstx.grandecom. net - 100 516197 101 10 21 248 16
eqix-da1.blizzard. com - 100 515112 97 12 23 256 16
ae1-br01-eqda6.as57976. net - 100 464827 101 31 42 213 35
et-0-0-4-br01-eqch2.as57976. net - 100 518320 101 31 44 177 35
et-0-0-0-pe04-eqch2.as57976. net - 100 519684 101 31 42 177 38
chi-eqch2-ia-bons-04.as57976. net - 100 515288 101 33 41 177 36
24.105.62.129 - 100 514597 101 33 41 177 35
________________________________________________ ______ ______ ______ ______ ______ ______

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

Pathping:


Tracing route to 24.105.62.129 over a maximum of 30 hops

  0  DESKTOP-RQR7Q37.Home [192.168.1.8] 
  1  DeviceDHCP.Home [192.168.1.1] 
  2     *        *        *     
Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           DESKTOP-RQR7Q37.Home [192.168.1.8] 
                                2/ 100 =  2%   |
  1    3ms     2/ 100 =  2%     0/ 100 =  0%  DeviceDHCP.Home [192.168.1.1] 

Trace complete.
Traceroute

Tracing route to 24.105.62.129 over a maximum of 30 hops

  1     2 ms     1 ms     1 ms  DeviceDHCP.Home [192.168.1.1] 
  2     *        *        *     Request timed out.
  3    14 ms    16 ms     9 ms  ae2.182.aggr01.wacotx.grandecom.net [130.45.28.101] 
  4    13 ms    12 ms    12 ms  ae1.0.core01.gf01.dllstx.grandecom.net [24.155.121.43] 
  5    16 ms    14 ms    13 ms  ae0.0.core02.gf01.dllstx.grandecom.net [24.155.121.83] 
  6    15 ms    13 ms    12 ms  eqix-da1.blizzard.com [206.223.118.237] 
  7    31 ms    31 ms    34 ms  ae1-br01-eqda6.as57976.net [137.221.74.33] 
  8    35 ms    34 ms    33 ms  et-0-0-4-br01-eqch2.as57976.net [137.221.65.38] 
  9    32 ms    32 ms    31 ms  et-0-0-0-pe04-eqch2.as57976.net [137.221.69.77] 
 10    34 ms    35 ms    33 ms  chi-eqch2-ia-bons-04.as57976.net [137.221.66.15] 
 11    33 ms    39 ms    35 ms  24.105.62.129 

Trace complete.

Hey, Agrim! Thank you for including the details here! The WinMTR test reflects the same thing as you’ve reported with disconnections. There’s a 100% loss. The test looks like it was ran for quite some time, though it could be due to the disconnection.

The pathping on the otherhand does show some more information, where it shows a 2% loss on the home network.

1 3ms 2/ 100 = 2% 0/ 100 = 0% DeviceDHCP.Home [192.168.1.1]

The internet completely disconnecting is usually a bandwidth or mitigation problem. It can’t be directly caused by World of WarCraft but it could be triggering something within the home network causing the disconnections.

It seems that this is a wireless connection, are you able to try a wired connection? If so, does this happen while directly connected?

It’s worth checking for QoS, WMM, UPnP settings within the router to see if toggling them may help. Typically, disabling it should work, but for some netgear routers, enabling them may help. If assistance with locating these settings is needed, please check with the router manufacturer or internet provider if the device was provided by them.

Does this happen only on one character or does this happen on all characters? Does it immediately connect after a Flush DNS and/or restarting the system?

If the problem continues, there’s a few questions!

  • What is the router/modem models in the home?
  • How is the home network set up? (ie. Modem to router)

As suggested I’d try a wired connection if possible. Another thing to do, if possible, is look at your router when this happens to see if faults and then reboots since that would show without a doubt what that it’s the issue.

Another thing, did you mess with WinMTRs settings? It shows it sent 514047 pings to your router. At the default interval of 1 per second that’s almost 6 straight days of testing.

Thanks for providing some additional suggestions, Clottibby! The WinMTR Test with 514047 packets is likely not a concern. This high spike in packets can occur when a disconnection occurs and the test goes wild since it can’t detect the servers properly. More than likely, it wasn’t ran for 6 days straight :laughing:

Caterpepi and Clottibby, thank you for the replies. I will formulate a proper response to your questions. In the meantime, I am still suffering from the same issue. However, I notice a new error message when I disconnect: WOW51900300. It was previously only WOW51900319. Not sure if that offers any new insight. More info to come.

edit: a new error message popping up as I disconnect: BLZ51901016

Hey Agrim,

Replying to you so you can reply back with the requested info.

Those new error codes are just different versions of the disconnections that you’re seeing, so not much to worry about there.

In my experience if the entire router is disconnecting when this happens it usually indicates an issue with the router device itself or a firmware issue. If it’s a router you lease from your internet provider you might want to contact them to see if they can assist with factory resetting the device and see if that helps.

Caterpepi, to answer your questions:

  1. I tried connecting my computer straight to my router using an Ethernet cable, and the problem still persists (internet completely disconnects once I reach 90% loading bar when I attempt to Enter World). As a reminder, this only happens when I try to log into a character in WoW. I can otherwise surf the internet just fine and play other games.

  2. The disconnect happens with any of my characters. Of note, the disconnect can also be reproduced when I attempt to Change Realm from the character select screen.

  3. I tried Flush DNS and it did not fix the problem. I tried power cycling my modem/router and it did not fix the problem.

  4. Router is Calix GigaCenter 844E. Modem is Arris Touchstone CM8200. Home network is modem to router.

  5. I am less inclined to think this is due to a problem on my computer, since WoW works just fine on other networks (friend’s house, work internet).

I really appreciate you all trying to help. Looking forward to hearing back from you.

edit: Do you suggest getting a brand new router to see if that helps? (in addition to the QoS, WMM, UPnP disabling/enabling that you suggested)

Thanks for the details, Agrim! I have a few more things in mind, but this may need to be addressed with the internet provider to see what’s going on with the home network and the 100% loss when attempting to connect.

If bypassing works, this does indicate some issues with the router, which may need a firmware update or checked for hardware/network related issues. The provider may be able to work with you on this and if needed send a technician out to check on the devices and replace them or suggest replacement as needed.

If neither seems to work, let’s gather new WinMTR tests. Let’s run this test while not attempting to connect to WoW for one, then another one while connecting to WoW for 5 minutes on each test run. It should help compare the two tests and get an accurate reading on the login issue. Copy and paste the text file created and paste it between two ~~~ like so:

~~~
WinMTR Here
~~~

If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)

Updates 6/2/2020:

  • Resetting the user interface did not work

  • Bypassing the router worked, by connecting the Ethernet from my modem straight to my laptop; but given my current living situation I need the internet to go through router for the other house occupants - this isn’t a long-term solution :frowning:

The above findings suggest the router is the problem, however my friend came over with his laptop and his WoW works just fine while using my router, suggesting there is a specific problem going on just between my computer and home router? That’s all I can think of.

WinMTR while doing nothing (no WoW, no other programs open) for 5 minutes:

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                         DeviceDHCP.Home -    0 |  349 |  349 |    2 |    3 |   35 |    3 |

|                   No response from host -  100 |   69 |    0 |    0 |    0 |    0 |    0 |

|     ae2.182.aggr01.wacotx.grandecom. net -    0 |  349 |  349 |    9 |   15 |  376 |   12 |

|  ae1.0.core01.gf01.dllstx.grandecom. net -    0 |  349 |  349 |   12 |   18 |  374 |   18 |

|  ae0.0.core02.gf01.dllstx.grandecom. net -    0 |  349 |  349 |   13 |   18 |   46 |   14 |

|                   eqix-da1.blizzard. com -    0 |  349 |  349 |   13 |   22 |  366 |   15 |

|              ae1-br01-eqda6.as57976. net -    0 |  349 |  349 |   32 |   42 |  148 |   37 |

|         et-0-0-4-br01-eqch2.as57976. net -    0 |  349 |  349 |   31 |   45 |  204 |   50 |

|         et-0-0-0-pe04-eqch2.as57976. net -    0 |  349 |  349 |   32 |   40 |  153 |   33 |

|        chi-eqch2-ia-bons-04.as57976. net -    1 |  345 |  344 |   33 |   37 |   70 |   37 |

|                           24.105.62.129 -    0 |  349 |  349 |   34 |   39 |   74 |   35 |

|________________________________________________|______|______|______|______|______|______|

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

WinMTR while trying to log onto a character from the character select screen for 5 minutes:

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|           Destination host unreachable. -   98 | 7197 |  192 |    1 |   34 | 3572 |    3 |

|                   No response from host -  100 | 7046 |    0 |    0 |    0 |    0 |    0 |

|     ae2.182.aggr01.wacotx.grandecom. net -   98 | 7199 |  192 |   10 |   46 | 3569 |   18 |

|  ae1.0.core01.gf01.dllstx.grandecom. net -   98 | 7201 |  192 |   11 |   48 | 3567 |   15 |

|  ae0.0.core02.gf01.dllstx.grandecom. net -   98 | 7200 |  192 |   12 |   50 | 3554 |   19 |

|                   eqix-da1.blizzard. com -   98 | 7197 |  192 |   13 |   53 | 3554 |   19 |

|              ae1-br01-eqda6.as57976. net -   98 | 7200 |  192 |   32 |   71 | 3555 |   37 |

|           Destination host unreachable. -   97 | 4941 |  191 |   34 |   79 | 3565 |   37 |

|           Destination host unreachable. -   98 | 7203 |  192 |   32 |   70 | 3552 |   37 |

|        chi-eqch2-ia-bons-04.as57976. net -   98 | 7201 |  192 |   34 |   70 | 3553 |   37 |

|                           24.105.62.129 -   98 | 7196 |  192 |   34 |   74 | 3552 |   43 |

|________________________________________________|______|______|______|______|______|______|

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

edit: sorry for the formatting issues ><!

Hey, Agrim! Sorry for the delay here. Thank you for including the update and details! With bypassing the router working, it does suggest there being some issues with the router. It’s a bit curious that your friend was able to connect to the router though.

I assume that your friend was on a wireless connection, while you were wired. It could be how the router is handling wired vs wireless connections. Usually QoS/WMM has to do with this, which you’ve already checked for. With that not resolving the issue, it could be a channel related issue within the device. I’d recommend to have the ISP look into this further to see if they can gather any information on what’s happening with the wired vs wireless connection.

I haven’t been on in over a week. My updates were completed and when I try to log on mine also gives me WOW519003 19 error code. I have attempted to log all the way out, checked the internet connection, went directly into the retail folder and tried signing on from there. It just keeps dc’ing me. I checked for errors and checked for updates as well.

Hey there Sieada,

Could you try the instructions Caterpepi mentioned? If those don’t work, be sure to run the winMTR test she mentioned as well and post the results as a reply to this post.

Thanks! We look forward to your reply!