When a Linux-based client computer tries to access a domain controller that is running Windows Server 2003 or Windows 2000, an access violation occurs

You are using a Linux-based client computer in an Active Directory directory service domain where the domain controller is running Microsoft Windows Server 2003 or Microsoft Windows 2000. When the client computer tries to access the domain controller, heap corruption may occur on the domain controller. The heap corruption deletes data from valid memory addresses and generates an access violation in the LSASS service.

Note This access violation causes the domain controller to crash.

This behavior occurs when the following conditions are true:

• A Linux client computer tries to query the domain controller by using a signed and sealed Lightweight Directory Access Protocol (LDAP) request.
• The LDAP bind calls use encryption buffers that are smaller than the encryption block size.

Windows Server 2003 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:

Windows Server 2003 hotfix information

Prerequisites

To apply this hotfix, the computer must be running one of the following operating systems:

• An Itanium-based version of Windows Server 2003 with Service Pack 1 (SP1)
• A 32-bit version of Windows Server 2003 with Service Pack 1 (SP1)
• An x64-based version of Windows Server 2003

Restart requirement

You must restart the computer after you apply this hotfix. This is because the Lsass.exe file must reload.

Hotfix replacement information

This hotfix replaces the hotfix that is documented in the following Microsoft Knowledge Base article:

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, x64-based versions

Windows Server 2003, Itanium-based versions

Windows Server 2000 hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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.

Prerequisites

To apply this hotfix, the computer must be running Windows Server 2000.

Restart requirement

You must restart the computer after you apply this hotfix. This is because the Lsass.exe file must reload.

Hotfix replacement information

This hotfix replaces the hotfix that is documented in the following Microsoft Knowledge Base article:

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.

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

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base: