WAR3 works on USWest, but not USEast ?

[Soul Taker]

A long time ago, I used to occasionally do something wrong with login stuff, and it would wait until I had logged in and joined a channel, and the instant I sent a chat command, would disconnect me.  Incredibly frustrating!

I wonder if I didn't suggest that at some time.

It's a good idea because it makes it harder to figure out what you did wrong... but a bad idea because it really got annoying  

[tA-Kane]

My hard drive crashed, so I've been unable to access the net for a while, and I'm on my dad's laptop for now.

http://linkware.clan-mac.com/kanebot/misc/private/war3-3-20-03.txt
http://linkware.clan-mac.com/kanebot/misc/private/w3xp-3-29-04.txt

Looks like there's no null terminator on your country abbreviation.  Dunno if that's the problem of course.
Edit: and it's being sent as a DWORD?

I had noticed that the WAR3 and W3XP packet logs are sending the country codes as DWORDS, so I figured I should do the same. It didn't fix the problem though.

Actually, it would read the country code as ASUU then, and the country as "nited States".  Perhaps that's why it doesn't ban you when you try to join the channel and it notices that you sent an invalid country?

Actually, if it was reading the country code as a string, it would read it in as an empty string (since as a DWORD, there's a NULL byte preceeding 'ASU'), and then the country name would then be "ASUUnited States". But, I do not beleive the country code is sent as a string, at least not in WAR3 or W3XP.

Perhaps someone could send me a packetlog (two or three would be better, for comparison reasons) of their WarCraft 3 game's connection?

[MyndFyre]

My hard drive crashed, so I've been unable to access the net for a while, and I'm on my dad's laptop for now.
Perhaps someone could send me a packetlog (two or three would be better, for comparison reasons) of their WarCraft 3 game's connection?

Straight out of an Ethereal packet capture of Warcraft III: The Frozen Throne (NOT my bot) -- the BNCS packet starts at 0x37 (the rest is protocol information):

Code Select Expand


0000 00 0c 41 89 cc 76 02 a0 cc 67 d5 59 08 00 45 00 ..A..v...g.Y..E.
0010 00 62 77 c9 40 00 80 06 b6 4c c0 a8 01 69 3f f0 [email protected]?.
0020 ca 7e 07 48 17 e0 70 43 52 b8 bd a9 3c 78 50 18 .~.H..pCR...<xP.
0030 44 70 f8 4e 00 00 ff 50 3a 00 00 00 00 00 36 38 Dp.N...P:.....68
0040 58 49 50 58 33 57 0e 00 00 00 53 55 6e 65 c0 a8 XIPX3W....SUne..
0050 01 69 a4 01 00 00 09 04 00 00 09 04 00 00 55 53 .i............US
0060 41 00 55 6e 69 74 65 64 20 53 74 61 74 65 73 00 A.United States.


Looks like it's a null-terminated string, not a DWORD, to me.

[observation] Perhaps this is a flaw in the Mac version of WC3? [/observation]

[edit=5]Come to think of it, BnetDocs specifies it as a String:

Packet ID: 0x50
Direction: Client -> Server (Sent)
Format:
(DWORD)       Protocol ID (0)
(DWORD)       Platform ID
(DWORD)       Program ID
(DWORD)       Version Byte
(DWORD)       Product language
(DWORD)       Local IP for NAT compatibility*
(DWORD)       Time zone bias*
(DWORD)       Locale ID*
(DWORD)       Language ID*
(STRING)       Country abreviation
(STRING)       Country

[/edit]

[tA-Kane]

Looks like it's a null-terminated string, not a DWORD, to me.

It looks like it, just like IX86 and STAR used to look like non-null-terminated strings... Maybe it is indeed a string for IX86, or maybe it's actually a DWORD, but one of the platforms got the endian incorrect?

Perhaps this is a flaw in the Mac version of WC3?

Perhaps it is.

Come to think of it, BnetDocs specifies it as a String

If it's indeed a DWORD, it wouldn't be the first time BnetDocs is wrong, I think. BnetDocs, after all, is based on what information users give it, and not on official information from Blizzard, so it would be easy to get information wrong.

Also, it would make sense for the country abbreviation to be a DWORD, since that would make the offset to the country name ("United States") an exact position, instead of needing to get the (assumably possibly arbitrary) length of the country abbreviation to be able to get the country name.


Anyways, I "corrected" the country abbreviation, but I'm still getting disconnected at logon, so I assume the problem is not in my 0x50 packet... does anyone see any problems (even subtle ones) that I do not?

Half an hour ago: http://linkware.clan-mac.com/kanebot/misc/private/mbb-war3-4-10.txt

[K]

I think you can pretty much assume the country abbreviation will be three letters, since it appears to be the country's ISO ALPHA-3 code.

[tA-Kane]

So is no one able to figure it out? Because I'm stumped.

[MyndFyre]

So is no one able to figure it out? Because I'm stumped.

I've gotten randomly disconnected from Bnet while on Warcraft III several times, but it seems to be random server maintenance, because my three connections (WC3, Diablo II, and Starcraft, all on different clients), all disconnect at about the same time.