Static IP addresses are recommended in a cluster

[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]  

Topic Last Modified: 2006-06-05

Microsoft® Exchange Server 2007 setup displayed this warning because one or more network interfaces are configured to use the Dynamic Host Configuration Protocol (DHCP).

It is a recommended best practice that static IP addresses be used for network interfaces managing client connections and heartbeat links in a Microsoft Windows server cluster. Using a dynamic configuration through DHCP is not recommended, as the failure to renew a DHCP lease could disrupt cluster operations.

To address this warning, configure each network interface managing client connections or heartbeat links to use a static IP address.

To Configure a Static IP address for a network connection

  1. On the Start menu, click Settings, and then Network Settings.

  2. Right-click the connection you want to configure, and then click Properties.

  3. On the General tab, in This connection uses the following items, click Internet Protocol (TCP/IP), and then click Properties.

  4. Click Use the following IP address, and in IP address, type the IP address.

  5. Click OK two times to finish.

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" (

For more information about the correct cluster heartbeat configuration, see Microsoft Knowledge Base article 258750, "Recommended private "Heartbeat" configuration on a cluster server" (