World of Warcraft

View All Posts by This User Toggle Ignore / Unignore This User
  • Level: 2 Random Team
  • Gateway: Lordaeron
  • 0. can not connect to US West   11/26/2008 06:22:48 PM PST
last 4 days, i tried to connect to us west but then it showed this message: unable to connect to battle.net.
You may be trying to connect to an invalid Battle.net server..." but the day before that, it still work normally.
I searched for help in forum and there's instruction to download Bnetdialog and i did step by step like it said. And here is the result:
------------------------------------------------------------------
System Overview
------------------------------------------------------------------
User : Main
Computer Name : MAIN-PC
System Directory : C:\Windows\system32
Windows Directory : C:\Windows
Operating System : 6.0 (Windows Vista)
OS Build : 6001
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 : 46%
Total Physical Memory : 2144813056
Total Virtual Memory : 2147352576
Page File Size : 4294967295
Available Physical Memory : 1145913344
Available Virtual Memory : 2118193152
Available Page File : 3044929536



------------------------------------------------------------------
Processor Information
------------------------------------------------------------------
Processors : 4
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 : No
PAE Enabled : Yes



------------------------------------------------------------------
Process Snapshot
------------------------------------------------------------------
[System Process]
System
smss.exe
csrss.exe
wininit.exe
csrss.exe
services.exe
lsass.exe
lsm.exe
winlogon.exe
svchost.exe
svchost.exe
svchost.exe
svchost.exe
svchost.exe
svchost.exe
audiodg.exe
SLsvc.exe
svchost.exe
svchost.exe
aawservice.exe
spoolsv.exe
svchost.exe
avgamsvr.exe
avgupsvc.exe
avgrssvc.exe
avgemc.exe
avgrssvc.exe
svchost.exe
svchost.exe
svchost.exe
SearchIndexer.exe
taskeng.exe
dwm.exe
explorer.exe
MSASCui.exe
avgcc.exe
rundll32.exe
rundll32.exe
jusched.exe
OpenDNS Updater.exe
sidebar.exe
WmiPrvSE.exe
ehtray.exe
RocketDock.exe
VistaStartMenu.exe
ehmsas.exe
btdna.exe
sidebar.exe
alg.exe
unsecapp.exe
YahooMessenger.exe
firefox.exe
taskeng.exe
war3.exe
wmplayer.exe
mfpmp.exe
SearchProtocolHost.exe
SearchFilterHost.exe
explorer.exe
BnetDiagTool.exe



------------------------------------------------------------------
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 *realm.battle.net
Querying information about the host... Error! 11001

+++ Begin connection test with Battle.net server 255.255.255.255
Creating socket...
Binding socket to any available address...
Placing socket into asynchronous mode...
Initiating connection...
Attempting to establish a connection with the server... Error! 10049

I would like yo know what is happening between my network and bnet.
View All Posts by This User Toggle Ignore / Unignore This User
Sixen
  • USWest
  • 1. Re: can not connect to US West   11/27/2008 12:40:36 AM PST
Use the correct realm, uswest.battle.net.

The Chat Gem Lives!
http://www.Sixen.org
View All Posts by This User Toggle Ignore / Unignore This User
  • Level: 2 Random Team
  • Gateway: Lordaeron
  • 2. Re: can not connect to US West   11/27/2008 01:13:30 AM PST
oh, sorry... and again, here's the result:
------------------------------------------------------------------
System Overview
------------------------------------------------------------------
User : Main
Computer Name : MAIN-PC
System Directory : C:\Windows\system32
Windows Directory : C:\Windows
Operating System : 6.0 (Windows Vista)
OS Build : 6001
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 : 56%
Total Physical Memory : 2144813056
Total Virtual Memory : 2147352576
Page File Size : 4294967295
Available Physical Memory : 923353088
Available Virtual Memory : 2118193152
Available Page File : 2871365632



------------------------------------------------------------------
Processor Information
------------------------------------------------------------------
Processors : 4
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 : No
PAE Enabled : Yes



