The past few days, I've been unable to connect to US East on my Verizon hotspot. US West and the others connect fine, but it times out every time I try to connect to East. When I'm at home, I can connect to US East with no problems on the same laptop so I know it's not the machine and must either be Verizon or Bnet. Any help appreciated.
------------------------------------------------------------------
System Overview
------------------------------------------------------------------
User : Lansiar
Computer Name : LANSTOP
System Directory : C:\Windows\system32
Windows Directory : C:\Windows
Operating System : 6.1 (Windows Vista)
OS Build : 7601
Platform ID : 2
Service Pack : Service Pack 1
Service Pack Version : 1.0
Product Suites : Home Edition, Remote Desktop (Single),
Platform Type : Workstation
Physical Memory Usage : 40%
Total Physical Memory : 4224892928
Total Virtual Memory : 2147352576
Page File Size : 4294967295
Available Physical Memory : 2508795904
Available Virtual Memory : 2104877056
Available Page File : 4294967295
------------------------------------------------------------------
Processor Information
------------------------------------------------------------------
Processors : 8
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 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...
206.17.175.122
206.17.175.126
206.17.175.127
206.17.175.128
206.17.175.129
206.17.175.130
206.17.175.131
206.17.175.134
206.17.175.138
206.17.175.139
206.17.175.120
206.17.175.121
+++ Begin connection test with Battle.net server 206.17.175.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
+++ Begin connection test with Battle.net server 206.17.175.126
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
+++ Begin connection test with Battle.net server 206.17.175.127
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
+++ Begin connection test with Battle.net server 206.17.175.128
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
+++ Begin connection test with Battle.net server 206.17.175.129
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
+++ Begin connection test with Battle.net server 206.17.175.130
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
+++ Begin connection test with Battle.net server 206.17.175.131
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
+++ Begin connection test with Battle.net server 206.17.175.134
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
+++ Begin connection test with Battle.net server 206.17.175.138
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
+++ Begin connection test with Battle.net server 206.17.175.139
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
+++ Begin connection test with Battle.net server 206.17.175.120
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
+++ Begin connection test with Battle.net server 206.17.175.121
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
Jond
Blizzard Poster
1. Re: Can't connect to US East only 07/06/2012 09:47:40 AM PDT
i have alot of lag ingame in the games Warcraft 3 & Starcraft broodwar & is imposible play and after few seconds the game boot me to the channel i´ll send a ticket into my account of battle.net
www.youtube.com/viackeysi
Lansiar
USEast
5. Re: Can't connect to US East only 07/09/2012 08:48:50 AM PDT
What's your IP address when using the hotspot?
http://whatismyipaddress.com/
Today my IP on the device is below. I've even tried putting the computer in the DMZ and there's still no ping to any of the useast servers while uswest, Europe, and Asia all work perfectly.
70.192.131.203
Jond
Blizzard Poster
6. Re: Can't connect to US East only 07/09/2012 01:21:51 PM PDT
Thanks for the update. I don't see any long blocks on the IP address you mentioned. That means you're probably getting flagged with shorter restrictions. These restrictions will last 5 minutes to 12 hours, and are usually caused by rapidly connecting/disconnecting to Battle.net.
Lansiar
USEast
7. Re: Can't connect to US East only 07/10/2012 08:02:52 PM PDT
Thanks for the update. I don't see any long blocks on the IP address you mentioned. That means you're probably getting flagged with shorter restrictions. These restrictions will last 5 minutes to 12 hours, and are usually caused by rapidly connecting/disconnecting to Battle.net.
Negative, I've gotten those before and know what it looks like. I haven't been able to access useast on the hotspot for weeks and it stops when trying to connect to fastest server. Pings timeout with no connection refused, the connection simply isn't there. If there's no ban, I suppose it must be something with Verizon, but I don't understand why they would simply ban useast and no west or the others. Thanks for the info, anyway, I guess.
I am having this same problem on USEast only. I am not sure why as I do not use any third party programs and fairly mannered and dont even play that much anymore. What causes this. If I am IP banned as it looks like the case with others who have this problem why? If someone else is using my key, how can I find out? Thanks in advance.
