Valhalla Legends Archive

Thanks for adding new version to site!

Quote from: MyStiCaL on August 24, 2006, 05:00 PM
I've had a week IPban, that would be saying a website in a public channel, but permantly IPban i doubt thats possible...

They are very strict on giving ip bans when you're spamming for a website. Doing things like logging in incorrectly probably won't ever earn you a perm ban but spamming can.

It's possible to get IP ban's that last for over a week. I believe they also do perm IP bans.

Yeah.. I noticed D2 is still working. Perhaps they are planning on doing some patch or resetting the ladder (as many people expect to happen soon)? It wouldn't make much sense that would be the reason but I dunno.

I don't know... but I just noticed this aswell.

edit: It seems that a legit client will download the new mpq's with the file transfer thing before it makes the check revision... it seems that it is doing this on east also though the check is not failing there.

It's possible (though unlikely imo) that you have a perm IP ban.
Battle.net accepts ips with open 1080 ports so something else is going wrong.

Okay, that makes more sense. Thanks!

Sorry if this is off topic or something but I don't know where else to post this. Anyways, I'm not entirely sure how webbot works. Does valhallalegends.com connect to b.net for the various people that use webbot? If this is the case then how is it that there are more than 8 bots connected to battle.net. I thought each realm was restricted to 8 connections per IP. Am I way off on this? Anyways thanks for reading.

Quote from: Lord[nK] on July 09, 2006, 09:14 PM

Quote from: Jman on July 09, 2006, 01:22 AM
Do you know what causes it though? It isn't from failed logon attempts.

Yes it is.

I know what you are talking about, but what I'm talking about is not a result of failed logon attempts.

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

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.

QuoteWell 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...

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