------------------------------------------------------------------
Process Snapshot
------------------------------------------------------------------
[System Process]
System
smss.exe
csrss.exe
wininit.exe
csrss.exe
services.exe
lsass.exe
lsm.exe
svchost.exe
winlogon.exe
svchost.exe
svchost.exe
svchost.exe
svchost.exe
svchost.exe
audiodg.exe
SLsvc.exe
svchost.exe
svchost.exe
aawservice.exe
spoolsv.exe
svchost.exe
avgamsvr.exe
avgupsvc.exe
avgrssvc.exe
avgemc.exe
avgrssvc.exe
svchost.exe
svchost.exe
svchost.exe
SearchIndexer.exe
alg.exe
taskeng.exe
taskeng.exe
dwm.exe
explorer.exe
MSASCui.exe
avgcc.exe
rundll32.exe
rundll32.exe
jusched.exe
OpenDNS Updater.exe
WmiPrvSE.exe
sidebar.exe
ehtray.exe
RocketDock.exe
VistaStartMenu.exe
btdna.exe
ehmsas.exe
sidebar.exe
unsecapp.exe
YahooMessenger.exe
firefox.exe
war3.exe
VisualCustomKick.exe
prevhost.exe
prevhost.exe
notepad.exe
dllhost.exe
BnetDiagTool.exe



------------------------------------------------------------------
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 *uswest.battle.net
Querying information about the host... Error! 11001

+++ Begin connection test with Battle.net server 255.255.255.255
Creating socket...
Binding socket to any available address...
Placing socket into asynchronous mode...
Initiating connection...
Attempting to establish a connection with the server... Error! 10049
View All Posts by This User Toggle Ignore / Unignore This User
Sixen
  • USWest
  • 3. Re: can not connect to US West   11/27/2008 08:00:50 AM PST

Q u o t e:
Use the correct realm, uswest.battle.net.


Use exactly what is bolded, remove the asterisk.

The Chat Gem Lives!
http://www.Sixen.org
View All Posts by This User Toggle Ignore / Unignore This User
  • Level: 2 Random Team
  • Gateway: Lordaeron
  • 4. Re: can not connect to US West   11/27/2008 01:11:17 PM PST
it said "...You appear to be IP banned. Error! 10054...", is it possible to know long will it take? cause it been 5 days already. And i'm wondering how'd my ip got ban... cause i never try to use some kind of hack. Only those support tools like Custom Kick, Auto Refresh etc.
View All Posts by This User Toggle Ignore / Unignore This User
Sixen
  • USWest
  • 5. Re: can not connect to US West   11/27/2008 01:27:51 PM PST

Q u o t e:
cause i never try to use some kind of hack. Only those support tools like Custom Kick, Auto Refresh etc.


Those are hacks and were never supported and never will be. Using those could've possibly gotten you restricted.



Unfortunately, we cannot tell you the exact reason as to why you have been restricted, or the amount of time you'll be restricted. The only thing we can show it the list of reasons for restrictions and give you a timeframe. Please note that restrictions cannot be removed or shortened, the only solution is to wait it out. You can view the thread below for more information about restrictions:
(http://forums.battle.net/thread.html?topicId=10972137363).

Now, there are different types of restrictions. First, there's the Realm Down message which only appears on Diablo2. This type of restriction lasts between 2 minutes and 12 hours. Next, there's the Temporary Restriction and the Extended Restriction. Temporary restrictions last anywhere from 2 minutes to 72 hours and Extended Restrictions last between 3 days and 2 weeks. If you would like to find out what type of restriction it is, send an e-mail to support@blizzard.com. Please note, it will take an employee 2-3 business days to respond to you.

The Chat Gem Lives!
http://www.Sixen.org
View All Posts by This User Toggle Ignore / Unignore This User
Protossking2
  • USWest
  • 6. Re: can not connect to US West   06/28/2009 03:21:34 PM PDT
yah i sorta have a similar problem i can't get on US West but i can get on US east, Asia, and Europe its really getting me pissed off... all of my friends are on west and i cant get on West its really gay.
View All Posts by This User Toggle Ignore / Unignore This User
Sixen
  • USWest
  • 7. Re: can not connect to US West   06/28/2009 08:58:03 PM PDT
You're restricted as well.

The Chat Gem Lives!
http://www.Sixen.org/
Forum Nav : Jump To This Forum
Blizzard Entertainment