Quick Question: CDKeys with letters in them

Don Cullen · February 21, 2007, 06:00 AM

Et tu, rabbit? my 0x1A was working when BNLS was up too. I was wondering the same thing. At first I thought it was my code, that I somehow broke it. 0.o

rabbit · February 21, 2007, 06:05 AM

Mine doesn't disconnect me, though. I can send it again and again with no trouble besides getting a failure result.

Don Cullen · February 21, 2007, 06:09 AM

...

Mind if I see a packet dump of your 0x1A? Also can I see your 0x1A code? This is mine:

Code Select

Private Sub BNLS_VERSIONCHECKEX2()  '0x1A
    With PacketBuf
        .InsertDWORD ProductID
        .InsertDWORD &H0
        .InsertDWORD Cookie
        .InsertNonNTString MPQFileTime
        .InsertNTString Ix86verfilename
        .InsertNTString ChecksumFormula
        .SendBNLSPacket sckBNLS, &H1A   'Send 0x1A packet
    End With
    RaiseEvent DebugOutput("0x1A BNLS_VERSIONCHECKEX2 packet sent.")
End Sub

Packet Dump:

0000: 32 00 1A 02 00 00 00 00 00 00 00 00 00 00 00 32  2............2
0010: 39 38 30 35 34 36 35 20 32 31 30 32 39 32 37 33  9805465 21029273
0020: 36 30 76 65 72 2D 49 58 38 36 2D 30 2E 6D 70 71  60ver-IX86-0.mpq
0030: 00 00                                            ................

Edit:

Also thought I'd mention that I got curious and pinged bnls.valhallalegends.com. It responded to the ping. So the computer (server) that was hosting BNLS is still up and running, it's the BNLS server software that isn't up. Or at least it's up but refusing connections? AFAIK, if something was unable to accept a connection, it'd time out. But instead of timing out, it's actively refusing connections. Which leads me to think that perhaps the BNLS software is indeed running, but that it's actively refusing connections.

Ringo · February 21, 2007, 06:11 AM

Quote from: [RealityRipple] on February 21, 2007, 04:56 AM
Hmm... you may want to give this temp server to people you can trust with it... to lessen the load on your own server. Maybe get a No-IP host and a splitting server, so that clients will connect to the least busy of the servers...

Might I ask why this is in this topic? Methinks this should be split....

No problems with speed/stress, mainly just dont like the idea of 95% of connections being a waste of time/space

Quote from: Kyro on February 21, 2007, 05:48 AM
Apologies, I posted the wrong packet. I'm tired. >.<

Here's the 0x1A that keeps getting me disconnected:
0000: 32 00 1A 02 00 00 00 00 00 00 00 00 00 00 00 32  2............2
0010: 39 38 30 35 34 36 35 20 32 31 30 32 39 32 37 33  9805465 21029273
0020: 36 30 76 65 72 2D 49 58 38 36 2D 30 2E 6D 70 71  60ver-IX86-0.mpq
0030: 00 00                                            ................

Ah, I see the problem, your format is bad (supprised BNLS handled it like that)
29805465 21029273 should be as 2 DWORDS, rather than a string and also your version check string is blank.

Quote from: rabbit on February 21, 2007, 05:48 AM
Ringo, I keep getting 0x1a failure out of your server, but I got a normal result out of BNLS (when it was up) using the same code. Are you using that database?

0x1A is returning false? or bnet is rejecting the results?
The errors i see atm, are:

Code Select


0x09 Failed CR lockdown-IX86-00.mpq Broodwar Hash - 5C 37 56 21 4A A6 8F 8A CE DB 67 26 34 1B DD 44
0x09 Failed CR lockdown-IX86-00.mpq Broodwar Hash - 04 1D FA 75 56 8D 0C 74 4E 12 01 B9 E0 7D 3F 6E
0x09 Failed CR lockdown-IX86-00.mpq Broodwar Hash - C1 6F BC 59 0E E7 0F 2F 69 3C BB A9 1F B5 55 FC
0x09 Failed CR lockdown-IX86-00.mpq Broodwar Hash - B9 17 C9 1D 31 E8 A9 6C CE 14 1E 08 E6 5C 0E 72
0x09 Correcting RATS lockdown-IX86-07.mpq To lockdown-IX86-17.mpq
0x09 Failed CR lockdown-IX86-00.mpq Broodwar Hash - A8 0B 48 F6 52 BB 6C 4B AA 38 B0 E1 47 2B AB 51

