World of Warcraft

View All Posts by This User Toggle Ignore / Unignore This User
Twisted398
  • USEast
  • 0. Unable to Connect   09/03/2011 01:06:42 AM PDT
I hopped onto the Diable 2 scene a little late (or at least I tried to) and just bought and played the game a few days ago. Everything seemed to work fine until the next day when I tried to log on and had a big Unable to connect to Battle.net error pop up. I am able to connect to every server except for US East. I've tried re-installing, following tech support guides, etc.

Here are the results of a diagnostics test:


-----------------------------------------------------------------------------------

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.122
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Failed
Unable to establish a usable connection with the server.


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... Failed
Unable to establish a usable connection with the server.


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... Failed
Unable to establish a usable connection with the server.


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... Failed
Unable to establish a usable connection with the server.


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... Failed
Unable to establish a usable connection with the server.


Testing connection with server: 63.240.202.130
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Failed
Unable to establish a usable connection with the server.


Testing connection with server: 63.240.202.131
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Failed
Unable to establish a usable connection with the server.


Testing connection with server: 63.240.202.134
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Failed
Unable to establish a usable connection with the server.


Testing connection with server: 63.240.202.138
Creating socket... Success
Assigning socket a local address... Success
Connecting to the server... Success
Determining the connection's stability... Failed
Unable to establish a usable connection with the server.


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... Failed
Unable to establish a usable connection with the server.


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... Failed
Unable to establish a usable connection with the server.


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... Failed
Unable to establish a usable connection with the server.






------------------------------------------
Results
------------------------------------------

Connection to 63.240.202.122: Failed (ERROR: 10054)
Connection to 63.240.202.126: Failed (ERROR: 10054)
Connection to 63.240.202.127: Failed (ERROR: 10054)
Connection to 63.240.202.128: Failed (ERROR: 10054)
Connection to 63.240.202.129: Failed (ERROR: 10054)
Connection to 63.240.202.130: Failed (ERROR: 10054)
Connection to 63.240.202.131: Failed (ERROR: 10054)
Connection to 63.240.202.134: Failed (ERROR: 10054)
Connection to 63.240.202.138: Failed (ERROR: 10054)
Connection to 63.240.202.139: Failed (ERROR: 10054)
Connection to 63.240.202.120: Failed (ERROR: 10054)
Connection to 63.240.202.121: Failed (ERROR: 10054)
View All Posts by This User Toggle Ignore / Unignore This User
  • Level: 1
  • Gateway: Azeroth
  • 1. Re: Unable to Connect   09/03/2011 10:15:56 AM PDT

Q u o t e:
Connection to 63.240.202.122: Failed (ERROR: 10054)


You have an extended 2 week IP restriction.

With very few exceptions, this is caused by use of an illegal CD-key (torrented, keygen, 3rd party website, etc.). The IP ban can not be removed, all you can do is wait it out.

[ Post edited by Darknesscalled- ]

View All Posts by This User Toggle Ignore / Unignore This User
Twisted398
  • USEast
  • 2. Re: Unable to Connect   09/03/2011 02:09:15 PM PDT
Well I sure am glad I was banned for no reason... I haven't even completed the first quest. I have maybe 30 minutes of play time, most of which was just me sitting AFK, and I get banned? Am I getting trolled by Blizzard or something because this seems pretty ridiculous.

May I ask the reason for my ban?

[ Post edited by Twisted398 ]

View All Posts by This User Toggle Ignore / Unignore This User
Creaver
  • USEast
  • 3. Re: Unable to Connect   09/03/2011 06:08:22 PM PDT
from what he said, it looks like the key you used is bad-pirated. either that or their service picked up something on your computer it didn't like...(maphack) or something of that nature. The usual case is that if you recieved the key from someone else and they were using something they detected at TOS violation--- your ip would be pray to the "bad" things other people did using that keycode.

If you bought the key directly from blizzard --- then you need to contact their customer service to find out what the problem was.
View All Posts by This User Toggle Ignore / Unignore This User
  • Level: 1
  • Gateway: Azeroth
  • 4. Re: Unable to Connect   09/03/2011 08:09:09 PM PDT

Q u o t e:
May I ask the reason for my ban?


Like I said, the most common reason for a 2 week ban is an illegal CD-key. If you contact Blizz tech support, they can tell you how much longer is left on the ban, they can't tell you the exact reason for it and they can't remove it.


Q u o t e:
Am I getting trolled by Blizzard or something


The system that does IP restrictions is automatic

[ Post edited by Darknesscalled- ]

View All Posts by This User Toggle Ignore / Unignore This User
Twisted398
  • USEast
  • 5. Re: Unable to Connect   09/03/2011 10:18:47 PM PDT
I purchased my copy digitally through Bnet, so my CD key is fine. I haven't used any third party software or mods. Is there a list of reasons posted somewhere that could help me figure out why I was banned?

After installing the game I joined a server with 2 of my friends, neither of which have ever had or have any violations. I played maybe 10 minutes with them and they taught me how to kill things, what the vendors did, where to find quests, etc. They got off for the night and I started my own server to level up on my own for a while. I ended up playing Xbox instead and never completed a quest and was just sitting AFK for maybe 30-45 minutes before logging out manually.

Is there some weird series of events there that made the server think I was a bot or something? I can't seem to figure out what it could be.
View All Posts by This User Toggle Ignore / Unignore This User
  • Level: 1
  • Gateway: Azeroth
  • 6. Re: Unable to Connect   09/03/2011 11:08:07 PM PDT
Copy-paste for you:


Q u o t e:

Common causes for 2 week extended restrictions include, but are not limited to:

* Attempting to use an illegal CD-Key (Most common reason)
* Excessive spamming or flooding in a channel
* Spamming over multiple channels - even if it is just one line per channel.
* Use of flood or load bots.
* Harrassment of another player and/or clan.
* Advertisement of an inappropriate website URL.
* Use of third-party/add-on programs (hacks) - these include but are not limited to sending bad packets, flooding the server(s), and the use of hack programs.


Also, if you share an IP address with someone, it's possible they could have gotten you restricted.

Otherwise, like I said above, there's no way to tell exactly why you got a 2 week IP ban, it's almost always due to an invalid CD-key though.

If you purchased it directly from the BNet store and have it registered through a www.battle.net account, I would recommend contacting Customer Support to figure out what's up.

[ Post edited by Darknesscalled- ]

Forum Nav : Jump To This Forum
Blizzard Entertainment