Bnet disconnect and reconnect

Desktop App Tech Support
1

I’ve just begun having this problem today. I log into WoW, I’m stable for maybe a second, and then I begin to lag out (inputs do not register, everyone running in place, etc) during which time I’m able to maintain connections to discord, web apps, etc. I’ve tried release/renew/flushdns, changed dns to google’s pub servers (8.8.8.8 and 8.8.4.4) and also fresh installs of windows, bnet app, and WoW.

Without launching any games, I can see the bnet app disconnecting and reconnecting every few minutes for a few seconds.
Ran WinMTR for 5 minutes while re-installing WoW, results below.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                SAGEMCOM -   20 |  166 |  134 |    0 |    0 |    1 |    1 |
|        065-190-016-001.inf.spectrum.com -   20 |  166 |  134 |    4 |   20 |   75 |   15 |
|    cpe-174-111-105-048.triad.res.rr.com -   20 |  166 |  134 |    9 |   21 |   51 |   16 |
|       cpe-024-025-041-106.ec.res.rr.com -   20 |  166 |  134 |    4 |   20 |   62 |   15 |
|       be31.drhmncev01r.southeast.rr.com -   20 |  166 |  134 |    9 |   22 |   51 |   23 |
|                           66.109.10.176 -   20 |  166 |  134 |   15 |   29 |   63 |   25 |
|                            66.109.5.117 -   19 |  170 |  139 |   13 |   34 | 1023 |   23 |
|                            66.109.9.155 -   20 |  166 |  134 |   11 |   28 |   85 |   23 |
|              ae1-br01-eqdc2.as57976.net -   19 |  165 |  134 |   69 |  127 | 1952 | 1952 |
|                   No response from host -  100 |   58 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   58 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   58 |    0 |    0 |    0 |    0 |    0 |
|                           137.221.68.79 -   20 |  166 |  134 |   70 |   87 |  191 |   77 |
|        lax-eqla1-ia-bons-02.as57976.net -   20 |  166 |  134 |   70 |   85 |  128 |   80 |
|                   No response from host -  100 |   58 |    0 |    0 |    0 |    0 |    0 |
|                            24.105.28.10 -   19 |  170 |  139 |   69 |   91 | 1064 |   81 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Any help would be appreciated. US East.

2

Hey there Gôdmode! Thanks for providing that WinMTR test data. The test here shows 20% packet loss beginning from the first ‘hop’ and persisting through all subsequent hops:

SAGEMCOM - 20:warning: | 166 | 134 | 0 | 0 | 1 | 1 |

This first hop is the connection from your computer to the router or modem (depending on which device you’re connecting to). Packet loss is relatively common to see with WiFi connections, so if you are using WiFi, try testing a direct connection to the router or modem via ethernet cable. Note that we do not directly support wireless connections. If you find that WiFi is the problem, you can contact the support team for the WiFi device or the wireless router.

If you continue to experience the packet loss & those disconnects – or if a wired connection isn’t an option – this would be an issue to bring up to your ISP, as they may need to run some diagnostic tests on your modem or router and/or temporarily replace the device to determine what is causing the packet loss. Keep in mind that you can request to speak with a “level 2 or level 3 technician” when contacting the ISP, as the front-line representatives typically only have access to basic diagnostics and troubleshooting tools. In addition, I encourage forwarding the WinMTR data to whomever you speak with when contacting the ISP, because if they’re able to interpret the data, this may enable them to diagnose and resolve the issue more quickly.

I hope that this information has provided further insight into the situation and helps get things fixed up so you can get back to playing as normal!