BNLS - Little trouble connecting..CDKey Problem

Networks · June 02, 2004, 05:21 PM

[3:14:17 PM] BNLS: Connecting...
[3:14:18 PM] BNLS: Connected!
[3:14:18 PM] Received 0x0E
[3:14:18 PM] Received 0x0F
[3:14:18 PM] Product: PXES CDKey: *************
[3:14:18 PM] Received 0x10
[3:14:19 PM] BNET: Connected!
[3:14:19 PM] BNLS: Sent 0x50
[3:14:19 PM] Product: PXES CDKey: *************
[3:14:19 PM] Received 0x09
[3:14:20 PM] Received 0x01
[3:14:20 PM] BNLS: Sent 0x51
[3:14:20 PM] 0x51 Packet Received.
[3:14:20 PM] BNET: Invalid CD-key!

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?

hismajesty · June 02, 2004, 05:26 PM

Possibly an invalid cdkey.

CrAz3D · June 02, 2004, 05:26 PM

It'd probably be easier to post the code now, it's most likely gonna be needed.

Idea: try a different server?

Networks · June 02, 2004, 05:31 PM

Does this help?

Code Select


    Case &H9
    AddC Form1.RTB1, True, vbGreen, "Received 0x09"
        version = Val("&H" & StrToHex(StrReverse(Mid(data, 8, 4))))
        version = CLng(version)
        CheckSum = Val("&H" & StrToHex(StrReverse(Mid(data, 12, 4))))
        CheckSum = CLng(CheckSum)
        ExeInfo = Mid(data, 16, Len(data) - 16)
          If varProduct = "PX2D" Then
            With pBuffer
                .InsertDWORD &H0
                .InsertBYTE &H2
                .InsertDWORD &H1
                .InsertDWORD Servers
                .InsertNTString (varCDKey)
                .InsertNTString (D2XPKey)
                .SendBNLSPacket &HC
            End With
          Else
            With pBuffer
               .InsertDWORD Servers
               .InsertNTString (varCDKey)
               .SendBNLSPacket &H1
            End With
          End If

Code Select


Public Sub Send0x51()
AddC Form1.RTB1, True, vbYellow, "BNLS: Sent 0x51"
    With pBuffer
        .InsertDWORD GTC
        .InsertDWORD version
        .InsertDWORD CheckSum
        If varProduct = "PX2D" Then
            .InsertDWORD &H2
        Else
            .InsertDWORD &H1
        End If
        .InsertDWORD &H0
        .InsertNonNTString CdkeyHash
        If varProduct = "PX2D" Then
            .InsertNonNTString Cdkey2Hash
        End If
        .InsertNTString ExeInfo
        .InsertNTString (varUser)
        .SendPacket &H51
    End With
End Sub

Lobo · June 02, 2004, 05:41 PM

You might want to post your SID_AUTH_CHECK(0x51) code too.

Networks · June 02, 2004, 05:47 PM

I'd like to know what could cause the problem besides the key actually being invalid. Could my product be wrong, BNLS Version Byte, etc.

DeTaiLs · June 02, 2004, 06:04 PM

this may be a crazy idea but how about u check the key on another bot and see if it works

LordNevar · 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.

DeTaiLs · June 02, 2004, 06:46 PM

Quote from: hismajesty[yL] on June 02, 2004, 05:26 PM
Possibly an invalid cdkey.

sorry i dident see that and then i seen that post and taught he dident check it

MyndFyre · June 02, 2004, 07:04 PM

Quote from: Twix on June 02, 2004, 06:46 PM
Quote from: hismajesty[yL] on June 02, 2004, 05:26 PM
Possibly an invalid cdkey.

sorry i dident see that and then i seen that post and taught he dident check it

i dident tink to reed teh post.

First of all, why does your Send0x51 function add to the display, "BNLS -- 0x51 Sent"? You're sending it to Bnet, right?

Also, what is the value of the GTC variable just before you send 0x51? It seems like it should be the Client Session Key provided by BNLS_CDKEY or BNLS_CDKEYEX, and why you would name it GTC is beyond me, unless you're either copying code or just have bizarre naming conventions.

The Client Session Key is provided as the second DWORD of BNLS_CDKEY (0x01) or as the first DWORD of repeating data for each key in BNLS_CDKEYEX (0x0c) (note that there is non-repeating data, a DWORD, a BYTE, a BYTE, and a DWORD before the repeating data begins).

LordNevar · June 02, 2004, 07:12 PM

I would have to agree with Myndfyre.

Eli_1 · June 02, 2004, 07:19 PM

Quote from: Myndfyre on June 02, 2004, 07:04 PM
Also, what is the value of the GTC variable just before you send 0x51?

Maybe the value returned by GetTickCount(). Can't the client key's value be whatever you want it to?

[edit] I'm probably wrong.

MyndFyre · June 02, 2004, 10:20 PM

Quote from: Eli_1 on June 02, 2004, 07:19 PM
Quote from: Myndfyre on June 02, 2004, 07:04 PM
Also, what is the value of the GTC variable just before you send 0x51?

Maybe the value returned by GetTickCount(). Can't the client key's value be whatever you want it to?

No. The client key is part of the hashing part, and when the CD key is encrypted, you need to use the client key.

BaDDBLooD · June 02, 2004, 10:45 PM

Get Token Client?

Eli_1 · June 02, 2004, 11:15 PM

Did I have client key confused with client token?