Article ID: 328478
Article Last Modified on 2/16/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Datacenter Server
This article was previously published under Q328478
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SYMPTOMS
When a logon attempt by a Windows Terminal Services client is unsuccessful, an event is logged in the Security log. This event records the logon failure, but it does not contain the IP address or the computer name that indicates where the unsuccessful logon attempt occurred.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to obtain the latest Windows 2000 service pack
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------------- 10-Dec-2002 21:50 5.0.2195.6158 333,072 Msgina.dll 13-Nov-2002 21:36 5.3.10.0 4,096 Spmsg.dll 13-Nov-2002 21:37 5.3.10.0 87,040 Spuninst.exe 10-Dec-2002 21:50 5.0.2195.6158 37,648 Winsta.dll 13-Nov-2002 21:37 5.3.10.0 18,432 Spcustom.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
MORE INFORMATION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
After you install this update, the security event that is logged after an unsuccessful Terminal Services logon attempt still does not contain the IP address or computer name. However, an additional event is added to the System log of Event Viewer. This new event specifies an IP address that indicates where the unsuccessful Terminal Services logon attempt was made. For example:
Event ID 35016
Terminal Services Remote Logon Failure:
User Name: Username
Domain: DOMAINNAME
Error Code: 0xc000006d
Source Network Address: 198.168.0.1
To turn on this new functionality, you must create the following registry value and set it to a value of 1 (one):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Value name: LogTSFailures
Value type: REG_DWORD
Value data: 1
Additionally, Windows 2000 SP4 automatically adds the EventMessageFile value to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System\TermService
The EventMessageFile value may cause Citrix MetaFrame event logging to stop working as expected. If this issue occurs, contact Citrix to obtain a possible workaround or resolution to this issue. For information about how to contact Citrix, visit the following Citrix Customer Care Web site:
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
The EventMessageFile value is located in the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System\TermService
You must add the following data to this value:
%SystemRoot%\System32\sp3res.dll
To add this data to the EventMessageFile value:
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System\TermService - On the Registry menu, click Export Registry File.
- In the File name box, type exported termservice key, and then click Save.
Note If you want to restore this registry subkey in the future, you can do so by double-clicking the Exported termservice key.reg file that you saved. - In the right pane, right-click EventMessageFile, and then click Modify.
- Click to put the insertion point at the end of the contents in the Value data box, and then type the following data (including the semicolon [;]):
;%SystemRoot%\System32\sp3res.dll
- Click OK, and then quit Registry Editor.
For more information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the following article number to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server product
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
891076 An event that is logged in the Security log does not in include the IP address or the computer name of the Terminal Services client
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Keywords: kbhotfixserver kbqfe kbwin2ksp4fix kbbug kbfix kbwin2000presp4fix KB328478
