PSS ID Number: 837202
Article Last Modified on 9/9/2004
The information in this article applies to:
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
SYMPTOMS
When you try to add or to join a node to an existing cluster, you may receive the following error:
The following entries may appear in the ClCfgSrv.log file:
[INFO] [BC] Cluster Service Win32 Exit Code= 0x00042b [INFO] [BC] Cluster Service Specific Exit Code= 0x001702
The following events may appear in the system event log on the joining node:
Event Type: Error
Event Source: ClusSvc
Event Category: Membership Mgr
Event ID: 1173
Description: Cluster service is shutting down because the membership engine detected a membership event while trying to join the server cluster. Shutting down is the normal response to this type of event. Cluster service will restart per the Service Manager's recovery actions.
CAUSE
This problem occurs if all the following conditions are true:
- You set the Network security: LAN Manager authentication level policy to Send NTLMv2 response only\refuse LM & NTLM.
- You set the Network security: Minimum session security for NTLM SSP based (including secure RPC) clients policy to Require NTLMv2 session security.
- You set the Network security: Minimum session security for NTLM SSP based (including secure RPC) servers policy to Require NTLMv2 session security.
However, this problem also occurs if you apply a high-security domain policy template.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
309689 How to apply predefined security templates in Windows 2000
The following policy settings may have been enabled by the domain policy template:
- Network security: Minimum session security for NTLM SSP based (including secure RPC) clients
- Network security: Minimum session security for NTLM SSP based (including secure RPC) servers
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Windows Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone 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
No prerequisites are required.
Restart requirement
You do not have to restart your 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) 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 tool in Control Panel.
Windows Server 2003, 64-Bit Edition
Date Time Version Size File name -------------------------------------------------------------- 18-May-2004 21:15 5.2.3790.173 341,504 Msv1_0.dll 18-May-2004 21:13 5.2.3790.173 129,536 Wmsv1_0.dll
Windows Server 2003, 32-bit editions
Date Time Version Size File name -------------------------------------------------------------- 19-May-2004 00:13 5.2.3790.173 129,536 Msv1_0.dll
WORKAROUND
To work around this problem, remove the NTLM version 2 (NTLMv2) requirement from the security policies. To do this, follow these steps:
- Click start, point to Administrative Tools, and then click Domain Security Policy.
- Expand the Local Policies subtree, and then click Security Options.
- Double-click Network security: Minimum session security for NTLM SSP based (including secure RPC) clients.
- Click to clear the Require NTLMv2 session security check box, and then click OK.
- Double-click Network security: Minimum session security for NTLM SSP based (including secure RPC) servers.
- Click to clear the Require NTLMv2 session security check box, and then click OK.
Note We recommend that you restart both nodes after you modify any one of the security policy settings.
Make sure that the Cluster service account has the correct permissions.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
269229 How to manually re-create the Cluster service account
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
REFERENCES
For additional information about joining a cluster node in Microsoft Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
272129 Cluster service does not start on "joining" node in Windows 2000 cluster
For additional information, 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 query words: sponsor clustered mscs
Keywords: kbClustering kbFileSystems kbWinServ2003SP1fix kbWinServ2003preSP1fix kbSecurity kbQFE kbfix kbBug KB837202
Technology: kbWinServ2003Ent kbWinServ2003EntSearch kbWinServ2003Search kbWinServ2003St
