Unable to Join or to Fail Over the Cluster if Nodes Have Different Subnets

This article was previously published under Q279119
This article has been archived. It is offered "as is" and will no longer be updated.
When you attempt to add a node to a cluster, you may receive the following error message:
Warning: This system is not attached to all defined cluster networks.
Then, a dialog box is displayed to configure the network's name, a step which had already been completed on node A.


When you try to fail over an Internet Protocol (IP) address resource to an existing node, the IP address may not come online, an Event ID 1069 message is displayed, and then your system returns to the original node.

If you open Cluster Administrator, you may observe an additional network connection listed under "Cluster Configuration / Networks".
This behavior can occur if you are using Dynamic Host Configuration Protocol (DHCP) assigned IP addresses for the nodes of a cluster. The nodes may have obtained IP addresses that are on different subnets (one subnet is a super-scoped subnet of the other). In this case, clustering does not enable you to join a new cluster, or to fail over an existing cluster.

This behavior can also occur if you have installed a different number of network adapters or ports in the nodes. This situation can enable the creation of an additional cluster network to which a different node with fewer interfaces cannot attach itself.
Microsoft Cluster Server does not support failing over IP address resources to different subnets. It is recommended that you only use static IP addresses on all interfaces in Cluster Server. You must change your IP addresses to static addresses and verify that they are in the same IP scope, and that your subnet mask is entered correctly. If your nodes are on different physical segments, you can create a virtual local area network (LAN) so that they seem to be on the same subnet.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
247392 MSCS/Cluster Node Is Not Attached to All Cluster Defined Networks
258750 Recommended Private Heartbeat Configuration on Cluster Server
MSCS W2000MSCS server cluster

Article ID: 279119 - Last Review: 10/21/2013 03:37:16 - Revision: 2.5

  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows NT Server 4.0 Enterprise Edition
  • kbnosurvey kbarchive kbbug kberrmsg kbpending KB279119