Re: Licensing Errors...

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Which licenses do you have on the TS Licensing Server?
Note that now you have upgraded the Terminal Servers to 2003, you
also need 2003 TS CALs for all of your clients (including XP Pro
and Vista clients).

And if you do have 2003 TS CALs (but you didn't mention re-
installing any license packs after re-installing the LS), then
check that the type of the 2003 TS CAL (i.e. Per Device or Per
User) matches the licensing type of your Terminal Servers (by
default, this is Per Device).

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

Erimikos <denlspe@xxxxxxxxx> wrote on 28 jun 2007:

Ok.. here is a quick rundown of the scenario..

We had a Windows 2000 Server Terminal Services Licensing Server
(COMM2 - Domain Controller), 2 Windows 2000 Server Terminal
services servers(TRMSRV1 & 2), and many clients as different
locations, ranging in OS from Windows 95 to Vista.

We are in the process of upgrading servers and domain to 2003,
and I did not realize that COMM2 was functioning as a license
server for terminal services, as it wasn't on our lists, and the
upgrade advisor did not point it out. After the server and
domain were upgraded, While most of the clients are still
connecting without issues, we have started having issues with a
couple clients machines.

The terminal services licensing snap-in was not connecting to
any license servers, so I reinstalled terminal services
licensing on OHSCOMM2, and activated it. I then did the
registry hack on both terminal servers to point them to COMM2 as
the license server, and restarted. This did not resolve the
issue.

A few of those machines are thinclients, so we obtained the
hotfix from Microsoft product support services, and applied that
to both terminal servers with no luck.

The clients are receiving the error message: "The remote
computer disconnected the session due to an error in the
licensing protocol.", and the event log on the terminal server
system event log shows event id 1004 from TermService: The
terminal server cannot issue a client license.

Anyone have any ideas? I am running out..
.

Relevant Pages

  • Re: Terminal Services Licensing question
    ... the server, but I did find this error message related to Terminal Services ... Use Terminal Server Licensing administrative tool to ... I did remove the temp license from one of the clients that was ...
    (microsoft.public.windows.terminal_services)
  • Re: TS in DMZ will not allow clients to connect - licensing issue
    ... External clients cannot get licenses issued so I assume the TS in the DMZ ... You can ping the license server, and it issues licenses to ther TS clients, ... Where is the TS Licensing Server located? ...
    (microsoft.public.windows.terminal_services)
  • Re: Windows 2003 Terminal Licensing Server not issuing licenses
    ... So it doesn't matter on which OS the TS Licensing Server ... Such TS CALs are in the TS Licensing ... Terminal Servers and wanted to use Per User TS licensing mode on ...
    (microsoft.public.windows.terminal_services)
  • Re: TS in DMZ will not allow clients to connect - licensing issue
    ... Where is the TS Licensing Server located? ... Have your internal clients received a free license from the built- ... What's the point of putting a server in the DMZ if it has to ...
    (microsoft.public.windows.terminal_services)
  • Re: Temporary Licences for Windows2000 Terminal Services Client
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... > Ok, the clients have Windows2000. ... > ** Are the Terminal Server and the TS Licensing Server running ... >> Are the Terminal Server and the TS Licensing Server running on ...
    (microsoft.public.windows.terminal_services)