Blizzard is just ignoring the "Connection interrupted issue"
Hey Golfire,
As mentioned in the other thread, this type of problem can be caused by a number of issues. I agree that your problem is not related to packet loss, but the only way to figure out what the problem is would be to troubleshoot it with you. Firewalls, security programs, etc can potentially cause this problem.
I did see your tags today, but my weekend is Monday and Tuesday, and I wasn’t working the forums when you tagged me. If you’ve refunded the game, I entirely understand, but again as mentioned we can work with players if they reach out to support.
Keep in mind that there are multiple forums that we need to keep up with here, and I cannot personally respond to every player in every thread. If you want a guaranteed answer to your specific problem, please contact support. Otherwise, you would want to rely on the community here in the forums.
Obviously if while troubleshooting this between players, we find a problem, we’ll find a good thread and post about it as a widespread issue. However, these threads keep getting flooded with a bunch of players trying to jump on the bandwagon and we simply cannot help everybody who hops into a single thread. Troubleshooting like that is entirely too chaotic, which is why I suggest this method in each of the threads I locked.
Note: looking at your winMTR from your other thread, I can’t point directly to anything in the connection path, so I’d probably suggest if you do decide to troubleshoot this that you contact support so we can get an MSInfo file from you and check out your PC and see if we can find out what’s going on. Typically if it’s not in the winMTR, it’s something with a firewall, security program, quality of service setting, or other program conflict, and those can be difficult to diagnose without some digging.
Copied word for word from the official Diablo II: Resurrected forum. Read the whole thread — and reply — on us.forums.blizzard.com. Get an alert for the next one