WAR3 works on USWest, but not USEast ?

[tA-Kane]

I'm having some very weird trouble...

My bot is able to connect just fine to WAR3 on USWest, but when it tries connecting to WAR3 on USEast, it gets disconnected (and last night, I was IP banned for an hour, after a number of tries).

What's even more weird, is that an older version of my client is able to connect to the USEast gateway.

I've tried different accounts, and all of them disconnect me.

I'd think it was something I'd done to the new version, but it's able to connect to USWest...

I packetlogged the connections, and they're pretty much identical. The differences between the one that works and the one that doesn't is that one's connecting to .126, while the other is connecting to .127, and then the one that works work is not sending SID_PING replies, whereas the one that doesn't work is.

But that shouldn't matter, should it? I later (after packetlogging) set up my older client to not send ping replies, and to use the other server, and it's still able to connect.


Here's the packetlog for the connection that works:
http://linkware.clan-mac.com/kanebot/misc/private/works.txt

And here's the packetlog for the connection that doesn't work:
http://linkware.clan-mac.com/kanebot/misc/private/doesntwork.txt

Perhaps someone here could point me in a new direction?

[CrAz3D]

I've encountered same problem.  Doesn't work on WAR3 but it works on SEXP, such strangeness.

[MyndFyre]

I am happy to report that I was able to log onto US East with Warcraft III: The Reign of Chaos via my bot.

[tA-Kane]

I know it's (very likely) the 0x0A because I've done some more testing after I had created that thread, and Battle.net does not disconnect me until I send my 0x0A.

Also, the problem has now appeared on my older clients, and on STAR.

I suspect that it's not a problem with my code, because it's happening for both of us, and for my older client which was previously able to connect perfectly to Battle.net.

Instead, I think it's a server problem, because Battle.net even disconnected its own game client... though not at 0x0A, but after joining the default channel (in my case, it was War2BNE USA-1), and downloading the userlist.

Also, it's worth noting that I've had this problem before (about a year ago), but it disappeared without any code changes on my part... and obviously, it's now back again.

[ChR0NiC]

Maybe you did not register an email with the account on East but you did with the account on West. Or it is trying to get you to decide whether you are going to register or cancel?

Just a suggestion that I thought of when testing my bot for the same problem..

Edit: Actually I was able to successfully log on to East and West

[tA-Kane]

Maybe you did not register an email with the account on East but you did with the account on West.

No, my bot automatically sends the email packets when requested by Battle.net

Both my USWest and my USEast accounts have previously had their emails set before this.

[o.OV]

But according to your packet log.. you were successfullly logged in after sending 0x0A.

Code Select Expand


Send data (6 bytes).
<00000100< FF 0A 06 00  00 00                                  
......

Send data (8 bytes).
<00000106< FF 0B 08 00  57 41 52 33                            
....WAR3

Receive data (29 bytes).
>000006D5> FF 0A 1D 00  74 41 2D 4B  61 6E 65 23  32 00 33 52  
....tA-Kane#2.3R
>000006E5> 41 57 20 30  00 74 41 2D  4B 61 6E 65  00          
AW 0.tA-Kane.

Receive orderly release indication (T_ORDREL_IND = 132).

Send orderly release request (T_ORDREL_REQ = 109).

Send unbind request (T_UNBIND_REQ = 110).


[ChR0NiC]

yeah it seems like you are just not sending 0xC......
I don't understand why you would be IP Banned once successfully logged on.

[BaDDBLooD]

YOu can be ipbanned if you send Flag: 0x02 for 0x0C

try editing that

EDIT: i forget the reason though..

[o.OV]

YOu can be ipbanned if you send Flag: 0x02 for 0x0C

try editing that

EDIT: i forget the reason though..

I use flag 0x02 all the time. if the channel is restricted or I just can't get in then it sends me to the void.

[tA-Kane]

yeah it seems like you are just not sending 0xC......

I don't have a chance  to send 0x0C... I get disconnected almost immediately after sending 0x0A (I say almost because I'm usually able to send 0x0B before receiving the orderly disconnect... but once, it was received before my bot had finished sending 0x0B, so the packetlog ended up displaying "Received orderly disconnected request, sent 0x0B packet, sent orderly disconnect acknowledgement".).

I don't understand why you would be IP Banned once successfully logged on.

Me neither.

I've noticed that the accounts which are mutual friends receive "Your friend tA-Kane has entered Battle.net.", immediately followed by "Your friend tA-Kane has exited Battle.net." But that's more annoying than anything else. If Battle.net is going to immediately disconnect me after logging in, it shouldn't annoy friends with "friend x has logged in, logged out"  

Edit: fixed some quoting tags

[Eric]

I've had this happen quite a few times. I think it's some form of a lower level IP ban, but I don't know for sure, nor do I know what causes it.

[Skywing]

Note that there are certain protocol violations which cause the server to wait until you have completed logging on to disconnect you.

[UserLoser.]

This happened to me one day on Warcraft II, I posted back a while ago on these forums and I believe the response I got was that I was reconnecting too much on the same name & CD-key, but I don't know how true that is

[o.OV]

This happened to me one day on Warcraft II, I posted back a while ago on these forums and I believe the response I got was that I was reconnecting too much on the same name & CD-key, but I don't know how true that is

Reconnecting too many times on the same cdkey does get a person ipbanned.
It ipbans as soon as the key hash is sent
and bnet's response is that the key is invalid.
I'm sure it isn't the same situation that ta-kane has.