Since yesterday I’ve been crashing in diablo, I get the network disconnected your client has been disconnected from the server error after 2 to 3 minutes joining my solo character and starting a nephalem rift, I can sit in town for as long as i want but as soon as i join a nephalem rift it disconnects, I run bounties and it disconnects, now this is all on my new necro i made yesterday, I switched over to both my wizard and monk and played in nephalem rifts for 10+ minutes and didnt have any problems with disconnecting at all which is the most confusing thing to me (i find it hard to believe that this issue could be entirely caused by which character or class i am), all the characters are seasonal, I tried making a brand new seasonal necro and running a nephalem rift and got kicked, I’ve already tried the following solutions,
Restart:
- PC
- Game
- Launcher
- Router (hard reset)
Reinstall:
- Game (from HDD to SSD)
- Battle.net Launcher
Ran the game in both 64 and 32 bit.
Ran Battle.net repair tool.
Ran Battle.net in both standard and beta versions.
Checked and (if needed) updated the following drivers:
- GeForce Driver
- Intel Drivers
-Dragon Center Drivers
- Realtek HD Universal Drivers***
- LAN Manager***
*** = drivers were out of date and updated
PC Specs:
i7-8700 3.2 GHz
MSI Z370 Gaming Plus
Corsair 16 GB (2x8)
MSI RTX 2070 Armor
Corsair 850 Watt PSU
(no overclocking at all)
any help would be appreciated, thank you
Hey, diggitydom! It’s definitely a bit odd that this occurs only on the Necromancer. Does the same problem happen on an alternative connection?
Let’s gather a WinMTR file until the problem occurs for 10 to 15 minutes. 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)
1 Like
Thank you for replying and helping me with this issue. I decided to load up Diablo 3 on this very terrible laptop I have and although the laptop almost melted, it was able to run the game for a whole rift without any connection issues, that laptop was running off the Wifi and my main PC that is having the connection issues is a wired connection but both connections are from the same router. During the 12 minute long test the game disconnected 2 times, but it took the game a while for the first disconnect, almost as if the MTR test was helping with the connection.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 1 | 790 | 789 | 1 | 12 | 162 | 11 |
| 96.120.62.65 - 1 | 790 | 789 | 7 | 12 | 158 | 10 |
| 68.86.146.185 - 1 | 790 | 789 | 7 | 12 | 162 | 11 |
| 69.139.169.230 - 1 | 790 | 789 | 7 | 12 | 161 | 15 |
|be-50-ar01.mckeesport.pa.pitt.comcast.net - 0 | 793 | 793 | 8 | 13 | 94 | 18 |
|be-31621-cs02.pittsburgh.pa.ibone.comcast.net - 1 | 790 | 789 | 9 | 14 | 160 | 14 |
|be-1211-cr11.pittsburgh.pa.ibone.comcast.net - 1 | 785 | 783 | 9 | 13 | 94 | 10 |
|be-302-cr12.ashburn.va.ibone.comcast.net - 1 | 790 | 789 | 13 | 18 | 152 | 19 |
|be-1212-cs02.ashburn.va.ibone.comcast.net - 26 | 394 | 294 | 15 | 18 | 96 | 16 |
|be-2207-pe07.ashburn.va.ibone.comcast.net - 1 | 782 | 779 | 13 | 18 | 163 | 15 |
|as4436-1-c.600wseventh.ca.ibone.comcast.net - 1 | 790 | 789 | 14 | 23 | 159 | 22 |
| ae1-br01-eqdc2.as57976.net - 0 | 793 | 793 | 71 | 78 | 179 | 74 |
| et-0-0-2-br01-eqch2.as57976.net - 0 | 793 | 793 | 71 | 80 | 188 | 123 |
| 137.221.65.132 - 0 | 793 | 793 | 71 | 81 | 475 | 77 |
| et-0-0-2-br01-eqla1.as57976.net - 0 | 793 | 793 | 71 | 83 | 284 | 75 |
| 137.221.68.77 - 0 | 793 | 793 | 70 | 77 | 174 | 73 |
| 24.105.30.129 - 0 | 793 | 793 | 70 | 74 | 97 | 74 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Thank you for the test, diggitydom! The connection tests is show some loss earlier on in the test, but it isn’t persisting once it reaches our servers. It’s starting off in the home network and throughout the comcast peers. It may be some mitigation or network ability issues causing the problem.
Let’s try a few things here.
-
Reset the network devices.
-
Reset the router and firewall settings.
-
There’s settings within the router/modem that helps mitigate or prioritize the home network traffic, so one device or connection type could have priority over another that can cause packet (data) loss or latency spikes, resulting in a disconnection.
Check for the following settings in the router and disable any that are enabled:
- QoS (Quality of Service)
- WMM (Wireless Multimedia)
- UPnP (Universal Plug and Play)
The settings for these can vary from depending on the device model. It’s not something that we help with directly because the settings and locations can vary. The router manufacturer or Internet Service Provider (if the router/modem was provided by them) can help look for these settings.
If it does continue, this will need to be addressed with the internet provider since the problems are starting off at the home network and throughout their peers. If you wanted to include a new WinMTR test to the main PC, we can take another look on the system where you probably play the most (and eliminate possible concerns with the wireless connection on the laptop).
2 Likes
I got with Xfinity yesterday and they had to reset my router remotely, apparently there was an offline gateway on my device, after they reset it everything began running smoothly again, I did disconnect one time in a span of 2 hours but compared to the rate at which I was disconnecting at before I really can’t complain about that, once my Xfinity store opens back up on June 1st I’m going to trade in my outdated router for the newest model. I can’t thank you enough for your help, I greatly appreciate your effort in helping me resolve my issue.
2 Likes
Glad to hear it’s been a bit better after working with Xfinity a bit on this, diggitydom! If you’re still experiencing any issues, we can take a look at a new WinMTR test 
Hopefully that disconnection was just a one and done, and it’s been stable since then!
1 Like