MS01-052: Clients with an Expired Temporary License May Be Unable to Connect to Terminal Services
This article was previously published under Q315404
This article has been archived. It is offered "as is" and will no longer be updated.
New Terminal Server clients, Terminal Services clients, or Remote Desktop Connection clients may connect to Terminal Services correctly, but some existing clients that could previously connect may be unable to connect. If an existing client cannot connect, the following error message may be displayed on the client computer:
Terminal Server has ended the connectionIn all cases, clients can connect as if they were new clients if you delete the license from the client. For additional information about deleting licenses, click the article number below to view the article in the Microsoft Knowledge Base:
248430 How to Transfer Terminal Services CAL from One Computer to Another
If a client's temporary license expires and the license server that is contacted by the Terminal Services server is not the issuer of the client's temporary license, the license server does not upgrade the license to a permanent license. This is most likely to occur because the original issuer of the temporary license cannot be contacted by the Terminal Services server. This may occur because the license server has been rebuilt or is currently unavailable.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service PackThe resolution for this problem is also included in Windows 2000 Security Rollup Package 1 (SRP1). For additional information about SRP1, click the article number below to view the article in the Microsoft Knowledge Base:
311401 Windows 2000 Security Rollup Package 1 (SRP1), January 2002The fix for this issue is included in the following patch:
287687 Terminal Services Licensing Enhancements
Microsoft has confirmed that this problem may cause a degree of security vulnerability in Microsoft Windows 2000. This problem was first corrected in Windows 2000 Service Pack 3.
The fix for this problem is server-side (on the license server). Because Terminal Services may potentially have a wide variety of clients that connect to it, it is not possible to list every affected client platform in this article. This may also affect clients running third-party operating systems or other Microsoft clients that may not be explicitly listed.
kbTermServ security_patch kbWin2000srp1
Article ID: 315404 - Last Review: 12/07/2015 08:32:30 - Revision: 4.4
Microsoft Windows 2000 Service Pack 1, Microsoft Windows 2000 Service Pack 2, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Service Pack 1, Microsoft Windows 2000 Service Pack 2, Microsoft Windows 95, Microsoft Windows 98 Standard Edition, Microsoft Windows 98 Second Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows XP Home Edition, Microsoft Windows XP Professional
- kbnosurvey kbarchive kberrmsg kbbug kbfix kbwin2000presp3fix kbwin2000sp3fix kbsecurity kbtermserv KB315404