There is more than one network between the Active Directory server and this Exchange server
[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 http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool queries the WIN32_PingStatus Microsoft Windows® Management Instrumentation (WMI) class in the root\cimv2 namespace to determine the value for the RouteRecord key. The RouteRecord key contains a record of intermediate hops (for example, the number of routers) between the Exchange server and the domain controller. The Exchange Server Analyzer takes a count of the number of routers listed in the RouteRecord key. If the Exchange Server Analyzer finds more than one router is listed, an error is displayed.
An optimal Active Directory® directory service is one that the design ensures that the Exchange Server computer can communicate with a domain controller or global catalog server on its subnet. This error indicates that the Exchange Server computer is communicating with domain controllers on networks that are more than one hop away.
To correct this error
Check your network topology and re-evaluate the placement of Active Directory servers.
Monitor the event logs on the Exchange Server and the domain controller to see if any network-related events have been logged that indicate potential problems.
Investigate the Active Directory site design. If your network is not partitioned according to this specification, consider partitioning the network into more Active Directory sites.
For more details about the Win32_PingStatus WMI class, see the MSDN article, "Win32_PingStatus" (http://go.microsoft.com/fwlink/?linkid=33549).
For more information about Active Directory site design, see "Designing the Site Topology" (http://go.microsoft.com/fwlink/?linkid=33551).