• Welcome to Valhalla Legends Archive.
 

War2 and War3 sudden disconnects

Started by UserLoser., November 25, 2003, 08:05 PM

Previous topic - Next topic

UserLoser.

Just today, after logging on, joining chat using Warcraft II or Warcraft III, I've been getting disconnected and don't know why.  I was sitting here for a while thinking I screwed up something on my side, but then I go on EternalChat  which usually never has problems, using War2, then I get disconnected!  Does anybody know if there were any changes lately in the servers?  Packet restrictions on certain clients, or ...?

Edit: This is happening right after I join a channel, is anyone else having this problem?

Note: IPbanned on East, Asia, and Europe due to this crappy problem!

MyndFyre

#1
ewww sux0rs.  Sorry to hear that bro.
QuoteEvery generation of humans believed it had all the answers it needed, except for a few mysteries they assumed would be solved at any moment. And they all believed their ancestors were simplistic and deluded. What are the odds that you are the first generation of humans who will understand reality?

After 3 years, it's on the horizon.  The new JinxBot, and BN#, the managed Battle.net Client library.

Quote from: chyea on January 16, 2009, 05:05 PM
You've just located global warming.

Spht

This is usually due to reconnecting on the same server address periodically. You should change server address (not gateway, address) to prevent this. If you attempt to reconnect over and over while getting disconnected after logon, you'll be IP banned.

Stealth

#3
I have both a Warcraft II and a Warcraft III bot logged onto West, both development builds of StealthBot; neither is having disconnect problems. (Reconnected both of them as well.)
- Stealth
Author of StealthBot

Spht

It's user-specific problem. I've been having the same problem sometimes before, I just change server address and it no longer does it.

Spht

Quote from: UserLoser. on November 25, 2003, 08:20 PM
Why would it be doing it to me only on War2 then? - I tried on D2, no disconnect, switched to War2 and disconnected

*shrug* Maybe server only remembers when you disconnect you based on server & product.

Mesiah / haiseM

Quote from: Spht on November 25, 2003, 08:12 PM
This is usually due to reconnecting on the same server address periodically. You should change server address (not gateway, address) to prevent this. If you attempt to reconnect over and over while getting disconnected after logon, you'll be IP banned.

According to UserLosers statement, it happens after he joins a channel. If an IP ban is put in effect, he would not make it past the connection stage, Silly.

It is most definatly a Client Side Problem, as I have also had a warcraft 2 bot logged on right around the same time, no problems here..
]HighBrow Innovations
Coming soon...

AIM Online Status: 

Spht

#7
Quote from: MesiaH on November 26, 2003, 01:24 PM
Quote from: Spht on November 25, 2003, 08:12 PM
This is usually due to reconnecting on the same server address periodically. You should change server address (not gateway, address) to prevent this. If you attempt to reconnect over and over while getting disconnected after logon, you'll be IP banned.

According to UserLosers statement, it happens after he joins a channel. If an IP ban is put in effect, he would not make it past the connection stage, Silly.

It is most definatly a Client Side Problem, as I have also had a warcraft 2 bot logged on right around the same time, no problems here..

Of course you're not having any problems, because you never violated anything. Server will disconnect violators after logging on & joining start-up channel.

Mesiah / haiseM

Sorry for any confusion, but I would not have posted unless i took my bot into thurough testing on this matter, I have, and I have in many other cases similar to this, same results for me everytime.

Perhaps your buffer and or queue was not cleared when you reconnected, that can never be good..
]HighBrow Innovations
Coming soon...

AIM Online Status: 

Spht

Quote from: MesiaH on November 26, 2003, 01:36 PM
Perhaps your buffer and or queue was not cleared when you reconnected, that can never be good..

No, that wouldn't case this.