Discussion:
XP home
(too old to reply)
Allen
2005-03-21 14:29:02 UTC
Permalink
I have a windows 2000 terminal server with Terminal Server licensing running
on a lical DC. TS licensing has plenty of available licenses.

It seems that XP Home PCs are unable to obtain a license. They receive a
message saying there is an error in the licensing protocol. This is
happening on several XP home machines.

Any help is much appreciated.

Allen
Vera Noest [MVP]
2005-03-21 21:08:23 UTC
Permalink
Is there anything in the EventLog on the Terminal Server?
Have you tried to delete the locally stored license from the XP Home
clinets? Try with one client first, and see if you can connect *at
least 2 times*, since the first connection always uses a temporary
license.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Post by Allen
I have a windows 2000 terminal server with Terminal Server
licensing running on a lical DC. TS licensing has plenty of
available licenses.
It seems that XP Home PCs are unable to obtain a license. They
receive a message saying there is an error in the licensing
protocol. This is happening on several XP home machines.
Any help is much appreciated.
Allen
Allen
2005-03-22 02:03:06 UTC
Permalink
There is an event ID 1004. It basically says unable to issue license (sorry,
I don't have the exact text). I did try deleting the locally stored license
on the client, no difference.
Post by Vera Noest [MVP]
Is there anything in the EventLog on the Terminal Server?
Have you tried to delete the locally stored license from the XP Home
clinets? Try with one client first, and see if you can connect *at
least 2 times*, since the first connection always uses a temporary
license.
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Post by Allen
I have a windows 2000 terminal server with Terminal Server
licensing running on a lical DC. TS licensing has plenty of
available licenses.
It seems that XP Home PCs are unable to obtain a license. They
receive a message saying there is an error in the licensing
protocol. This is happening on several XP home machines.
Any help is much appreciated.
Allen
Vera Noest [MVP]
2005-03-22 20:39:20 UTC
Permalink
And I assume that the TS can locate the LS and the LS *does* issue
licenses to other clients correctly?
Does it work when you log on with an account that is a local
Administrator (on the XP Home client)? Users need write access to
the licensing registry key on the local machine to store the
license.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Post by Allen
There is an event ID 1004. It basically says unable to issue
license (sorry, I don't have the exact text). I did try
deleting the locally stored license on the client, no
difference.
Post by Vera Noest [MVP]
Is there anything in the EventLog on the Terminal Server?
Have you tried to delete the locally stored license from the XP
Home clinets? Try with one client first, and see if you can
connect *at least 2 times*, since the first connection always
uses a temporary license.
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Post by Allen
I have a windows 2000 terminal server with Terminal Server
licensing running on a lical DC. TS licensing has plenty of
available licenses.
It seems that XP Home PCs are unable to obtain a license.
They receive a message saying there is an error in the
licensing protocol. This is happening on several XP home
machines.
Any help is much appreciated.
Allen
Allen
2005-03-23 04:11:02 UTC
Permalink
Yes, it does issue licenses to other operating systems correctly. I haven't
checked if the user is a local Administrator but I did follow the steps found
in KB315277.
Post by Vera Noest [MVP]
And I assume that the TS can locate the LS and the LS *does* issue
licenses to other clients correctly?
Does it work when you log on with an account that is a local
Administrator (on the XP Home client)? Users need write access to
the licensing registry key on the local machine to store the
license.
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Post by Allen
There is an event ID 1004. It basically says unable to issue
license (sorry, I don't have the exact text). I did try
deleting the locally stored license on the client, no
difference.
Post by Vera Noest [MVP]
Is there anything in the EventLog on the Terminal Server?
Have you tried to delete the locally stored license from the XP
Home clinets? Try with one client first, and see if you can
connect *at least 2 times*, since the first connection always
uses a temporary license.
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Post by Allen
I have a windows 2000 terminal server with Terminal Server
licensing running on a lical DC. TS licensing has plenty of
available licenses.
It seems that XP Home PCs are unable to obtain a license.
They receive a message saying there is an error in the
licensing protocol. This is happening on several XP home
machines.
Any help is much appreciated.
Allen
Loading...