Terminal Services connection error

[Homerboy]

She used to be able to connect no problem. Upon trying to connect last night via her XP Home home PC, she got the following error msg:

Error in licensing protocol --

error message in trying to connect viaremote desktop

Server is Win2k Server. Other people (including myself) are having no issues.
Any suggestions?

 

[RebateMonger]

If she first logged onto the TS 90 days ago, then she didn't have a valid Terminal Server Client Access license, and the temporary, 90-day, license has expired.

Have you looked at the Event Logs in the Terminal Server for more information?

 

[Homerboy]

"The terminal server cannot issue a client license. "

You're likely spot on with your diagnoses.
Whats the fix

 

[Homerboy]

anyone?

 

[dawks]

Buy Terminal Services licenses from Microsoft and install them on your Server. You can get per seat or per user. Which you choose depends on your type of usage.

Like RebateMonger said, you are given a 90 day grace period from when that remote machine first logged on. After the 90 days, you're locked out unless you obtain operating licenses.

 

[Homerboy]

I guess Im a little lost here (inhertited this server) as Im not overly familiar with Terinal Server itself.

I'm looking at the licenses on the server and I have 8 under "Existing Windows 2000 License" and 2 under "Temporary Licenses" These 2 seem to be from this 1 user, with the latest expired on March 6th. The previous is from a previous incarnation of her home PC (if I recall she had to do a system restore on her Dell shortly after getting it).

About 6 other people log in via TS including myself and have never had this issue. Is it because we all use XP Pro and/or Win2k? Or is it just because she was the last to connect out of the bunch and has pushed us over or licensed limit? Out of those 8 listed in the Win2K licenses window some are inactive and some are duplicates... can I remove them?

 

[Tsaico]

If other peopel are logging in just fine, and this particular user has problems then it might be something else. Does she always have a problem now? I would also look to see how many people are logged in via TS. If you hav emore than your licensed number, it will not let you start another session.

We had a similar situation when people were "X"ing out of their sessions, leaving them open, then when we ran out of connections, people were unable to log in anymore.

 

[dawks]

Originally posted by: Homerboy
I guess Im a little lost here (inhertited this server) as Im not overly familiar with Terinal Server itself.

I'm looking at the licenses on the server and I have 8 under "Existing Windows 2000 License" and 2 under "Temporary Licenses" These 2 seem to be from this 1 user, with the latest expired on March 6th. The previous is from a previous incarnation of her home PC (if I recall she had to do a system restore on her Dell shortly after getting it).

About 6 other people log in via TS including myself and have never had this issue. Is it because we all use XP Pro and/or Win2k? Or is it just because she was the last to connect out of the bunch and has pushed us over or licensed limit? Out of those 8 listed in the Win2K licenses window some are inactive and some are duplicates... can I remove them?

Sounds like they may be per seat licenses, meaning they are restricted to the first computers that log in (I think). So she might have tried logging on after 8 other systems had at some point and she was given one of those temp license, and is now over the 90 day period. Try deleting some of those older unused systems to clear up some logons (If you can).

 

[stash]

Sounds like they may be per seat licenses, meaning they are restricted to the first computers that log in (I think).

Computer CALs are the only type of TSCALs that Windows 2000 TS supports.

The license on the XP Home box is probably corrupted. On the XP box, backup the following key: HKLM\Software\Microsoft\MSLicensing.

Then delete the entire MSLicensing key and all subkeys. Then reboot the XP box and try to connect again. The first successful connection will give the client a temporary license. The second successful connection should change that to a perm license.