Microsoft KB Archive/824905

= Event ID 677 and event ID 673 audit failure messages are repeatedly logged to the Security log of domain controllers that are running Windows 2000 and Windows Server 2003 =

Article ID: 824905

Article Last Modified on 11/4/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server

-





Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
In a Microsoft Windows Server 2003 domain, event ID messages that are associated with account logon failures may be repeatedly logged to the security event log on domain controllers. For example, the following event message is repeatedly logged on Microsoft Windows 2000-based domain controllers: Type: Failure Audit

Source: Security

Event Category: Account Logon

Event ID: 677

User: NT AUTHORITY\SYSTEM

Description: Service Ticket Request Failed:

User Name:

User Domain:

Service Name:

Ticket Options: 0x40830000

Failure Code: 0xE

Client Address:



The following event message is repeatedly logged on Windows Server 2003-based domain controllers: Type: Failure Audit

Source: Security Event

Category: Account Logon

Event ID: 673

User: NT AUTHORITY\SYSTEM

Description: Service Ticket Request:

User Name:

Domain:

Service Name:

Service ID:

Ticket Options: 0x40830000

Ticket Encryption Type:

Client Address:

Failure Code: 0xD

Logon GUID:

Transited Services:



CAUSE
This problem occurs because the Kerberos client on Windows 2000-based computers and on Windows Server 2003-based computers examines the Key Distribution Center (KDC) at set intervals to verify that the Service-for-User (S4U) Kerberos extension is supported. By default, the Kerberos client examines the KDC every 15 minutes. Because Windows 2000 does not support the S4U Kerberos extension, event ID 677 messages are logged to the security event log of a Windows 2000 domain controller. In Windows Server 2003, event ID 673 messages are logged to the security event log if the S4U Kerberos extension is not configured. To use the S4U Kerberos extension, you must have a Windows Server 2003 native domain, and you must configure the appropriate computer accounts for constrained delegation.



RESOLUTION
This hotfix suppresses Event ID 677 and Event ID 673 in this context.

Hotfix information
A supported hotfix is now 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 Windows Server 2003 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 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 item in Control Panel.

Windows Server 2003, x86-based versions

Windows Server 2003, Itanium-based versions

Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

Prerequisites
To apply this hotfix, you must have Windows 2000 Service Pack 3 (SP3) installed on the computer.

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 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 item in Control Panel.

Note This hotfix should be applied to the following computers:
 * Domain controllers that are running Windows 2000 or Windows Server 2003
 * Member servers that are running Windows Server 2003



WORKAROUND
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this problem and to reduce the frequency of event ID 677 and event ID 673 event messages, increase the S4U cache timeout value in the Kerberos client on computers that are running Windows Server 2003:  On a computer that is running Windows Server 2003, click Start, click Run, type regedit, and then click OK. Locate and then click the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters

 On the Edit menu, point to New, and then click DWORD Value. Type S4UCacheTimeout, and then press ENTER. In the Value data box, type the number of minutes that you want to specify for the timeout value, and then click OK.

Note By default, the S4U cache timeout value is 15 minutes.</li> Quit Registry Editor.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
Windows Server 2003 introduces support for constrained delegation in the Service-for-User-to-Proxy (S4U2Proxy) extension to Kerberos. By using the S4U2Proxy extension, a service can obtain tickets to another service for a user. For more information about S4U Kerberos extensions, visit the following Microsoft Web site:

For more information about the LsaLogonUser For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New Naming schema for Microsoft Windows hotfix packages

For additional information about 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

Keywords: kbhotfixserver kbwinserv2003presp1fix kbbug kbfix kbqfe kbwin2000presp5fix KB824905

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.