Not sure if I did this correctly, but here is the WinMTR result text:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
| 30.10.10.1 - 7 |
171 |
160 |
0 |
0 |
0 |
0 |
| 10.255.0.1 - 67 |
59 |
20 |
0 |
0 |
1 |
1 |
| s209-121-64-1.bc.hsia.telus. net - 7 |
171 |
160 |
1 |
2 |
4 |
2 |
| 154.11.12.219 - 67 |
59 |
20 |
7 |
10 |
39 |
26 |
| 74.125.50.110 - 7 |
171 |
160 |
7 |
7 |
10 |
8 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
43 |
0 |
0 |
0 |
0 |
0 |
| ________________________________________________ |
______ |
______ |
______ |
______ |
______ |
______ |
| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
|
|
|
|
|
|
You are showing loss at every node here. And the 67% loss around your ISP. So that’s pretty bad. Not sure, but is the first one your router? That’s showing 7%. You connected with wireless?
You can also just point them to the thread where I’m collecting the info for these tests Nicole. Its located here:
Not to mention, not every merged thread that was put here was solely about the east coast issue. So please refer them to this one if need be.
-For everyone having connection issues of various types: UPDATE 8-7-23
Thanks.
There is no loss in that test, all 171 packets make it to the last node that is responding. WinMTR does not handle IPv6 because the developer stopped working on it like 20 years ago.
It would be best if they just make a new thread so they can get troubleshooting for their issue.
Well even then, they are showing a loss. 171 sent 160 returned just on the last node alone.
And why then is the WinMTR page still showing the tool and the IP addresses for D4 if they are 20 years out of date?
The next hop would show 171 also, because there is no actual loss, the test doesn’t know how to handle the protocol.
I don’t work at Blizzard, but if I had to guess it would be the fact that WinMTR is a free tool and the majority of people in the US only have access to IPv4. There are other tools like PingPlotter that can provide some insight too, but you need to buy the premium version to use UDP (required for IPv6 tests) instead of TCP. Additionally, Blizzard hops don’t always respond to pings due to the protection mechanism on their network.
If that’s the case, what’s the point of even having the tests to run then? If the results are going to be useless?
This is a problem then. We need to be able to test these connections. I have spent a couple days now trying to gather reports on connections using the tools provided by Blizzard, only to find out they are kinda useless. Ugh.
This part I already know.
Again, IPv4 is the most common connection type, so the tests can gather data in some cases. Generally the staff and MVPs will ask for these because we don’t know someone’s connection type until they run the test. However, giving people the correct assessment is also crucial.
Allowing players to get troubleshooting on their issue in one thread keeps the conversation focused and easy to follow—especially when me or another helper can’t respond immediately.
A collection of WinMTRs in a megathread is useful in cases where a singular ISP is experiencing problems, because the test data can sometimes help pinpoint the troublesome node. But if it’s many ISPs, that’s too much random data.
Well then, I will continue to keep the thread updated. And review assessing the posts.
The problem I have is, that I think the traffic from the game itself is causing issues at a hardware level in some cases. Such as the posts about routers and modems being shut down only while playing D4. The same thing could be going on with some ISP pathing. This is in part why I have been pushing for these tests.
But that’s me.
The first one (|30.10.10.1) is my Sophos router.
I have no issues connecting to Battlenet in general, nor Diablo 3. Downloading anything from Battlenet launcher is also very fast (as it should be on my internet), be it updates, re-downloading the game, or anything else. It’s just Diablo 4 I am having trouble.
Well that follows with the majority. While I can’t guarantee you are having loss in your connection based on just the MTR, you very well might be anyway. And obviously there is an issue at some point.
What’s happening, exactly? The connection looks good.
If you want do that, sure, but I would focus on your experience vs collecting tests from others. There is simply too much data from varying ISPs to make use of the tests.
Every time I enter Diablo 4, immediately after I get placed in queue, I get error code 300001, player disconnected, please reconnect. I press the “accept” button and gets booted out of the game. This happened around June 13th (Tuesday). I do not remember altering any internet, firewall, anti-virus or in general my computer settings before this. For some reason I was able to play again on Wednesday night for a few hours, but after that it’s back to the same problem.
1 Like
For some players in the forum, running Bnet as admin, or reinstalling it after removing all associated data (in the Userdata folders), solved the issue. Did you try that yet?
Tried both running as Admin, and a clean re-install, before I made the post, didn’t work.
Would you be opposed to collecting an MSInfo and posting it on Pastebin? Might give some clues what’s happening around that time. And have you checked the event viewer? A disconnect will be logged there if the internet is cutting off.
I checked the event viewer and seems like the disconnects brought on this error:
The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout.
and some accompanied warnings:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Did you add an exception for Bnet and the game client in the Windows firewall? Usually it provides a pop-up alert. And how about the MSInfo?
Here is the pastebin link.
I checked my firewall and anti-virus logs and settings, nothing was blocked and no alerts so far. I am beginning to think it might be the most recent patch that broke something client-side in game.