And ye its a databse, so theres a very small change it might have not been found

[EDIT]: Just a side note, if anyone is useing the server and is naughty, you will end up with the following:

Code Select


[14:12:43] [BNLS] Connecting..
[14:12:43] [BNLS] Connected!
[14:12:43] [BNLS] UnHandled Packet: 0xFF
41 00 FF 59 6F 75 72 20 49 50 20 49 73 20 52 65       A..Your IP Is Re
73 74 72 69 63 74 65 64 20 46 6F 72 20 41 6E 6F       stricted For Ano
74 68 65 72 20 31 31 20 4D 69 6E 73 2E 2E 20 50       ther 11 Mins.. P
6C 65 61 73 65 20 54 72 79 20 4C 61 74 65 72 2E       lease Try Later.
00                                                    .
[14:12:43] [BNLS] Disconnected.

Barabajagal · February 21, 2007, 11:29 AM

Wait, you're getting ver-ix86-0 using which client? Is the notorious ver-ix86-0 with no request string back?

Don Cullen · February 21, 2007, 11:59 AM

Quote from: [RealityRipple] on February 21, 2007, 11:29 AM
Wait, you're getting ver-ix86-0 using which client? Is the notorious ver-ix86-0 with no request string back?

Using SEXP. And I would assume so that there was no request string because my code was obtaining them without a problem previously with BNLS.

Quote from: [Ringo]Ah, I see the problem, your format is bad (supprised BNLS handled it like that)
29805465 21029273 should be as 2 DWORDS, rather than a string

I'll convert my current code to use 2 DWORDs rather than a string then. I'm just surprised that your server isn't reacting well to my using it as a string when BNLS handled it fine.

Barabajagal · February 21, 2007, 12:05 PM

If you're getting ver-ix86-0 with no request string on SEXP, then change the server you're connecting to until you don't get that request anymore. None of the BNLS servers can handle it. It's still an anomaly.

Don Cullen · February 21, 2007, 12:09 PM

Quote from: [RealityRipple] on February 21, 2007, 12:05 PM
If you're getting ver-ix86-0 with no request string on SEXP, then change the server you're connecting to until you don't get that request anymore. None of the BNLS servers can handle it. It's still an anomaly.

By 'change the server', you're referring to the Battle.net server or BNLS server?

[Edit]

I was on uswest originally. I changed bnet server to uswest, europe, asia. All four still resulted in the ver-ix86-0 with no request string.

[Edit 2]

Decided to try switching to D2DV. This time, I got a request string:

0000: 70 00 1A 04 00 00 00 00 00 00 00 00 00 00 00 32  p............2
0010: 39 38 30 35 34 36 35 20 32 31 30 32 39 32 37 33  9805465 21029273
0020: 36 30 76 65 72 2D 49 58 38 36 2D 30 2E 6D 70 71  60ver-IX86-0.mpq
0030: 00 42 3D 32 37 35 30 39 33 36 30 34 37 20 43 3D  .B=2750936047 C=
0040: 33 31 31 31 38 31 33 39 20 41 3D 33 33 30 32 33  31118139 A=33023
0050: 38 30 34 31 33 20 34 20 41 3D 41 5E 53 20 42 3D  80413 4 A=A^S B=
0060: 42 2D 43 20 43 3D 43 2D 41 20 41 3D 41 5E 42 00  B-C C=C-A A=A^B.

But this time, I'm getting a failure response like rabbit.

[edit 3]

Wait, my failure response isn't like rabbit's: his is failing at 0x1A, mine is failing at 0x01 (BNLS_CDKEY)

Quote[10:19:00 AM] Connecting to Battle.net...
[10:19:00 AM] Connected to Battle.net.
[10:19:01 AM] BNLS reported failure with 0x01 (BNLS_CDKEY). Disconnecting.
[10:19:01 AM] Disconnected.

And the debug log:

