Article ID: 247392
Article Last Modified on 3/1/2007
APPLIES TO
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Datacenter Server
- Microsoft Windows NT Server 4.0 Enterprise Edition
This article was previously published under Q247392
SYMPTOMS
During a join operation of a cluster node, you may receive the following error message:
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:
169790 How to Troubleshoot Basic TCP/IP Problems in Windows NT 4.0
175141 Cluster Service Ignores Network Cards
241828 Nodes in Cluster constantly fail over upon rebooting either member
Keywords: kbenv kbfile kbprb KB247392
