Just installed Diablo 2 yesterday to play for some nostalgia and battlenet cannot connect. Today it just continuously says disconnected from battlenet try again. Is something up with battlenet or is there anything I can do on my side to fix this? Tried the fixes they recommend but I cannot connect to battlenet so I cannot install the patch 1.14d.
I can see others have had this issue without much response so hopefully this doesn’t go to the void.
Hey, TeHSaint. I was able to find an active temporary restriction preventing your connection. We have a list of reasons of what can cause a temporary restriction here. It looks like this one is related to connection, so it could be a vpn, proxy, or business connection that caused the restriction. The restriction should be lifted on the morning of 2021-09-11T05:00:00Z.
Hey there KarlTang. I was able to verify the same connection-related restriction on your IP. The restriction will also expire on the morning of 2021-09-11T05:00:00Z.
I feel like Blizzard are getting extra hard on people to let them abandon this old gem. Which is apparent because when I orders D2 2000 they gave me the option to buy D2R when checkout.
Two weeks for forgetting vpn on? If this is not brutal what is?
The restrictions have been in place for years, so this is not a new thing to upset people. It is an attempt on an old Bnet platform to tamp down on bots and cheating, as well as keep the servers stable. It is an automated system - and it is not perfect. It helps though compared to nothing.
What is an issue mostly is that people don’t know that the Temp Restrictions exist so they accidentally trigger the system.
Download page for D2 (2000) should (in my opinion) contain a warning and link to the Support Article with the restrictions. That way new or returning players get a chance to read up on the system before playing.
In the interest of helping as many folks as possible, we encourage you to refer to our Sticky post below regarding Diablo II (2000) temporary restrictions:
This thread is now closed. If you encounter a different issue, please start your own thread.