• Welcome to Valhalla Legends Archive.
 

BNLS - Little trouble connecting..CDKey Problem

Started by Networks, June 02, 2004, 05:21 PM

Previous topic - Next topic
Print
|
Go Down Pages 1 2
User actions

Networks

#15
June 03, 2004, 09:55 AM Last Edit: June 03, 2004, 09:58 AM by Networks
I LOVE YOU GUYS BUT I FIXED IT:

Code Select

[7:53:39 AM] BNLS: Connecting...
[7:53:40 AM] BNLS: Connected!
[7:53:40 AM] Received 0x0E
[7:53:40 AM] Received 0x0F
[7:53:40 AM] Product: PXES CDKey: <NO FREE KEY FOR JOO!>
[7:53:40 AM] Received 0x10
[7:53:41 AM] BNET: Connected!
[7:53:41 AM] BNET: Sent 0x50
[7:53:41 AM] Product: PXES CDKey: <NO FREE KEY FOR JOO!>
[7:53:41 AM] Received 0x09
[7:53:41 AM] BNLS: Sending CDKey...
[7:53:41 AM] Received 0x01
[7:53:41 AM] BNLS: Received CDKey Hash:
[7:53:41 AM] BNLS: Sent 0x51
[7:53:42 AM] 0x51 Packet Received.
[7:53:42 AM] BNET: Version and CD-key check passed!
[7:53:42 AM] 0x14 Sent.
[7:53:42 AM] 0x3A Packet Sent.
[7:53:42 AM] 0x0A Packet Sent.
[7:53:42 AM] Logon Passed.
[7:53:42 AM] Received 0x3A
[7:53:42 AM] Received 0x0A
[7:53:42 AM] Logged on as Networks
[7:53:42 AM] Joined Channel: Op []


I am thinking it was because I didn't make Servers as public and it was private in my parseBNLS and ParseBNET Modules.

But as soon as I made it public it worked perfectly =p

MyndFyre

#16
June 03, 2004, 01:31 PM
Again, why is BNLS getting 0x51?  :P
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.

Networks

#17
June 03, 2004, 02:21 PM
oops, fixed it was just addc...

hismajesty

#18
June 03, 2004, 03:14 PM
Quote from: LordNevar on June 02, 2004, 06:39 PM
Quote from: Networks on June 02, 2004, 05:21 PM

NOTE: The key is valid, I connected using it on a hashed connection.

Now what might be the problem before I send you guys any code at all?

You all need to read closely before you tell him to retry his key, he already stated that he did check to make sure it worked.

Not you all, he edited his post after I posted. :)

Networks

#19
June 03, 2004, 03:56 PM
He's right the only one that had the right to ask was the guy who posted 2nd anyhow.

I am getting any error for war3:

Code Select

[1:52:24 PM] BNLS: Connecting...
[1:52:24 PM] [BNLS] Connected.
[1:52:25 PM] [BNLS] Received 0x0E
[1:52:25 PM] [BNLS] Received 0x0F
[1:52:25 PM] Product set to: 3RAW
[1:52:26 PM] [BNLS] Received 0x10
[1:52:26 PM] [BNET] Connected.
[1:52:26 PM] [BNET] Sent 0x50
[1:52:26 PM] Product set to: 3RAW
[1:52:27 PM] [BNLS] Received 0x09
[1:52:27 PM] BNLS: Sending CDKey...
[1:52:27 PM] [BNLS] Received 0x01
[1:52:27 PM] BNLS: Received CDKey Hash
[1:52:27 PM] [BNET] Sent 0x51
[1:52:28 PM] 0x51 Packet Received.
[1:52:28 PM] BNET: Version and CD-key check passed!
[1:52:28 PM] [BNLS] Received 0x0B
[1:52:29 PM] [BNLS] Received 0x02
[1:52:29 PM] [BNLS] Received 0x0B
[1:52:29 PM] BNET: Logon failed, Incorrect password.
[1:52:29 PM] Received 0x3A
[1:52:30 PM] [BNLS] Received 0x03


Code Select

With pBuffer
                   If SPass = True Then
                       .InsertDWORD GTC
                       .InsertDWORD Servers
                       .InsertNonNTString Mid(data, 4, Len(data) - 3)
                       .InsertNTString (Config.Username)
                       .SendPacket &H3A
                       SPass = False
                       CB = 0
                   Else
                       .InsertDWORD GTC
                       .InsertNonNTString Mid(data, 4, Len(data) - 3)
                       .InsertNTString Config.Realm
                       .SendPacket &H3E
                       CB = 0
                   End If
               End With

This is where I think error is caused.



Note: the password, server, username is fine.

Eric

#20
June 03, 2004, 04:22 PM
War3 doesn't use 0x3A.

Newby

#21
June 03, 2004, 06:02 PM
Packetlog a Warcraft III connection and figure out what packet it uses to login. It's not 0x3A as Lord pointed out. :)
- Newby

Quote[17:32:45] * xar sets mode: -oooooooooo algorithm ban chris cipher newby stdio TehUser tnarongi|away vursed warz
[17:32:54] * xar sets mode: +o newby
[17:32:58] <xar> new rule
[17:33:02] <xar> me and newby rule all

Quote<TehUser> Man, I can't get Xorg to work properly.  This sucks.
<torque> you should probably kill yourself
<TehUser> I think I will.  Thanks, torque.

MyndFyre

#22
June 03, 2004, 06:31 PM
Quote from: Newby on June 03, 2004, 06:02 PM
Packetlog a Warcraft III connection and figure out what packet it uses to login. It's not 0x3A as Lord pointed out. :)

Why bother?  The BNLS protocol spec clearly identifies it as 0x53 and 0x54.  It's not a secret.  ;-)
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.
Print
|
Go Up Pages 1 2
User actions