Quote[10:18:57 AM] Username set.
[10:18:57 AM] Password set.
[10:18:57 AM] GameCode set to D2DV.
[10:18:57 AM] Default Home channel set to Op xDMx.
[10:18:57 AM] UseLagPlug set.
[10:18:57 AM] BNLS server set to 84.9.75.83.
[10:18:57 AM] BNET server set to asia.battle.net.
[10:18:57 AM] CDKey set.
[10:19:00 AM] Connecting to BNLS...
[10:19:00 AM] Connected to BNLS.
[10:19:00 AM] Connecting to BNET...
[10:19:00 AM] Connected to BNET.
[10:19:00 AM] 0x01 SID_EmuByte sent.
[10:19:00 AM] 0x50 SID_AUTH_INFO packet sent.
[10:19:00 AM] Received Packet: 0x25 (SID_PING)
[10:19:00 AM] 0x25 SID_PING packet sent.
[10:19:00 AM] Received Packet: 0x50 (SID_AUTH_INFO)
[10:19:00 AM] 0x01 BNLS_CDKEY packet sent.
[10:19:01 AM] Receiving data from BNLS...
[10:19:01 AM] Received Packet: 0x1 (BNLS_CDKEY)
[10:19:01 AM] Sockets closed: BNLS_CDKEY failure.

Ringo · February 21, 2007, 12:22 PM

Quote from: Kyro on February 21, 2007, 11:59 AM
Quote from: [RealityRipple] on February 21, 2007, 11:29 AM
Wait, you're getting ver-ix86-0 using which client? Is the notorious ver-ix86-0 with no request string back?

Using SEXP. And I would assume so that there was no request string because my code was obtaining them without a problem previously with BNLS.

Quote from: [Ringo]Ah, I see the problem, your format is bad (supprised BNLS handled it like that)
29805465 21029273 should be as 2 DWORDS, rather than a string

I'll convert my current code to use 2 DWORDs rather than a string then. I'm just surprised that your server isn't reacting well to my using it as a string when BNLS handled it fine.

If your not downloading or handling any of the BnFTP files, then you dont really need to do anything with the 8 byte filetime structure other than copy it over into the 0x1A BNLS packet body.
From 0x50 to 0x1A
The problem being, is that as a string, it is no longer fixed lengh and put the filename offset out, causeing 0x1A handler to abort.
When you say BNLS handled it, did Bnet accept it originaly?
Also, any chance you can post your 0x50 parseing, where you gather the values for 0x1A?

Also what i ment about the lockdown filenumber 0, and ver-IX86 filenumber 6, is (im guessing) out of date bots that are not parseing the number from the new file names correctly.
So what I have done, is try to correct/match to the correct file number, inorder to return the correct result. (or at least better chance to)
Example:

Code Select


0x09 Correcting VD2D ver-IX86-6.mpq To ver-IX86-2.mpq
0x09 Correcting VD2D ver-IX86-6.mpq To ver-IX86-7.mpq
0x09 Correcting VD2D ver-IX86-6.mpq To ver-IX86-1.mpq
0x09 Correcting VD2D ver-IX86-6.mpq To ver-IX86-5.mpq
0x09 Correcting VD2D ver-IX86-6.mpq To ver-IX86-1.mpq
0x09 Correcting VD2D ver-IX86-6.mpq To ver-IX86-5.mpq
0x09 Correcting VD2D ver-IX86-6.mpq To ver-IX86-5.mpq
0x09 Correcting VD2D ver-IX86-6.mpq To ver-IX86-1.mpq
0x09 Correcting NB2W lockdown-IX86-00.mpq To lockdown-IX86-17.mpq
0x09 Correcting NB2W lockdown-IX86-00.mpq To lockdown-IX86-19.mpq
0x09 Correcting NB2W lockdown-IX86-00.mpq To lockdown-IX86-14.mpq
0x09 Correcting RATS lockdown-IX86-00.mpq To lockdown-IX86-13.mpq
0x09 Correcting RATS lockdown-IX86-00.mpq To lockdown-IX86-15.mpq

Also, it should handle IX86ver version checks to (0x1A only) so as long as the formula string is not empty, it should pass with no problems.

Barabajagal · February 21, 2007, 12:28 PM

