[quote]Well i am sending 0x3A for login, receiving &H1 (Account does not exist) so i am sending 0x3D to create a new.

from 0x3D i am getting &H0 as response (Account created) so i am sending 0x3A for login again.

But now i don't get any response from battle.net... what could that be?

even after disconnecting and trying to connect again (with different existing account) i don't get any response for 0x3A...[/quote]

The exact same thing is happening to me. My client connects fine most of the time, but after creating a few accounts I often experience exactly what the original poster was talking about. I don't believe it is any sort of bruteforce protection that is causing it. The odd thing is when I restart my computer it will be able to connect fine (but logging on and off of windows won't do the trick). Any advice?

EDIT: Turns out I just have to flush the local DNS cache every so often

No, in the case of it being 2-3 years old..you should just make a new one.

Split from https://davnit.net/bnet/vL/index.php?topic=1790.msg13721#msg13721 .  Although I appreciate that you wanted to stay on-topic, because of the age, it'd be better to just link to the old topic.

After so many failed logon attempts, Battle.net will stop responding to your requests.

[quote]The odd thing is when I restart my computer it will be able to connect fine (but logging on and off of windows won't do the trick). Any advice?[/quote]

Your ISP is probably assigning you a new IP.

I get this too sometimes, found that switching the server you are connecting to to a dfferent IP fixes this.
Ex: if you're connecting to 63.240.202.139 switch to 63.240.202.138

Ok, thanks for the advice about trying a different IP. Do you know what causes it though? It isn't from failed logon attempts.
And no my ISP is not assigning me a new IP.

[quote author=Jman link=topic=15362.msg155518#msg155518 date=1152426169]
Ok, thanks for the advice about trying a different IP. Do you know what causes it though? It isn't from failed logon attempts.
And no my ISP is not assigning me a new IP.
[/quote]

I honestly don't know, I experience this too with SC client, sometimes it just gets stuck on "Accessing Account..." so it's the same problem for packet 0x29 as well, it has to be a server-side bug.

Ok changing IP does work. The problem I'm running into is that the bot is connecting to useast.battle.net. Windows only grabs the IP of useast.battle.net once per boot. So how do I get it so either windows looks up useast.battle.net and gets a new IP each time, or the bot knows the proper IP to connect to?

I really appreciate the help. Thanks

[quote author=Jman link=topic=15362.msg155518#msg155518 date=1152426169]
Do you know what causes it though? It isn't from failed logon attempts.
[/quote]

Yes it is.

[quote author=Lord[nK] link=topic=15362.msg155550#msg155550 date=1152497698]
[quote author=Jman link=topic=15362.msg155518#msg155518 date=1152426169]
Do you know what causes it though? It isn't from failed logon attempts.
[/quote]

Yes it is.
[/quote] I know what you are talking about, but what I'm talking about is not a result of failed logon attempts.