Timeout Error While Trying To Join Node To Windows Server 2008 R2 Failover Cluster

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

SYMPTOMS

When attempting to join a new node to an existing Failover Cluster, you receive a time out error at the end of the Add Node Wizard.

CAUSE

There are have been multiple causes for this error and each should be checked.
  1. Duplicate objects in Active Directory.
  2. IPv6 enabled on the existing nodes and disabled on the node trying to join.
  3. Invalid DNS entries.



RESOLUTION

  1. To check for duplicate Active Directory objects, use LDIFDE.EXE from a command line to do the search.

    Example: C:\> ldifde -f output.ldf -r "(samAccountName=W2K8-R2*)"

    In the example above:

    -f = filename to write to
    -r = the variable to search
    W2K8-R2* = give me everything that starts with W2K8-R2

    This will create the file output.ldf in the current directory that can be read by notepad.  If you review the file, if it is a computername, you will see the below information:

    objectclass: Computer
    ServicePrincipleName: ****

    If it is a user or service account, it will not have the above, but would have:

    UserPrincipleName= ****

    Also in the sections, it will give you the current OU that it resides in. To get the node to join, you must rename user/service account name to something else. For this, just go to the OU listed.
  2. We have seen IPv6 being disabled on the new nodes and enabled on the existing nodes giving this error as well. Failover Clustering will use IPv6 first for its Cluster communication between nodes, if it is an enabled protocol. It will drop and use IPv4 only if IPv6 is disabled. Failover Clustering is not going to mix and match the versions.

    For example, you have an existing running Windows 2008 R2 Failover Cluster with IPv6 enabled. Any new node that will be brought into the Cluster will also need IPv6 enabled. The new node will be senbding IPv4 traffic to the running Cluster and will be ignored.
  3. Any kind of name resolution issues will also cause these time outs as it may be going to something it is not intended. If you are using any DNS or WINS, all entries need to be checked. If there is an invalid entry somewhere, it should be cleaned up and corrected.

MORE INFORMATION

These are some of the more common issues we are seeing. There may be others and article will be updated as they come in.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2634445 - Last Review: October 19, 2011 - Revision: 2.0
APPLIES TO
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Datacenter without Hyper-V
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Enterprise without Hyper-V
Keywords: 
kbclustering KB2634445

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