Some Workstations on Network Unable to Terminal into Windows 2000 Terminal Server - Used to Work Fine

Posted on 2007-10-17
Last Modified: 2013-12-05
We have a small network of two servers. One server is a windows 2003 server, and the other is a windows 2000 advanced server.  The 2000 advanced server is a standalone terminal server and is just a member of the domain. The 2003 server is our main primary domain server and also has exchange.

For a long time we had no problems, however recently some computers will not connect. *SOME* not all workstations started being unable to connect. When we try to connect from these workstations we get the following error:

Error: The remote computer disconnected the session because of an error in the licensing protocol.

It is really strange because it is not all of the computers, and just some. Additionally all of our computers are XP Pro workstations which according to my understanding should be getting a free terminal cal license.

The one computer worked and then started to give the above message. We tried formatting and reloading and it still didn't fix. We have a feeling it is something with windows updates.

Event Type:      Warning
Event Source:      TermService
Event Category:      None
Event ID:      1010
Date:            10/17/2007
Time:            3:06:37 AM
User:            N/A
Computer:      TERMSRV
The terminal services could not locate a license server. Confirm that all license servers on the network are registered in WINS\DNS, accepting network requests, and the Terminal Services Licensing Service is running.


Event Type:      Warning
Event Source:      LicenseService
Event Category:      None
Event ID:      213
Date:            10/12/2007
Time:            3:48:27 AM
User:            N/A
Computer:      TERMSRV
Replication of license information failed because the License Logging Service on server \\SRV2003 could not be contacted.
0000: 22 00 00 c0               "..À    
Question by:FASTECHS
    LVL 13

    Expert Comment

    by:George Sas
    The error says it: Your machines have no licenses to connect to the Terminal server.
    Is the server running with Per Client of Per Machine licenses ?
    LVL 5

    Assisted Solution

    In control panel, add/remove programs, windows components....make sure you have the terminal services license server installed.
    Worst case, if you already have it installed, remove and reinstall it.

    XP machines don't get a free terminal server CAL. They can use Remote desktop to connect to the server, but cannot connect as a regular user, unless you purchase a terminal server CAL.

    Hope that helps.

    Author Comment

    Thats really strange. My Windows 2000 CD says it comes with 10 Terminal Server CALS. I bought from a legit spot too. I tried to install license server on the 2000 machine but it gave me some error that it is not a primary domain controller. It is really bizarre because everything worked just fine for nearly a year.
    LVL 13

    Accepted Solution

    As per default you will get some temporary licenses that will expire in time.
    You will also have to install those licenses on your licensing server.
    Try to install the licensing again and install the licenses you bought.
    Eventually you can try the licensing model from per machine to per user and restart the TS machine.
    See if it works that way.

    Featured Post

    The problems with reply email signatures

    Do you wish that you could place an email signature under a reply? Well, unfortunately, you can't. That great Exchange/Office 365 signature you've created will just appear at the bottom of an email chain. What a pain! Is there really no way to solve this? Well, there might be...

    Join & Write a Comment

    Introduction You may have a need to setup a group of users to allow local administrative access on workstations.  In a domain environment this can easily be achieved with Restricted Groups and Group Policies. This article will demonstrate how to…
    Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

    732 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    24 Experts available now in Live!

    Get 1:1 Help Now