Authentication requests between nodes in the same cluster may be unable to use the Kerberos protocol if the Negotiate SSP is specified

Article translations Article translations
Article ID: 982549 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Authentication requests that use the Negotiate SSP may be unable to use the Kerberos protocol to access resources from one node in a cluster to another node in the same cluster. In this scenario, NTLM is used as the authentication protocol that cannot perform the delegation.

The following is an example scenario:
  • You install an instance of Microsoft SQL server on a node.
  • You install another instance of SQL server on another node.
  • In the first instance, you create a linked server that targets the second instance.
  • The cluster resource group which includes the second instance is failed over to the first node. Then, the cluster resource group is moved to the second node.
  • You access databases in the second instance on the first node by using a linked server configuration.
In this scenario, anonymous access is used to access the linked database unexpectedly. Therefore, inconsistent data results are returned.

CAUSE

This problem occurs because the target clustered resource DNS name is not removed from the local name table that is maintained by the Local Security Authority (LSA) when the cluster resource is transitioned into an offline state.

When a cluster resource is transitioned into an online state on a node, the Cluster service registers its DNS name and NetBIOS name into a table that is maintained by LSA. This table contains the names of all the cluster resources that are hosted on the Cluster node locally.

The registration of the DNS names is a new functionality in Windows Server 2008. Previously, only the NetBIOS names are registered.

When an application on the cluster node calls the InitializeSecurityContext function to start authentication with a service and the Negotiate SSP is used, LSA checks the local names table for the target name. If the target name exists in the local names table, LSA uses optimization to service the request. The optimization is used because the target resource is local. Therefore, is not necessary to build Kerberos authentication data to send to a remote host.

When a Cluster resource enters the offline state on the node, the DNS name is not removed from the table. In this situation, LSA considers the resource to be hosted on the local node. However, the resource is hosted on a remote node.

If LSA uses the optimization and the target service is not located on the local node, NTLM will be used to authenticate to the remote host. This results in a failure in the delegation and the impersonation on the remote host will be created under the anonymous context. Therefore, the access to the cluster resources may fail or there is no sufficient access to return the expected results.


RESOLUTION

After you apply this hotfix, the NetBIOS and DNS names will be removed from the local names table when the resource transitions into an offline state.

This hotfix also removes a dependency upon DNS name registration that may stop the local names table being updated. After you apply this hotfix, the DNS and NetBIOS names will be added or removed from the local names table regardless of DNS name registration.

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:
http://support.microsoft.com/contactus/?ws=support
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, you must be running Windows Server 2008 Service Pack 2 (SP2).

For more information, 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 may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released 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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 0 . 20xxxWindows VistaRTMLDR
    6.0.600 1 . 22xxxWindows Vista and Windows Server 2008SP1LDR
    6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxx version number.
  • 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 and for Windows Vista" 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Clusres.dll6.0.6002.22401919,04010-May-201016:53x86
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Clusres.dll6.0.6002.224011,155,07210-May-201016:55x64
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Clusres.dll6.0.6002.224011,925,63210-May-201016:47IA-64

STATUS

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

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

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameX86_25117a9ac770cc8e037806eb6dce6159_31bf3856ad364e35_6.0.6002.22401_none_4dd9ed6d8ce0c607.manifest
File versionNot applicable
File size711
Date (UTC)11-May-2010
Time (UTC)00:12
PlatformNot applicable
File nameX86_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.0.6002.22401_none_c34bb98cb33e4637.manifest
File versionNot applicable
File size10,641
Date (UTC)10-May-2010
Time (UTC)18:38
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameAmd64_9865deabe33f175b7397b28df433c13f_31bf3856ad364e35_6.0.6002.22401_none_1001171e77f6dd33.manifest
File versionNot applicable
File size715
Date (UTC)11-May-2010
Time (UTC)00:12
PlatformNot applicable
File nameAmd64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.0.6002.22401_none_1f6a55106b9bb76d.manifest
File versionNot applicable
File size10,693
Date (UTC)10-May-2010
Time (UTC)18:38
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameIa64_2e3559a55f65581234b49869a4b072f1_31bf3856ad364e35_6.0.6002.22401_none_a17e341562a168a1.manifest
File versionNot applicable
File size713
Date (UTC)11-May-2010
Time (UTC)00:12
PlatformNot applicable
File nameIa64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.0.6002.22401_none_c34d5d82b33c4f33.manifest
File versionNot applicable
File size10,667
Date (UTC)10-May-2010
Time (UTC)18:15
PlatformNot applicable

Properties

Article ID: 982549 - Last Review: September 11, 2010 - Revision: 2.1
APPLIES TO
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 for Itanium-Based Systems
Keywords: 
kbclustering kbHotfixServer kbautohotfix kbsurveynew kbexpertiseadvanced kbqfe kbfix KB982549

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com