MSCS/Cluster Node Is Not Attached to All Cluster Defined Networks

ID: Q247392

The information in this article applies to:

Microsoft Windows NT Server, Enterprise Edition version 4.0
Microsoft Windows 2000 Datacenter Server
Microsoft Windows 2000 Advanced Server

SYMPTOMS

During a join operation of a cluster node, you may receive the following error message:

Warning: This system is not attached to all defined cluster networks.

CAUSE

The Cluster service identifies networks based on network ID numbers. The network ID number is the result of a combination of subnet mask and IP addresses. If, during the join operation, the installation detects that the current node is not attached to all cluster networks, this warning message is displayed.

For example, node 1 has the following three interfaces:


172.16.100.1 / Subnet Mask 255.255.255.0
172.16.110.1 / Subnet Mask 255.255.255.0
172.16.120.1 / Subnet Mask 255.255.255.0

While Node 2 has the following:


172.16.100.2 / Subnet Mask 255.255.255.0
172.16.110.2 / Subnet Mask 255.255.255.0

During Node 2's join procedure, this error message may be displayed if all three networks were identified as cluster networks during node 1's installation. This error message may also be displayed if there is a configuration error in the IP settings for one node of the cluster.

RESOLUTION

To resolve this problem, check the IP settings for all nodes and resolve any configuration conflicts. If this network configuration is by design, ignore the warning.

MORE INFORMATION

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

Q169790 How to Troubleshoot Basic TCP/IP Problems in Windows NT 4.0

Q175141 Cluster Service Ignores Network Cards

Q241828 Nodes in Cluster constantly fail over upon rebooting either member

Additional query words:

Keywords : kbenv kbfile
Version : WINDOWS:2000; winnt:4.0
Platform : WINDOWS winnt
Issue type : kbprb