Temp Ban... No Reason?

[barbowns]

Temp Ban... No Reason?

I just finished with a trade (did change chars like 2-3 times, mules) and when I exited the game I got logged of bnet and it says "Your connection has temp been restricted on this realm. Please try to log in again later"

No hacks, etc... here

Any reason why it won't let me log on? Could it be from changing out chars too quickly?

I've also been mfin Meph all day long, would that be a problem?

Thanks guys, just confused as to why I can't play right now.

 

[Alientank]

Armageddon has come.

 

[mhl12]

It's the new realm down message for 1.11.

 

[barbowns]

It's the new realm down message for 1.11.

Meaning everyone on UsEast got it? Or that I was entering/exiting too quick?

 

[Ismalia]

Meaning everyone on UsEast got it? Or that I was entering/exiting too quick?

Possibly either or. My vote would be that is for entering/exiting/too many games in too short a time before Realm Down.

 

[Painman]

I keep a mule in a game for at least 30 seconds now and slowed the char switching down a little, I haven't got kicked off since the first couple days of the patch.

*knocks wood*

 

[muzyk]

its because you were going into too many games too quickly, blizz does this in order to stop botters from botting. if they notice you going into too many games very quickly you'll have a temp ban for around 10-20 mins and sometimes up to hours if you keep trying to log into account

 

[bladesyz]

its because you were going into too many games too quickly, blizz does this in order to stop botters from botting. if they notice you going into too many games very quickly you'll have a temp ban for around 10-20 mins and sometimes up to hours if you keep trying to log into account

It's a completely inane and retarded way to stop botting, if you ask me. When it inconveniences legitimate players a lot more than botters, you know there's something wrong with the method.

 

[Ismalia]

It's a completely inane and retarded way to stop botting, if you ask me. When it inconveniences legitimate players a lot more than botters, you know there's something wrong with the method.

All it really means is that you spend a few more minutes in a game. Do a Countess or Meph run while you're waiting. It's not really a very big deal.

If it keeps bots out for a little bit, I'm all for it.

 

[Ryhan]

I got a temp ban a couple of days ago for scrolling the mouse wheel to fast.

 

[Hacknshoot]

I got a temp ban a couple of days ago for scrolling the mouse wheel to fast.

Yeah, I had that problem happen once too. Of course, it also happened after I spammed Holyshield about 40 times in a row. So it couldbe the strain of changing skills so quickly and having to load the info for them off of the server, that would kick you off. It was kinda weird.

 

[FatalAquaintance]

I got a temp ban a couple of days ago for scrolling the mouse wheel to fast.

HAHAHAH i got that too!! I was cleaning my mouse and changed my pally's auras too many times too fast and poof.. i got booted out lol

 

[mhl12]

blizzard's server does random stuff sometimes. The only way to get around it is wait it out or use a different IP. Take a look at my bnet connection guide for more info.

 

[Swerdlow]

It's actually very easy to get around R/D, even with a static IP address.

 

[barbowns]

It's actually very easy to get around R/D, even with a static IP address.

Care to share?

 

[Swerdlow]

Sure...ok, so assuming you have a high speed modem and router, running windows XP:

Click Start > Control Panel > Network Connections > Local Area Connection OR Wireless Network Connection (whichever you use).

Open up your connection, go to Support Tab > Details

Copy down the "Physical Address"

Close that window, then go to General Tab > Properties > Configure > Advanced Tab

In the property box highlight "Network Address".

Take the physical address that you copied down, enter it in (change the value from "not present").

Change the last two digits to anything you like.

Don't hit "OK" yet. Go to your modem/router, and unplug them both. Hit "OK" on your computer, turn the computer off, then reboot the network.

All done!