ver-ix86-0.mpq with no request string is only showing up for lockdown clients on certain servers. As far as I know, changing your BNet Server IP should fix the problem. Last time I checked this (a few weeks ago, so it may be different now), 63.241.83.9 and 63.241.83.12 requested ver 0 with no request, whereas the rest of the west servers (63.241.83.13, 63.241.83.107, 63.241.83.108, 63.241.83.109, 63.241.83.110, 63.241.83.111, and 63.241.83.112) returned the normal lockdown system.

Edit: Just checked on Starcraft and I'm not getting any ver requests... You may want to double-check what you're receiving.

Ringo · February 21, 2007, 12:40 PM

Quote from: [RealityRipple] on February 21, 2007, 12:28 PM
Edit: Just checked on Starcraft and I'm not getting any ver requests... You may want to double-check what you're receiving.

I just twigged on, hes trying to add D2, so that sorta adds up

Kyro, try checking your code vs the below code, to make sure your parseing lines up for 0x50.
Im taking a wild guess, and guesing that is the cause of the problems.

Code Select


    0x50:
    m_ServerToken = GetDWORD(Mid(Data, 9, 4))
    tmpFileTime = Mid(Data, 17, 8)
    tmpFile = GetSTRING(Mid(Data, 25))
    tmpVals = GetSTRING(Mid(Data, 26 + Len(tmpFile)))
    
    BNLS 0x1A:
    With Buf
        .InsertDWORD m_ClientIndex '1, 2, 3, 4, 5, 6, 7, 8
        .InsertDWORD 0 'Flags (unused)
        .InsertDWORD 1 'cookie
        .InsertSTRING tmpFileTime
        .InsertNTSTRING tmpFile
        .InsertNTSTRING tmpVals
        .InsertHEADER &H1A, BNRS_HEADER
        .SendPacket sckTCP.SocketHandle
    End With
    
    BNLS 0x01:
    With Buf
        .InsertDWORD m_ServerToken
        .InsertNTSTRING "YOURCDKEYHERE"
        .InsertHEADER &H1, BNRS_HEADER
        .SendPacket sckTCP.SocketHandle
    End With

Don Cullen · February 21, 2007, 12:44 PM

Quote from: Ringo on February 21, 2007, 12:22 PM
When you say BNLS handled it, did Bnet accept it originaly?

Yes.

Quote from: Ringo on February 21, 2007, 12:22 PMAlso, any chance you can post your 0x50 parseing, where you gather the values for 0x1A?

I'll do better than that. Here:

[10:37:23 AM] Username set.
[10:37:23 AM] Password set.
[10:37:23 AM] GameCode set to SEXP.
[10:37:23 AM] CDKey set.
[10:37:23 AM] Default Home channel set to Op xDMx.
[10:37:23 AM] UseLagPlug set.
[10:37:23 AM] BNLS server set to 84.9.75.83.
[10:37:23 AM] BNET server set to 63.241.83.13.
[10:37:24 AM] Connecting to BNLS...
[10:37:25 AM] Connected to BNLS.
[10:37:25 AM] Connecting to BNET...
[10:37:25 AM] Connected to BNET.
[10:37:25 AM] 0x01 SID_EmuByte sent.
[10:37:25 AM] 0x50 SID_AUTH_INFO packet sent.
[10:37:25 AM] Received Packet: 0x25 (SID_PING)
[10:37:25 AM] 0x25 SID_PING packet sent.
[10:37:25 AM] Received Packet: 0x50 (SID_AUTH_INFO)
[10:37:25 AM] 0x01 BNLS_CDKEY packet sent.
[10:37:25 AM] Dumping sent packet...
(removed since it exposes cdkey)
[10:37:25 AM] End of packet dump.
[10:37:25 AM] Receiving data from BNLS...
[10:37:25 AM] Dumping received packet...
[10:37:25 AM] Dumping packet...
[10:37:25 AM] 
0000: 2F 00 01 01 00 00 00 63 E2 EC 71 0D 00 00 00 01  /....câìq....
0010: 00 00 00 36 F7 66 00 00 00 00 00 70 66 66 85 7C  ...6÷f.....pff...|
0020: D5 C8 9B 78 51 18 73 23 9D 10 E8 C0 87 AC B3     ÕÈ›xQs#?èÀ‡¬³.
[10:37:25 AM] End of packet dump.
[10:37:25 AM] Received Packet: 0x1 (BNLS_CDKEY)
[10:37:25 AM] 0x1A BNLS_VERSIONCHECKEX2 packet sent.
[10:37:25 AM] Dumping sent packet...
[10:37:25 AM] Dumping packet...
[10:37:25 AM] 
0000: 32 00 01 02 00 00 00 00 00 00 00 00 00 00 00 32  2............2
0010: 39 38 30 35 34 36 35 20 32 31 30 32 39 32 37 33  9805465 21029273
0020: 36 30 76 65 72 2D 49 58 38 36 2D 30 2E 6D 70 71  60ver-IX86-0.mpq
0030: 00 00                                            ................
[10:37:25 AM] End of packet dump.
[10:37:25 AM] BNLS Disconnected.
[10:37:38 AM] Sockets closed.

