I am unable to connect to USEast or West in Diablo 2 or in WC3. I can connect to Europe or Asia somewhat. It usually doesn't go past "Downloading Data Files," however. It has been this way for several months, possibly over a year, I can't recall. I believe I have actually been in two different homes since it has been like this, though I'm not 100% certain.
Here is my log from bnetdiagtool
------------------------------------------------------------------
System Overview
------------------------------------------------------------------
System Directory : C:\Windows\system32
Windows Directory : C:\Windows
Operating System : 6.1 (Windows Vista)
OS Build : 7600
Platform ID : 2
Service Pack :
Service Pack Version : 0.0
Product Suites : Home Edition, Remote Desktop (Single),
Platform Type : Workstation
Physical Memory Usage : 36%
Total Physical Memory : 4294037504
Total Virtual Memory : 2147352576
Page File Size : 4294967295
Available Physical Memory : 2726952960
Available Virtual Memory : 2104930304
Available Page File : 4294967295
------------------------------------------------------------------
Processor Information
------------------------------------------------------------------
Processors : 2
Processor Architecture : x86 (Intel)
Processor Family : Pentium
Page Size : 4096
Min. Memory Address : 65536
Max. Memory Address : 2147418111
3D Now! : No
MMX : Yes
SSE3 : Yes
SSE2 : Yes
SSE : Yes
Channels : No
Soft. Float Emulation : No
DEP Enabled : Yes
PAE Enabled : Yes
------------------------------------------------------------------
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.122
63.240.202.126
63.240.202.127
63.240.202.128
63.240.202.129
63.240.202.130
63.240.202.131
63.240.202.134
63.240.202.138
63.240.202.139
63.240.202.120
63.240.202.121
+++ Begin connection test with all servers on useast.battle.net
+++ Begin hostname resolution on useast.battle.net
Querying information about the host...
Hostname successfully resolved, displaying results...
63.240.202.122
63.240.202.126
63.240.202.127
63.240.202.128
63.240.202.129
63.240.202.130
63.240.202.131
63.240.202.134
63.240.202.138
63.240.202.139
63.240.202.120
63.240.202.121
+++ Begin connection test with Battle.net server 63.240.202.122
Creating socket...
Binding socket to any available address...
Placing socket into asynchronous mode...
Initiating connection...
Attempting to establish a connection with the server... Error! 0
This message repeats for all IPs.
+++ Exiting application.
Closing the application log...
When using the application on Asia/EU servers, this is what happens
+++ Begin hostname resolution on europe.battle.net
Querying information about the host...
Hostname successfully resolved, displaying results...
213.248.106.201
213.248.106.202
213.248.106.204
213.248.106.65
213.248.106.66
213.248.106.67
213.248.106.68
213.248.106.200
+++ Begin connection test with Battle.net server 213.248.106.201
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...
The tool does not make it past this point regardless of how long it runs.
I would really like to be able to play these games. Any help would be really appreciated.
Martyt
Blizzard Poster
1. Re: Cant connect to USEast/West, but can to E 04/23/2012 06:24:35 PM PDT
I'm not seeing any IP restrictions for USEast or USWest.
Using the Telnet command will determine if you can connect properly to a Battle.net server.
What does the Telnet command do?
* The telnet command tests the connection from your computer to the target location you specify.
* Using this command will determine if your computer can connect correctly to Battle.net.
* Using the information you gain from this command, you can contact your Internet Service Provider (ISP) and work with them on solving your Internet connection issues, if necessary.
Steps to run the Telnet command can be found below:
For Windows: (Note for Vista users, please view the bottom paragraph on how to install the Telnet program)
1. Click on the Start button on the taskbar and then Run....
2. In the Run window, type TELNET and click on the OK button to open the Telnet window.
3. Type the following into the Telnet Window:
o REALM.battle.net 6112
And press enter. (Note: The first character is the letter O as used in Oscar. Replace the word REALM with the realm you are trying to connect to, example USWEST, USEAST, EUROPE or ASIA, please make sure to check the spelling and make sure you have to correct spacing and the number on the end before pressing enter)
4. You if the connection is working correctly, you will get a message that you are connecting to Battle.net...
5. Press C and the server should list your IP address and will automatically disconnect you. If this happens then your connection is working. If the connection is not successful you may receive a "The current directory is invalid" error which indicates no active Internet connection, or the presence of a firewall restricting TCP port 6112. If the connection freezes before displaying the final information there may be a security feature (firewall or router) in place preventing the connection from completing.
Note for Windows Vista users:
Vista does not have Telnet installed by default, you may have to add this program manually so that it can be run.
1. Open "Control Panel"
2. Select "Programs and Features"
3. In the left column, select "Turn Windows features on or off" (You may have to answer a UAC prompt at this point)
4. Check the box next to TELNET and Click Ok, and the wait until this completes and it should be ready to run as normal.
Elshako
USEast
2. Re: Cant connect to USEast/West, but can to E 06/10/2012 03:45:41 AM PDT
