|Network Disconnect||April-17-2016 2:25 AM PDT (4 years ago)|
|I keep getting the Network Disconnect error as soon as Town loads. I can log in fine and can select a character but I cannot even play for one second! The error shows as soon as the game starts. Below is my tracert, pathping and Looking Glass results. As you can see, my pathping doesn't get past my router! Is that serious? I am not having problems with any other games/websites (SimCity, League of Legends, Youtube, etc.)|
This started the day before yesterday (15 Apr 2015) at about 11:00 am GMT+2. My ISP is AfriHost (South Africa).
|Network Disconnect||April-17-2016 8:34 AM PDT (4 years ago)|
That 100 % loo doesn't have to be bad, it might just look like. Can i kindly ask you what kind of connection you are using? Wireless or Ethernet? Could i also ask you to post a dxdiag here?
What's your opinion?
|Network Disconnect||April-17-2016 11:52 AM PDT (4 years ago)|
You definitely want to have a look at your drivers. They are outdated. Graphics driver is half a year old, sound 4 years and your Network driver is half a year old. I had a look for you about the Intel(R) 82578DC Gigabit Network Connection driver, but it seems like they haven't brought one for Windows 10 yet, which might be a problem. Have you just recently upgraded to Windows 10? If so you might want to look at the compatibility mode for Diablo 3. Right click the .exe -> Properties -> Compatibility -> Set it to your previous windows version.
What's your opinion?
|Network Disconnect||April-20-2016 3:12 AM PDT (4 years ago)|
Taking a look at your tracer, we can indeed see some anomalies:
4 116 ms 112 ms 82 ms dbn-in1.ip.adsl.co.za [220.127.116.11]
In this hop the latency really increases compared to the previous ones. Then it goes back to normal, and then in hop 8 it goes even higher and stays like that until the end of the tracer:
8 217 ms 222 ms 207 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [18.104.22.168]
9 250 ms 242 ms 249 ms if-ae-5-30.tcore2.PV9-Lisbon.as6453.net [22.214.171.124]
10 200 ms 200 ms 200 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [126.96.36.199]
11 247 ms 233 ms 221 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [188.8.131.52]
12 260 ms 251 ms 233 ms if-ae-19-2.tcore2.L78-London.as6453.net [184.108.40.206]
13 202 ms 202 ms 213 ms if-ae-15-2.tcore2.LDN-London.as6453.net [220.127.116.11]
On the second traceroute, the same happens at the 8th hop:
8 196 ms 196 ms 196 ms if-ae-2-2.tcore1.JSO-Johannesburg.as6453.net [18.104.22.168]
9 215 ms 287 ms 236 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [22.214.171.124]
10 226 ms 234 ms 204 ms if-ae-5-80.tcore2.PV9-Lisbon.as6453.net [126.96.36.199]
11 215 ms 205 ms 205 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [188.8.131.52]
12 209 ms 207 ms 207 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [184.108.40.206]
13 290 ms 236 ms 205 ms if-ae-19-2.tcore2.L78-London.as6453.net [220.127.116.11]
14 210 ms 211 ms 208 ms if-ae-15-2.tcore2.LDN-London.as6453.net [18.104.22.168]
I would recommend contacting your internet provider and passing the traceroutes on to them so they can take a look and make sure everything is working good in these nodes that are showing high latency.
¿Tienes algún comentario sobre mi atención? ¡Házmelo llegar!
|Network Disconnect||April-23-2016 9:21 AM PDT (4 years ago)|
Apart from the Looking Glass Report, could you provide us with the rest of the information? It helps us check your case:
- Details of issue:
- Date/time it started:
- Internet Provider:
- Traceroute (right after a disconnection or whenever you're experiencing the issue)
- Pathping (right after a disconnection or whenever you're experiencing the issue)
Got feedback about the support I'm providing? Leave your comments here!
|Network Disconnect||April-27-2016 11:51 AM PDT (4 years ago)|
I am sorry to hear about this. Like Delmoryth said, could you please provide a dxdiag and MSInfo, traceroute and a pathping? If the data is too big to be posted on the forum directly, you can use a page like pastebin.com and post the link to it here then.
What's your opinion?