This is my 0x50 parsing code:

Code Select

        Case cSID_AUTH_INFO&   '0x50
            LogonType = PktDeBuf.rDWORD
            ServerToken = PktDeBuf.rDWORD   'AKA Session Key
            UDPValue = PktDeBuf.rDWORD
            MPQFileTime = PktDeBuf.rFILETIME(True)
            Ix86verfilename = PktDeBuf.rNTString
            ChecksumFormula = PktDeBuf.rNTString
            Call BNLS_CDKEY(ServerToken)

Then after receiving BNLS_CDKEY, here's the parsing section for that:

Code Select

        Case &H1    'BNLS_CDKEY
            Results = CBool(PktDeBuf.rDWORD)
            If Results = False Then
                RaiseEvent sError("BNLS reported failure with 0x01 (BNLS_CDKEY). Disconnecting.")
                Disconnect
                Exit Sub
            End If
            ClientToken = PktDeBuf.rDWORD
            KeyLength = PktDeBuf.rDWORD
            CDKeyProdValue = PktDeBuf.rDWORD
            CDKeyPubValue = PktDeBuf.rDWORD
            Unknown = PktDeBuf.rDWORD
            HashedKeyData(0) = PktDeBuf.rDWORD
            HashedKeyData(1) = PktDeBuf.rDWORD
            HashedKeyData(2) = PktDeBuf.rDWORD
            HashedKeyData(3) = PktDeBuf.rDWORD
            HashedKeyData(4) = PktDeBuf.rDWORD
            Call BNLS_VERSIONCHECKEX2

This is the BNLS_VERSIONCHECKEX2 sub:

Code Select

Private Sub BNLS_VERSIONCHECKEX2()  '0x1A
    Dim tmp As String
    With PacketBuf
        .InsertDWORD ProductID
        .InsertDWORD &H0
        .InsertDWORD Cookie
        .InsertNonNTString MPQFileTime
        .InsertNTString Ix86verfilename
        .InsertNTString ChecksumFormula
        tmp = .RetBNLSPkt(&H1)
        .SendBNLSPacket sckBNLS, &H1A   'Send 0x1A packet
    End With
    RaiseEvent DebugOutput("0x1A BNLS_VERSIONCHECKEX2 packet sent.")
    RaiseEvent DebugOutput("Dumping sent packet...")
    DumpPacket (tmp)
    RaiseEvent DebugOutput("End of packet dump.")
End Sub

Ringo, I only switched to D2DV because SEXP wasn't working. D2DV got a BNLS_CDKEY failure so I just switched back to SEXP.

RealityRipple, 63.241.83.13, 63.241.83.107, 108, 109, 110, 111, 112 all return ver-ix86-0 with no request string.

Ringo · February 21, 2007, 12:52 PM

Quote from: Kyro on February 21, 2007, 12:44 PM
This is my 0x50 parsing code:
Code Select Expand
Case cSID_AUTH_INFO& '0x50 LogonType = PktDeBuf.rDWORD ServerToken = PktDeBuf.rDWORD 'AKA Session Key UDPValue = PktDeBuf.rDWORD MPQFileTime = PktDeBuf.rFILETIME(True) Ix86verfilename = PktDeBuf.rNTString ChecksumFormula = PktDeBuf.rNTString Call BNLS_CDKEY(ServerToken)

