Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

An LDAP client authentication request fails when the Digest-MD5 SASL subsequent authentication mechanism is used


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You install the Active Directory Domain Services (AD DS) role on a computer that is running Windows Server 2008 or Windows Server 2008 R2.
  • A Lightweight Directory Access Protocol (LDAP) client supports SASL Digest-MD5 subsequent authentication and sends an authentication request using the SASL Digest-MD5 authentication mechanism.
  • However, Active Directory Domain Services (AD DS) does not support subsequent authentication when the Digest-MD5 Simple Authentication and Security Layer (SASL) authentication mechanism is used, but still indicates that it does to the client.

In this scenario, the LDAP client authentication request fails.

↑ Back to the top


Cause

Active Directory Domain Services (AD DS) does not support subsequent authentication when the Digest-MD5 Simple Authentication and Security Layer (SASL) authentication mechanism is used.

↑ Back to the top


Resolution

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 the problem described in this article. 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

To apply this hotfix, the computer must be running one of the following operating systems:
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows Server 2008 R2
Additionally, the computer must have the Active Directory Domain Services (AD DS) role installed.

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

968849 How to obtain the latest service pack for Windows Server 2008

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    1.
    22xxx
    Windows Server 2008RTMLDR
    6.0.600
    2.
    22xxx
    Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Ntdsai.dll6.0.6001.225411,950,72014-Oct-200915:07x86
Ntdsai.dll6.0.6002.222451,950,72014-Oct-200914:11x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Ntdsai.dll6.0.6001.225412,635,77614-Oct-200915:08x64
Ntdsai.dll6.0.6002.222452,635,77614-Oct-200914:26x64
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.1.760
    0.
    21xxx
    Windows Server 2008 R2RTMLDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Ntdsa.mofNot Applicable227,76510-Jun-200920:34Not Applicable
Ntdsai.dll6.1.7600.210612,726,40030-Sep-201107:23x64

↑ Back to the top


Status

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

↑ Back to the top


More Information

For more information about software update terminology, 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

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
X86_microsoft-windows-d..toryservices-ntdsai_31bf3856ad364e35_6.0.6001.22541_none_f125a6e9d25fe220.manifestNot Applicable12,57414-Oct-200916:56Not Applicable
X86_microsoft-windows-d..toryservices-ntdsai_31bf3856ad364e35_6.0.6002.22245_none_f31019f9cf829ca0.manifestNot Applicable12,57414-Oct-200915:30Not Applicable

Additional files for all supported x64-based versions of Windows Server 2008


File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-d..toryservices-ntdsai_31bf3856ad364e35_6.0.6001.22541_none_4d44426d8abd5356.manifestNot Applicable12,63214-Oct-200916:57Not Applicable
Amd64_microsoft-windows-d..toryservices-ntdsai_31bf3856ad364e35_6.0.6002.22245_none_4f2eb57d87e00dd6.manifestNot Applicable12,63214-Oct-200916:12Not Applicable

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_0a42936db200cbe5c4b36d51372fb3d2_31bf3856ad364e35_6.1.7600.21061_none_11367a0df37447da.manifest
File versionNot Applicable
File size716
Date (UTC)30-Sep-2011
Time (UTC)19:52
PlatformNot Applicable
File nameAmd64_microsoft-windows-d..toryservices-ntdsai_31bf3856ad364e35_6.1.7600.21061_none_4d5650aeebe4f2d7.manifest
File versionNot Applicable
File size3,531
Date (UTC)30-Sep-2011
Time (UTC)07:57
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,350
Date (UTC)30-Sep-2011
Time (UTC)19:52
PlatformNot Applicable

↑ Back to the top


References

For more information about the Simple Authentication and Security Layer (SASL) authentication, visit the Microsoft Web site: For more information about DIGEST-MD5 subsequent authentication implementation (2.1.3), visit the following Internet Engineering Task Force (IETF) Web site: Microsoft 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.

↑ Back to the top


Keywords: kbqfe, kbhotfixserver, kbsurveynew, kbautohotfix, kbexpertiseinter, kbbug, kbfix, kb

↑ Back to the top

Article Info
Article ID : 975697
Revision : 1
Created on : 1/7/2017
Published on : 11/9/2011
Exists online : False
Views : 229