Valhalla Legends Forums Archive | Battle.net Bot Development | Help?

AuthorMessageTime
AC_Drkan
I get my Bot Connected then bnls disconnects look:
[code]
[10:10:41 PM] BNLS: Connecting...
[10:10:42 PM] BNLS: Connection Established!
[10:10:42 PM] BNLS: Authorization Complete!
[10:10:42 PM] Battle.net: Connecting...
[10:10:42 PM] Battle.net: Connection Established!
[10:10:43 PM] Version check passed.
[10:10:43 PM] CD-Key check passed.
[10:10:44 PM] BNLS: Disconnected!
[/code]
July 16, 2004, 2:11 AM
UserLoser.
[13:46:48] Error 10053 connecting to Battle.net server!

HELP PLZ
July 16, 2004, 7:56 PM
ChR0NiC
[quote author=UserLoser. link=board=17;threadid=7725;start=0#msg70825 date=1090007796]
[13:46:48] Error 10053 connecting to Battle.net server!

HELP PLZ
[/quote]

Although I'm sure Userloser is joking...
[quote]
(10053) Software caused connection abort.
[/quote]

Solution:
[quote]
A connection abort was caused internal to your host machine. The software caused a connection abort because there is no space on the socket's queue and the socket cannot receive further connections.
[/quote]

Always remember to use Google first ;D
July 16, 2004, 8:00 PM
Lenny
[quote]I get my Bot Connected then bnls disconnects look:[/quote]

Looked....

(In case you havent noticed the subtlety in these posts, more information is needed)
July 16, 2004, 8:08 PM
AC_Drkan
like what?

thats all it gives me,
Bot connects to BNLS,
connection authrized,
connects to battle.net

then after the cdkey is sent, the bot disconnects.
im using CleanSlateBot
July 19, 2004, 6:17 PM
UserLoser.
The whole point of my post above is that by pasting outputs of the status of the connection, won't get you much help. (But thanks anyways for sharing what the 10053 is) If you really want to get some help, you're going to have to paste some packet logs so people can pick through it and find what's going wrong.
July 19, 2004, 6:24 PM
Quarantine
Post some code.
July 19, 2004, 8:02 PM
K
Um, correct me if I'm wrong, but aren't you supposed to disconnect from BNLS once you've successfully logged in?
July 19, 2004, 8:06 PM
Eli_1
Yes, it automaticly disconnections some time after you've logged in. But his is not only disconnecting immediatly, but he's also not finished logging in, I don't think.

I think you need to set a breakpoint and check to make sure none of your variables are empty.
July 19, 2004, 8:13 PM
KkBlazekK
[quote author=AC_Drkan link=board=17;threadid=7725;start=0#msg70703 date=1089943871]
I get my Bot Connected then bnls disconnects look:
[code]
[10:10:41 PM] BNLS: Connecting...
[10:10:42 PM] BNLS: Connection Established!
[10:10:42 PM] BNLS: Authorization Complete!
[10:10:42 PM] Battle.net: Connecting...
[10:10:42 PM] Battle.net: Connection Established!
[10:10:43 PM] Version check passed.
[10:10:43 PM] CD-Key check passed.
[10:10:44 PM] BNLS: Disconnected!
[/code]
[/quote]

I'd check your 0x0B packet.... Looks like your getting disconnected due to a packet in the wrong format..


Edit: Typos fix
July 19, 2004, 8:46 PM
Eli_1
[quote author=Kk)Blaze(kK link=board=17;threadid=7725;start=0#msg71360 date=1090269981]
[quote author=AC_Drkan link=board=17;threadid=7725;start=0#msg70703 date=1089943871]
I get my Bot Connected then bnls disconnects look:
[code]
[10:10:41 PM] BNLS: Connecting...
[10:10:42 PM] BNLS: Connection Established!
[10:10:42 PM] BNLS: Authorization Complete!
[10:10:42 PM] Battle.net: Connecting...
[10:10:42 PM] Battle.net: Connection Established!
[10:10:43 PM] Version check passed.
[10:10:43 PM] CD-Key check passed.
[10:10:44 PM] BNLS: Disconnected!
[/code]
[/quote]

I'd check your 0x0B packet.... Looks like your getting disconnected due to a packet in the wrong format..


Edit: Typos fix
[/quote]

He's using CSB, which handles all the packets for you. I think I was able to recreate this error by leaving my Username or Password blank. You might want to check that.
July 19, 2004, 10:11 PM
AC_Drkan
Fixed it already,
i read from a database and then i misspelled the strpass causing it to not send the password
July 22, 2004, 6:21 PM
Adron
Use Option Explicit?
July 22, 2004, 7:58 PM

Search