Then after receiving BNLS_CDKEY, here's the parsing section for that:

Code Select Expand
Case &H1 'BNLS_CDKEY Results = CBool(PktDeBuf.rDWORD) If Results = False Then RaiseEvent sError("BNLS reported failure with 0x01 (BNLS_CDKEY). Disconnecting.") Disconnect Exit Sub End If ClientToken = PktDeBuf.rDWORD KeyLength = PktDeBuf.rDWORD CDKeyProdValue = PktDeBuf.rDWORD CDKeyPubValue = PktDeBuf.rDWORD Unknown = PktDeBuf.rDWORD HashedKeyData(0) = PktDeBuf.rDWORD HashedKeyData(1) = PktDeBuf.rDWORD HashedKeyData(2) = PktDeBuf.rDWORD HashedKeyData(3) = PktDeBuf.rDWORD HashedKeyData(4) = PktDeBuf.rDWORD Call BNLS_VERSIONCHECKEX2

This is the BNLS_VERSIONCHECKEX2 sub:

Code Select Expand
Private Sub BNLS_VERSIONCHECKEX2() '0x1A Dim tmp As String With PacketBuf .InsertDWORD ProductID .InsertDWORD &H0 .InsertDWORD Cookie .InsertNonNTString MPQFileTime .InsertNTString Ix86verfilename .InsertNTString ChecksumFormula tmp = .RetBNLSPkt(&H1) .SendBNLSPacket sckBNLS, &H1A 'Send 0x1A packet End With RaiseEvent DebugOutput("0x1A BNLS_VERSIONCHECKEX2 packet sent.") RaiseEvent DebugOutput("Dumping sent packet...") DumpPacket (tmp) RaiseEvent DebugOutput("End of packet dump.") End Sub

From what I can see by the responces, its all good apart from the filetime.

Code Select


    MPQFileTime = PktDeBuf.rFILETIME(True)

Code Select


        .InsertNonNTString MPQFileTime

rFILETIME() just needs to return a fixed lengh 8 byte string, then 0x1A should aline.

Also, one other thing, what version byte are you useing in 0x50? 0xCF for sc/bw and 0x0B for d2/d2lod?

Don Cullen · February 21, 2007, 01:05 PM

WTH? I just checked the verbyte (it obtains verbyte by itself automatically), and it was 0. Bah, must be an error in the verbyte code somewhere. In any case I put it back to CF. Let's see if it works...

Hmm, this is where the whole mess started. No wonder why it was set to 0. Check this out:

Main window:

Quote[10:57:59 AM] Connecting to Battle.net...
[10:57:59 AM] Connected to Battle.net.
[10:58:00 AM] BNLS reported failure with 0x1A (BNLS_VERSIONCHECKEX2). Disconnecting.
[10:58:00 AM] Disconnected.
[10:58:00 AM] VerByte has been updated with new VerByte. Please reconnect.
[10:58:00 AM] Disconnected.

This is the debug log:

Quote

