Article ID: 328478 - View products that this article applies to.
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:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows registry
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.
Service pack informationTo 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:
(http://support.microsoft.com/kb/260910/ )How to obtain the latest Windows 2000 service pack
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
File informationThe 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 188.8.131.52 4,096 Spmsg.dll 13-Nov-2002 21:37 184.108.40.206 87,040 Spuninst.exe 10-Dec-2002 21:50 5.0.2195.6158 37,648 Winsta.dll 13-Nov-2002 21:37 220.127.116.11 18,432 Spcustom.dll
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.
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
Additionally, Windows 2000 SP4 automatically adds the
Value name: LogTSFailures
Value type: REG_DWORD
Value data: 1
EventMessageFilevalue to the following registry key:
EventMessageFilevalue 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:
http://www.citrix.com/site/customerCare/index.aspMicrosoft 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.
EventMessageFilevalue is located in the following registry subkey:
You must add the following data to this value:
%SystemRoot%\System32\sp3res.dllTo add this data to the
265173For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/265173/ )The Datacenter Program and Windows 2000 Datacenter Server product
891076The 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.
(http://support.microsoft.com/kb/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
Article ID: 328478 - Last Review: February 16, 2007 - Revision: 2.5
Contact us for more help
Connect with Answer Desk for expert help.