Topic Last Modified: 2006-08-24

The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine the value for the msExchRoutingMasterDN attribute of each routing group in the current administrative group. The Exchange Server Analyzer then tries to open a socket connection to the routing master on TCP port 25. If the Exchange Server Analyzer does not receive an expected custom response of 25 Available, an error is displayed.

This error indicates that the routing master is not accessible on TCP port 25, and that routing failures may occur as a result. To correct this error, you can troubleshoot the connectivity problem with the routing master, or assign a new routing master.

To troubleshoot the connectivity problem with the routing master
  1. Can you telnet to port 25 from the routing master itself? If not, the problem is not with the network.

  2. Is everything plugged in? Is all your hardware functioning correctly?

  3. Is DNS working and configured correctly?

  4. Is your router functioning correctly?

  5. Are there any firewalls or applications preventing you from connecting?

To assign a new routing master
  1. Open Exchange System Manager

  2. Right-click the Organization Name (Exchange) icon at the top of the tree in the left pane (where Organization Name is the name that you selected for your Exchange 2000 organization), and then click Properties.

  3. Click Display administrative groups , click Display routing groups , and then click OK.

  4. Expand Administrative Groups, expand <AdministrativeGroup>, and then expand Routing Groups.

  5. Expand the routing group, and then click Members.

  6. In the right pane, right-click the Exchange computer that you want to configure as the routing group master, and then click Set as Master.

For more information about troubleshooting routing, configuring routing topologies, and advanced routing concepts, see "Troubleshooting Routing" in the Exchange Server 2003 Transport and Routing Guide (http://go.microsoft.com/fwlink/?LinkId=47579).