Can't connect to terminal server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have terminal services running on a Windows 2000 Server computer and have
had no problems connecting with machines with XP pro. I have one user with a
XP home machine who has been able to connect for 90 days with a temporary
license which has now expired. She has upgraded to XP pro but continues to
get the same error message and won't let her connect. I understood that the
upgrade would get her a license to log on with her RDP connection without
limits. How can I resolve this problem? I haven't been able to find help on
the MS knowledge base.
 
I considered this but the technical bulletin refers to WIN 2K and this
problem is on the machine that is running XP pro. So do the same
instructions apply: the registry entry looks a little different on the XP
machine than the bulletin. Should I just go ahead and delete the entire
MSlicensing key? Please advise.
 
I can't see any difference on my XP compared with the KB article,
the licensing information is stored under HKLM\Software\Microsoft
\MSLicensing, as described.

As always when editing the registry, back it up first, or at least
export the key you want to remove before actually deleting it.
Then you can always import it again if things go wrong.
I'd delete everything under MSLicensing.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Well, please excuse if this is a duplicate post, but I didn't see my last
reply post:
I deleted the keys suggested and continued to get the same error message:
"The remote computer disconnected the session because of an error in the
licensing protocol. Please try connecting to the remote computer again or
contact your serve administrator." Interestingly, now that XP pro is on the
machine a liscense appears on the Terminal Services Licensing control panel
for the computer. As we have deleted the keys several times, each time a new
connection is attempted, a new license is created under Existing Windows 2000
licenses. The error message persists however. There seems to be something
else that needs to be done. Does the suggestion in Article ID : 323597 apply
or is there some other fix that I should try? HELP!
 
Aaaah, but the situation has now actually changed, hasn't it?
Your first post mentioned that the temporary license had expired,
and after deleting it, the error message is about a licensing
protocol error. It needs to be fixed on the server, yes, as
described in KB 323597.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Back
Top