This article was previously published under Q272129
This article has been archived. It is offered "as is" and will no longer be updated.
The Cluster service starts on the first node on a Windows 2000-based cluster, but may not start on a joining node, or a node may not join an existing cluster on the initial installation. The following events may be logged in the system log in sequential order:
Event ID 9 The device, \Device\Scsi\Scsi/Fibre Controller, did not respond within the timeout period.
Event ID 1009 The Clustering Service could not join an existing cluster and could not form a new cluster. The Clustering Service has terminated.
Event ID 7031 The Cluster Service service terminated unexpectedly. It has done this X time(s). The following corrective action will be taken in XXXXXX milliseconds. Restart the service.
This problem may occur after you apply a security template through a domain policy or by manually setting the LAN Manager Authentication Level Local Security Policy option to anything other than Send LM and NTLM responses on the nodes in a Windows 2000-based cluster.
The Cluster service does not function properly using NTLM 2. All cluster authentication is handled internally to the Cluster service after using RPC datagrams to form a cluster. The only time the Cluster service contacts a domain controller for authentication is when the cluster is first formed to validate the Cluster service account. Every node that requests to join a cluster is validated by using RPC communication over the private network by the node that owns the quorum resource. Only LM or NTLM authentication is used.
LmCompatibility settings range from 0 to 5. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Any entry other than "LmCompatibilityLevel=0" allows for the negotiation of NTLM 2 among Windows 2000-based clients and servers. Specifically, the "LmCompatibilityLevel=0" setting equates to "Send LM and NTLM response; never use NTLM 2 session security. Clients use LM and NTLM authentication, and never use NTLM 2 session security; domain controllers accept LM, NTLM, and NTLM 2 authentication."
If you permit or force NTLM 2 by using either a local security policy or by using a domain security policy, a cluster can be formed, but a cluster node cannot be joined. When you install the Cluster service on nodes other than the first and the LmCompatibilityLevel setting is set to something other than 0 (zero), the installation stops working when you are prompted to enter the name of the cluster to join. The error message is:
The specified cluster name could not be found on the network. Make sure the cluster is running and that the cluster node is reachable from this node.
If you start a command prompt and ping the cluster name, the cluster IP address is returned. You can then use Registry Editor to change the LmCompatibilityLevel setting to 0 (zero), which allows the Cluster service installation on the node to be completed. However, the LmCompatibilityLevel setting will be different among the nodes; the Cluster service will not start and the following events will be registered in the System log:
Event ID 1079: The node cannot join the cluster because it cannot communicate with node NODE1 over any network configured for internal cluster communication. Check the network configuration of the node and the cluster.
Event ID 7023: The Cluster Service service terminated with the following error: A security package specific error occurred.
The English version of this fix should have the following file attributes or later:
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 resolve this problem, return the NTLM authentication level to its default level of Send LM and NTLM responses. Follow these steps on each node in your Windows 2000-based cluster:
In Control Panel, double-click Administrative Tools.
Start the Local Security Policy tool.
Expand Local Policies, and then click Security Options.
Double-click Lan Manager Authentication Level, and then click Send LM and NTLM responses.
Click OK, and then quit Local Security Policy Editor.
Restart the server.
You can also resolve this issue by editing the registry:
Start Registry Editor.
Locate, and then click the following registry key: