I have made a post last week about this. Blizz didnt like it so got muted and post removed. paying customers has no say anymore for what they pay for.
anycase…
I still keep getting this 1016 errors but they are mostly when joining a party or while in a party or changing characters while in a party… or when you just log on.
When you are Solo and ingame it runs for a few hours not to bad.
The first five hops are inside your internal network (10.x.x.x and 192.168.x.x address ranges), the traffic then goes out to 196.25.120.217 (your South African ISP) but then, instead of carrying on towards the destination, comes back into a 10.x.x.x address, i.e. back into your internal network.
As you apparently work for the ISP, perhaps you could try and explain why traffic intended for a remote address, after having left the home network / private IP address ranges, is being routed back into the internal network by the ISP…
I don’t worry about 137.* nodes because the data packet loss and latency didn’t continue down. (Likewise, you don’t worry about the 18% data packet loss at bundle-ether11.martr1.marseille.opentransit.net - 18)
The last hop looked fine to me. I can’t pinpoint any issue from your log. But, I can tell you that it wasn’t at 137.* nodes.
I did everything - resetting windows 10 even. Disconnections continued UNTIL I disabled QoS yesterday morning - on Maskraider’s advice. The result is the order has been reversed regarding network disconnects and 1016. Prior, 10 disconnects to every successful game connection. Now: 1 disconnect to every 12 or so successful connection. I’m sure there are some other tweaks to be done, such as adjusting in-game settings, or corrupted game cache folders that simply need deleting. Otherwise, check game updates regularly to see if patches have been release to fix certain bug issues.
@Shaolin
You may also check the QoS settings on Windows’ Network Settings.
My QoS setting is Disabled by default. Not sure if same for yours.
Good Luck.
It could also be a new issue related to bitrate. I usually play bit 32 for the smoothness of streaming, but bit 64 disconnects much less, although yes, my QoS is Disabled in network settings.
*I have left all communities and my clan
*Before every D3 Session i release/renew IP
*I close battle.net upon launching a D3
With these things done it does lessen the disconnects but there are still some.
I have noticed like this morning i ran a quick GR102 and GR105 without any problems but it seems when D3 hits peaks the disconnects are much more, like i logon and disconnect, join party then disconnect plus changing characters.
I have checked we don’t have QoS on our network but ill make sure for my PC and maybe as you mentioned corrupt cache files.
Would you suggest i disable the QoS Packet Scheduler in the LAN > properties > context menu?
or the one in the Group Policies?
I know all the posts and all the comments, i have read 90% of them over and over but i really really think this might also be a problem being populated unknowingly from the D3 servers, i mean this definitely might be a possibility since everything ran 100% for me from season 15 onwards and only from like season 21 these crazy issues started all of a sudden.
Notices
I also seen this that if i change my region the problems are gone but i cannot do this i got friends on EU
I only get a disconnect error 1016 but it looks more like a GUI disconnect because i can still use my abilities and move mouse and even when I’m busy speaking to someone the chat being send goes to say chat and all of this happens without any kind of delay even when my MS bar is green.
Any case any and all advice is welcome and will be tried.
have a nice day.
I am trying to give as much info about this as possible so there might be useful stuff or irrelevant stuff non the less its still information for someone else
so i just ran my WinMTR again and these 2 address has almost 10-50% packet loss. i made ticket to blizzard maybe they mute me again or delete again. but its okay it will only prove my point again.
That’s because the routers at Blizzard’s network edge are configured to drop / deprioritise ICMP traffic (the type of packets used by PING, TRACERT and WinMTR). It’s completely normal to find that in a trace, even for people that aren’t having problems.
In your earlier post you said “I am the ISP” from which I took it that you worked for an ISP. In which case, I’m kind of surprised you don’t know about ICMP deprioritisation.
[quote=“Rekkov-2887, post:1, topic:2466, full:true”]
So as the title says
As you can see my packet loss is not on my network and even if it was i could solve it because i am the ISP.
and even also a 1-3% packet loss should not make a difference because i play very competitive other live online games.
There are so MANY people suffering due to this error and all of a sudden its a client problem, i cannot understand this.
It would be really awesome if a fix could be put in place for this.
[/quote]’’
i can’t disagree with this as I did not have these connection problems before the last patch, some time last week. That must have written some conflicting codes with the normal network set-up.
I can suggest opening network adapter from device manager settings, clicking properties, and disabling all entries marked with “offload” such as checksum offload, large send offload etc, though IDK how effective that would be with connection issues
As Meteorblade said, as57976.net nodes are configured to de-prioritize ICMP messages. This had been clarified by Blizzard support.
Many ISP do this for security or performance concerns. It is normal.
Similar reason for those “No response from host” nodes.
For these nodes, their data is irrelevant. We should read further down to see if data loss/latency continue down. If these nodes have issues, they shall reflect in subsequent hops below. Otherwise, they are fine.
18)