The Lsass.exe process crashes when you use Kerberos authentication to log on to a MIT realm on a Windows Server 2003 SP1-based domain controller

When you use Kerberos authentication on a Microsoft Windows Server 2003-based domain controller and try to log on to a Massachusetts Institute of Technology (MIT) Kerberos realm, the Lsass.exe process on the domain controller crashes and the computer restarts. Also, the following events are logged in the system event log:

Event ID: 1074
Event Source: USER32
User: NT AUTHORITY\SYSTEM
Computer: ComputerName
Description: The process winlogon.exe has initiated the restart of computer ComputerName on behalf of user for the following reason: No title for this reason could be found.
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\WINDOWS\system32\lsass.exe' terminated unexpectedly with status code -1073740972. The system will now shut down and restart.

Event ID: 26
Application popup: System Shutdown - The system is shutting down. Please save all work in progress and log off. Any unsaved changes will be lost.
This shutdown was initiated by NT AUTHORITY\SYSTEM. Shutdown will begin in 57 seconds.
Shutdown message: The system process 'C:\WINDOWS\system32\lsass.exe' terminated unexpectedly with status code -1073740972.
The system will now shut down and restart.

Additionally, the following error message is logged in the application event log:

This problem occurs because the Windows Server 2003-based domain controller uses Domain Naming System (DNS) lookup to automatically find a trusted MIT realm Key Distribution Center (KDC). The Lsass.exe process that is running on a domain controller experiences a crash when the domain controller uses DNS lookup to automatically find a trusted MIT realm KDC.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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 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

Windows Server 2003, x64-based versions

To work around this problem, use the Ksetup.exe utility to manually add the MIT realm KDCs to the domain controller. To do this, follow these steps.

Note The Ksetup.exe utility is located in the \Support\Tools folder on the Windows Server 2003 CD-ROM.

1. Click Start, click Run, type cmd.exe, and then click OK.
2. At the command prompt, type a command that resembles the following, and then press ENTER:
   ksetup /addkdc MTU.EDU kerberos.mtu.edu
   
   
   Note In this command, MTU.EDU represents the MIT realm name and kerberos.mtu.edu represents the KDC host name. If you want to add more than one KDC, repeat step 2.
3. Click Start, click Run, type cmd.exe, and then click OK.
4. At the command prompt, type a command that resembles the following, and then press ENTER:
   ksetup /addkpasswd MTU.EDU kerberosmaster.mtu.edu
   
   
   Note In this command, MTU.EDU represents the MIT realm name and kerberosmaster.mtu.edu represents the KDC master name.
5. At the command prompt, type exit, and then press ENTER to close the Command Prompt window.

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 Server 2003 Service Pack 2.

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

Technical support for x64-based versions of Microsoft Windows

Your hardware manufacturer provides technical support and assistance for x64-based versions of Windows. Your hardware manufacturer provides support because an x64-based version of Windows was included with your hardware. Your hardware manufacturer might have customized the installation of Windows with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your x64-based version of Windows. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:

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.