[10:57:57 AM] Username set.
[10:57:57 AM] Password set.
[10:57:57 AM] GameCode set to SEXP.
[10:57:57 AM] CDKey set.
[10:57:57 AM] Default Home channel set to Op xDMx.
[10:57:57 AM] UseLagPlug set.
[10:57:57 AM] BNLS server set to 84.9.75.83.
[10:57:57 AM] BNET server set to 63.241.83.112.
[10:57:59 AM] Connecting to BNLS...
[10:57:59 AM] Connected to BNLS.
[10:57:59 AM] Connecting to BNET...
[10:57:59 AM] Connected to BNET.
[10:57:59 AM] 0x01 SID_EmuByte sent.
[10:57:59 AM] 0x50 SID_AUTH_INFO packet sent.
[10:57:59 AM] Received Packet: 0x25 (SID_PING)
[10:57:59 AM] 0x25 SID_PING packet sent.
[10:57:59 AM] Received Packet: 0x50 (SID_AUTH_INFO)
[10:57:59 AM] 0x01 BNLS_CDKEY packet sent.
[10:57:59 AM] Dumping sent packet...
[10:57:59 AM] Dumping packet...
[10:57:59 AM] 
(removed dump due to cdkey)
[10:57:59 AM] End of packet dump.
[10:58:00 AM] Receiving data from BNLS...
[10:58:00 AM] Dumping received packet...
[10:58:00 AM] Dumping packet...
[10:58:00 AM] 
0000: 2F 00 01 01 00 00 00 A1 B9 FF 71 0D 00 00 00 01  /....¡¹ÿq....
0010: 00 00 00 36 F7 66 00 00 00 00 00 E5 28 B9 5D 12  ...6÷f.....å(¹]
0020: 98 19 CC 5E C0 FD F6 D7 28 97 4D 48 01 D2 FA     ˜Ì^Àýö×(—MHÒú.
[10:58:00 AM] End of packet dump.
[10:58:00 AM] Received Packet: 0x1 (BNLS_CDKEY)
[10:58:00 AM] 0x1A BNLS_VERSIONCHECKEX2 packet sent.
[10:58:00 AM] Dumping sent packet...
[10:58:00 AM] Dumping packet...
[10:58:00 AM] 
0000: 48 00 01 02 00 00 00 00 00 00 00 00 00 00 00 32  H............2
0010: 39 38 31 37 39 37 30 20 2D 36 33 38 30 37 36 34  9817970 -6380764
0020: 31 36 6C 6F 63 6B 64 6F 77 6E 2D 49 58 38 36 2D  16lockdown-IX86-
0030: 31 33 2E 6D 70 71 00 24 EF 45 31 02 95 71 3B 9A  13.mpq.$ïE1•q;š
0040: 14 DF B0 93 7B 72 44 00                          ß°"{rD.........
[10:58:00 AM] End of packet dump.
[10:58:00 AM] Receiving data from BNLS...
[10:58:00 AM] Dumping received packet...
[10:58:00 AM] Dumping packet...
[10:58:00 AM] 
0000: 0B 00 1A 00 00 00 00 00 00 00 00                 ..............
[10:58:00 AM] End of packet dump.
[10:58:00 AM] Received Packet: 0x1A (BNLS_VERSIONCHECKEX2)
[10:58:00 AM] Sockets closed.
[10:58:00 AM] VerByte set.

Jeez. What a mess... No wonder why. I forgot to add 'Exit Sub' right after it fails. So it was trying to parse the rest of the packet.

Okay, now this time instead of getting disconnected, 0x1A (like rabbit) is returning failure.

Barabajagal · February 21, 2007, 01:06 PM

I just tried connecting to all the west servers, and got the following requests:

Code Select

Server Request: lockdown-IX86-15.mpq -  86 EF 2D EC 11 06 0C CE 11 A4 E8 D4 75 1B 1B 47
Server Request: lockdown-IX86-03.mpq -  DD 47 36 80 82 03 48 AF 9E 50 39 44 34 72 AB 92
Server Request: lockdown-IX86-19.mpq -  46 4F BC 12 E2 F5 19 A4 3C 2B 56 86 90 53 32 1C
Server Request: lockdown-IX86-02.mpq -  7F F6 0A D6 1A DC 5A F5 F9 C8 47 34 17 0F 2D 04
Server Request: lockdown-IX86-12.mpq -  A4 B3 70 7C C9 70 D8 81 B4 F3 B2 54 58 48 39 63
Server Request: lockdown-IX86-18.mpq -  A2 FE AB 7B 03 66 29 A8 27 39 64 EF F2 C5 8D B8
Server Request: lockdown-IX86-09.mpq -  33 11 19 7C A3 FE F9 1B 38 DE 84 99 DF 11 1B BC
Server Request: lockdown-IX86-11.mpq -  98 28 1C 75 08 CC 22 FE E2 D6 4C 90 9B 5F 0F 78
Server Request: lockdown-IX86-10.mpq -  69 13 AE 6D 84 24 19 C7 A8 57 10 E9 C8 E3 1F C4

You may want to use WPE or a similar packet logger to check that you're actually receiving ver-ix86-0.mpq from BNCS.

Edit: Nvm, Looks like you're getting the right requests now.

Quick Question: CDKeys with letters in them

Barabajagal

Barabajagal

Barabajagal

Barabajagal