RDP client connecting to 2k3 TS error, license protocol

[ewiley]

Hi,

I'm setting up a 2k3 TS in application mode and trying to get a few Windows XP and 2000 clients to connect. I've installed the new RDP 5.1 client on my 2000 clients, and one or two give me a problem when I try to connect. The client sits at Connecting, then times out with the error "network problems are preventing the license protocol from connecting". The TS does not generate any event log errors, like errors issuing licenses (I have the license service installed on the 2k3 TS).

Anyone have any ideas?

Thanks!

 

[mlichstein]

Is "network problems are preventing the license protocol from connecting" the exact error you get on the clients?

 

[ewiley]

Oops, the exact error is:

"Remote session was disconnected because there were network problems during the licensing protocol. Please try connecting to the remote computer again."

This comes up on only 2 of my Win2kSP4 clients with the new RDP client installed. I tried re-installing the RDP client and checking the HKLM/software/microsoft/mslicensing key (it didnt' exist--it doesn't get created until the client successfully gets a token, i guess).

Thanks!

 

[ewiley]

Here's some more information:

I did a packet capture on the terminal server, and I can see the one packet that seems to be transmitting the license information from the TS to the client. The checksum on the packet is wrong, according to network monitor.

TCP: Checksum = ERROR: CheckSum is 0x1EA0, Should be 0xFE69

Sourceport is 3389 (from the terminal server)

Some of the payload from that packet (the name of my terminal server is TS1):

...U.....T.S.10-
..U...&.S.i.t.e.
..L.i.c.e.n.s.e.
..S.e.r.v.e.r0\0

<later, same packet>

.0......8.T.S.1.
..6.9.7.1.3.-.6.
4.0.-.3.7.9.3.2.
7.4.-.4.5.2.7.3.
..S.i.t.e...L.i.
c.e.n.s.e...S.e.
r.v.e.r.....0...

That looks like a UID to me...

Any ideas?

Thanks!

 

[ewiley]

Whoops, the bad checksum is a red herring, appears to happen when you capture traffic directly from a server participating in the conversation. I captured the traffic from another host and the checksums come out fine.

Still working :-/

 

[mlichstein]

First, check if there is an IPC$ share on the terminal server licensing server. Type 'net share' at the command prompt.

If it is missing, do a 'net share IPC$' to re-add it. But this will probably only be a temporary fix, because a missing IPC$ share typically means virus.

If the share is already there, you may have a corrupted TS license server. Can you open the TS licensing MMC on the license server? Does it show the server, or do you get an error?

 

[ewiley]

The IPC share is there, and i can view the terminal server licenses.. turns out it's a permissions issue:

Actually, I fixed the problem by accident. The HKLM/software/microsoft/MSLicensing key had the wrong permissions, so when a normal user was logging into terminal services for the first time, they couldn't modify the key to insert the token issued from the licensing server.

I found this out by logging into the computer as an admin and connecting to the TS. Worked fine. Looked at the MSLicensing key, and there was now a license key. *sigh*.

Thanks for the help, though!