Security Event 529 is logged for local user accounts

Symptoms

Consider the following scenario. A Microsoft Windows XP Professional-based member computer is joined to a domain controller. In the domain controller, the audit policy is turned on for logon failures. When a local user on the member computer logs off, the following event is logged two times in the Security log in the domain controller:
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 529
Date: date
Time: time
User: NT AUTHORITY\SYSTEM
Computer: domain controller computer name
Description:
Logon Failure:
Reason: Unknown user name or bad password
User Name: user name
Domain: client computer name
Logon Type: 3
Logon Process: KSecDD
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0

Workstation Name: client computer name

For more information, see Help and Support Center at http://support.microsoft.com.
Consider the following scenario. A Microsoft Windows Server 2003-based member computer is joined to a domain controller. In the domain controller, the audit policy is turned on for logon failures. When a local user on the member computer logs off, the following event is logged in the Security log in the domain controller:
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 529
Date: date
Time: time
User: NT AUTHORITY\SYSTEM
Computer: domain controller computer name
Description:
Logon Failure:
Reason: Unknown user name or bad password
User Name: user name
Domain: client computer name
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM

Workstation Name: client computer name

For more information, see Help and Support Center at http://support.microsoft.com.

Cause

When a user logs off, Windows XP or Windows Server 2003 re-reads the user record for updated information to optimize the next logon process. However, Windows ignores the fact that the user is from the local SAM database and instead tries to contact the domain if the computer is a member of a domain.

Resolution

Windows XP

To resolve this problem, obtain the latest service pack for Microsoft Windows XP.

Service pack information

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

322389 How to obtain the latest Windows XP service pack

For more information about the list of fixes included in Windows XP Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

811113 List of fixes included in Windows XP Service Pack 2

Windows Server 2003

To resolve this problem, do one of the following:
  • Obtain the latest service pack for Microsoft Windows Server 2003.
  • Apply the hotfix that is mentioned in this article to the Windows Server 2003-based member computer.

Service pack information

For more information about how to obtain the latest service pack for Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information

A 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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: Note 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.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) 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.
Windows Server 2003, Itanium-based Systems

Date Time Version Size File name Platform
------------------------------------------------------------------------
08-Jul-2005 13:17 5.2.3790.367 640,000 Winlogon.exe IA-64
08-Jul-2005 13:26 5.2.3790.367 67,072 Arpidfix.exe IA-64
24-Feb-2005 15:22 6.1.22.4 639,712 Updspapi.dll IA-64
Windows Server 2003, 32-bit versions

Date Time Version Size File name
-------------------------------------------------------------
11-Jul-2005 19:55 5.2.3790.367 497,152 Winlogon.exe
09-Jul-2005 02:02 5.2.3790.367 30,208 Arpidfix.exe
05-Mar-2005 01:30 6.1.22.4 371,936 Updspapi.dll

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Propriedades

ID do Artigo: 811082 - Última Revisão: 09/10/2011 - Revisão: 1

Comentários