List of Terminal Services Fixes in Windows 2000 Service Pack 4 (815017)

MORE INFORMATION

Debug Output Is Generated When You Log Unsuccessful Logon Attempts by Terminal Services

When you use the method that is described in the following Microsoft Knowledge Base article to log an event for each unsuccessful logon attempt by using Terminal Services, additional debug output is generated to the kernel debugger:

328478 Security Event Does Not Contain an IP Address or Computer Name When an Unsuccessful Logon Attempt Occurs

WinStationQueryInformation Returns User Data in Clear Text Form

Under certain conditions, a call to WinStationQueryInformation may cause user information to be returned in clear text form.

Memory Leak Caused by Runaway Thread Creation in Terminal Services Licensing Server

A memory leak may occur on a Windows 2000-based Terminal Services licensing server. When GetAllEnterpriseServer() is called, CoIntialize() is also called. This creates two threads and loads Cdoexm.dll and Pptrace.dll. Each GetAllEnterpriseServer() call loads the Cdoexm.dll and Pptrace.dll library files, but they are not unloaded with CoUninitialize().

A Terminal Server That Is Running in Remote Administration Mode Does Not Start

Terminal Services may not start when the Windows 2000-based server is running Terminal Services in Remote Administration mode. Additionally, an event ID 1014 message is logged with a description similar to the following:Cannot load illegal module: C:\WINNT\System32\rdpwsx.DLL For additional information about the bugs fixed in Windows 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:

327194 List of Bugs Fixed in Windows 2000 Service Pack 4

For additional information about how to obtain the latest Windows 2000 service pack, click the following article number to view the article in the Microsoft Knowledge Base: