I can't connect to USEast and USWest however I am able to connect to Asia and Europe. I thought I was banned or restricted. I use a linksys router and when I connected directly using an ethernet I was able to connect to USEast. Even standing right next to my router it would still not connect and using my ethernet only is a significant pain. I ran the Battle.net Diagnostic tool and the following came up:
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.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.


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.






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

Connection to 63.240.202.120: Failed (ERROR: 10054)
Connection to 63.240.202.121: Failed (ERROR: 10054)
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)

i also tried using tracert useast.battle.net:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Billy>tracert useast.battle.net

Tracing route to useast.battle.net [63.240.202.131]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.1.1
2 9 ms 8 ms 9 ms 10.240.164.9
3 8 ms 9 ms 7 ms dstswr2-vlan2.rh.hntnny.cv.net [167.206.34.162]

4 * * * Request timed out.
5 11 ms 7 ms 9 ms rtr3-tg11-2.wan.hcvlny.cv.net [64.15.4.1]
6 * * * Request timed out.
7 * * * Request timed out.
8 10 ms 11 ms 10 ms ae-43-99.car3.NewYork1.Level3.net [4.68.16.197]

9 11 ms 10 ms 11 ms 192.205.33.93
10 19 ms 15 ms 17 ms cr2.n54ny.ip.att.net [12.122.130.130]
11 19 ms 17 ms 17 ms cr2.wswdc.ip.att.net [12.122.3.38]
12 18 ms 17 ms 16 ms 12.122.134.1
13 18 ms 20 ms 17 ms 12-122-254-98.attens.net [12.122.254.98]
14 19 ms 18 ms * mdf001c7613r0003-gig-10-1.wdc1.attens.net [63.24
0.193.10]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Users\Billy>
Any assistance would be greatly appreciated.

You are temporarily 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.

How am I temporarily restricted if it would allow me on when I connect directly to my modem. It only does not let me on when I use something that goes through my router.

Maybe you should read. Or did you miss the whole BDT Log, which is 3/4 of the post. Thanks.

---

Q u o t e:
------------------------------------------
Results
------------------------------------------

Connection to 63.240.202.120: Failed (ERROR: 10054)
Connection to 63.240.202.121: Failed (ERROR: 10054)
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)

---

He is restricted. Yes. He's restricted while using his router.

This is not fair...I have no idea why I have been restricted but i was.
Now i have been restricted to US west/East and Europe i can only connect to asia now...
to US west i have been restricted for about 3 days already :(
battle.net should give us the reason for restriction!!!!

Nowhere in there does he say he has an "unstable connection". It's simple, he's restricted, as the BDT displays. The BDT does not lie.

---

Q u o t e:
Originally posted by C0rr0sive

Sixen sir, you are a dumb!*#*, one for not listening to the situation and going by the log, ever think for a moment his routers wireless could be bad? He PLUGS STRAIGHT INTO THE !*#*ING ROUTER WITH A CAT5 CABLE AND CONNECTS TO BATTLE.NET JUST FINE, he goes on wireless and gets a unstable connection, talk about !*#*ing stupidity, not everything is what it appears, !*#* far, figured you of all idiots here would realize that.

---

Being the author of the sticky on this matter, I figure I might as well chime in here. When he's plugging into the "router" (sounds like he was actually plugging into his modem), his ISP is seeing a different MAC address. Many ISPs assign IP addresses based on the MAC address, so whenever he's directly connected to the modem, he'll have a different IP address (that isn't restricted) than the IP address he has over the wireless. Trust me, Sixen knows what he's doing.