The Lightweight Directory Access Protocol (LDAP) directory service is hosted on many nodes that are put behind a Network Load Balancing (NLB) server.
The nodes use Secure Socket Layer (SSL), and the nodes are configured to use an alias name.
You try to establish SSL connections to the nodes by using the alias name from the LDAP client computer that is running Windows 7 or Windows Server 2008 R2.
In this scenario, the operation fails, and you receive the following error:
<Result value="800B010F">The certificate's CN name does not match the passed value.</Result>
Additionally, the following Error event is logged in the System log:
Event Type: Error Event Source: Schannel Event ID: 36884 Description: The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is server_name. The SSL connection request has failed. The attached data contains the server certificate.
This problem occurs because of an error in Windows 7 and in Windows Server 2008 R2. The LDAP client stores the node's canonical name in the alias field. This problem occurs if the node alias and the node name are different.
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 website:
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.
To apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To use one of the hotfixes in this package, you must create a registry subkey. To do this, follow these steps:
Create a new REG_DWORD value that is named UseHostnameAsAlias, and set the value to anything other than zero.
Exit Registry Editor, and then restart the computer.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 7 and 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 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 and for Windows 7" 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 x86-based versions of Windows 7
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
For all supported IA-64-based versions of Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to configure LDAP over SSL requirements for Active Directory Lightweight Directory Services (AD LDS), visit the following Microsoft website:
Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Standard without Hyper-V, Windows Server 2008 R2 Enterprise without Hyper-V, Windows Server 2008 R2 Datacenter without Hyper-V