Ok so the story goes I played last ladder reset for a good bit and stopped playing. Started back up this past ladder reset and all is going fine while gaming at home from my laptop. The problem comes in when I come to work for a week and am on Satellite internet, then I cannot connect to USEAST. I can connect to USWEST or other servers and I played on this very connection last ladder reset.
I've tried the bnetdiagtool and the beta version which I will include at the end of this post. The original bnetdiagtool shows it hanging up at checking for ipban (for hours) and the beta shows everything going through great.
I have called Blizzard tech support and no luck (I don't blame them since this game is 10 years old) so I decided to give the forums a try. The most me and the tech guy could figure was something wrong on my ISP (Hughesnet) side.
I have firewalls allowing D2 and I've tried with firewalls completely off. I have the router setup the same way I did last time I played with the ports forwarded.
There should be some kind of magic dust in the blizzard store that fixes all connection problems...$10 sounds fair :P
BnetDiagTool2.2
------------------------------------------------------------------
System Overview
------------------------------------------------------------------
------------------------------------------------------------------
Processor Information
------------------------------------------------------------------
------------------------------------------------------------------
Process Snapshot
------------------------------------------------------------------
------------------------------------------------------------------
Application Log
------------------------------------------------------------------
Running version 2.2
+++ Begin application initialization.
Initializing console...
Assigning console control handler...
Loading the Winsock library...
Initialization complete.
+++ Begin hostname resolution on useast.battle.net
Querying information about the host...
Hostname successfully resolved, displaying results...
63.240.202.139
63.240.202.120
63.240.202.121
63.240.202.122
63.240.202.126
63.240.202.127
63.240.202.128
63.240.202.129
+++ Begin connection test with Battle.net server 63.240.202.129
Creating socket...
Binding socket to any available address...
Placing socket into asynchronous mode...
Initiating connection...
Attempting to establish a connection with the server...
Connection established with the server, determining if user is banned...
BnetDiagToolBeta
-----------------------------------------------------------------------------------
Battle.net Connection Diagnosis
-----------------------------------------------------------------------------------
Begin connection diagnosis on: useast.battle.net
Retrieving information about the realm... Success
Begin testing the user's connection with Battle.net...
Testing connection with server: 63.240.202.139
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.120
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.121
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.122
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.126
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.127
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.128
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.129
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
------------------------------------------
Results
------------------------------------------
Connection to 63.240.202.139: Success
Connection to 63.240.202.120: Success
Connection to 63.240.202.121: Success
Connection to 63.240.202.122: Success
Connection to 63.240.202.126: Success
Connection to 63.240.202.127: Success
Connection to 63.240.202.128: Success
Connection to 63.240.202.129: Success
-----------------------------------------------------------------------------------
Battle.net Connection Diagnosis
-----------------------------------------------------------------------------------
Begin connection diagnosis on: useast.battle.net
Retrieving information about the realm... Success
Begin testing the user's connection with Battle.net...
Testing connection with server: 63.240.202.139
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.120
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.121
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.122
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.126
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.127
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.128
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
Testing connection with server: 63.240.202.129
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Success
Connection sucessfully established.
------------------------------------------
Results
------------------------------------------
Connection to 63.240.202.139: Success
Connection to 63.240.202.120: Success
Connection to 63.240.202.121: Success
Connection to 63.240.202.122: Success
Connection to 63.240.202.126: Success
Connection to 63.240.202.127: Success
Connection to 63.240.202.128: Success
Connection to 63.240.202.129: Success
|
|