Cluster network interface card is DHCP-enabled
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at https://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool queries the Win32_NetworkAdapterConfiguration Microsoft Windows® Management Instrumentation (WMI) class to determine the value of the DHCPEnabled key for all network interfaces in the cluster. If the Exchange Server Analyzer finds the value for DHCPEnabled set to True for any private network interface in the cluster, an error is displayed.
A value of True for the DHCPEnabled WMI key indicates that a network interface is configured to use the Dynamic Host Configuration Protocol (DHCP). Microsoft does not support using DHCP for nodes on the private network in a Windows server cluster. Additionally, it is recommended that you use static IP addresses for nodes on the public networks in a Windows server cluster. Using dynamic configuration of public networks through DHCP is not recommended, as the failure to renew a DHCP lease could disrupt cluster operations. Additionally, using dynamic configuration of private networks through DHCP is not supported, and should never be performed.
To resolve this problem, you must reconfigure the network interfaces for the private networks to use a static IP address. It is recommended that addresses be selected within the following ranges:
10.0.0.0 - 10.255.255.255 (Class A network)
172.16.0.0 - 172.31.255.255 (Class B network)
192.168.0.0 - 192.168.255.255 (Class C network)
To correct this error
In Network Connections, right-click the network connection for your private network adapter, and then click Properties.
Click Internet Protocol (TCP/IP), and then click Properties.
On the General tab, enter a static IP address that is not on the same subnet or network as another one of the public network adapters. An example of good IP addresses to use for the private adapters is 10.10.10.10 on node 1 and 10.10.10.11 on node 2 with a subnet mask of 255.0.0.0. If your public network uses the 10.x.x.x network and 255.0.0.0 subnet mask, use an alternate private network IP and subnet.
Make sure that there is no value set in the Default Gateway box.
Verify that there are no values defined in the Use the following DNS server addresses box.
Click Advanced.
On the DNS tab, verify that there are no values defined. Make sure that the Register this connection's addresses in DNS and Use this connection's DNS suffix in DNS registration check boxes are cleared.
On the WINS tab, verify that there are no values defined. Click Disable NetBIOS over TCP/IP.
When you close the dialog box, you may receive the following prompt. If you receive this prompt, click Yes: This connection has an empty primary WINS address. Do you want to continue?
Click OK to save your changes.
Complete the previous steps on all other nodes in the cluster.
For more information about the optimal network configuration for Windows server clusters, see "Server Clusters: Network Configuration Best Practices for Windows 2000 and Windows Server 2003" (https://go.microsoft.com/fwlink/?linkid=34304).
For more information about the correct cluster heartbeat configuration, see the Microsoft Knowledge Base article 258750, "Recommended Private 'Heartbeat' Configuration on a Cluster Server" (https://go.microsoft.com/fwlink/?linkid=3052&kbid=258750).