Exchange cluster node could not be contacted

[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: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool queries the Win32_Service Microsoft Windows® Management Instrumentation (WMI) class to determine the value of the Started key for the Cluster service (ClusSvc). A value of True indicates the Cluster service is started and a value of False indicates the Cluster service is not running.

The Exchange Server Analyzer also reads the following registry entry to determine the version of Windows that is running on the Exchange Server computer:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\CurrentVersion

A CurrentVersion value of 4.0 indicates the computer is running Microsoft Windows NT® Server 4.0. A value of 5.0 indicates the computer is running Windows 2000 Server, and a value of 5.2 indicates the computer is running Windows Server™ 2003.

If the Exchange Server Analyzer cannot determine the version of Windows running in the cluster, or if the Exchange Server Analyzer cannot determine whether the Cluster service is running, an error is displayed. This error indicates that the Exchange Server Analyzer could not contact a node in an Exchange Server cluster.

To correct this error

  1. Ensure that the Exchange Server computer has been started and is connected to the network.

  2. Use the ping command to see if the Exchange Server computer is reachable.

  3. If there is a firewall in place, check to see if remote procedure call (RPC) ports are blocked.

  4. Ensure that the Remote Registry service on the Exchange Server computer has been started.

  5. Check the permissions for the account under which the Exchange Server Analyzer is running to ensure that the account has sufficient permissions to read the registry on the Exchange Server computer.

For more information about troubleshooting network connectivity problems, see the Microsoft Knowledge Base article 325487, "How to troubleshoot network connectivity problems" (