Port did not respond

[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: 2006-05-16

The Microsoft® Exchange Server Analyzer Tool queries the user-defined server and tries to open a socket connection to the specified server on the default configuration of TCP port 25 or a user-defined port. If the Exchange Server Analyzer does not receive an expected custom response of xx Available, where xx is the default port of 25 or the alternative port number defined by the user, the Exchange Server Analyzer displays an error.

This error indicates that the server cannot be accessed on the desired TCP port and that failures may occur. To correct this error, you can troubleshoot the connectivity problem with the server.

To troubleshoot the connectivity problem with the server

  1. Can you telnet to the desired port from the designated server 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 preventing you from connecting?

For more information about how to troubleshoot server connectivity issues, see "Microsoft Exchange Server Best Practices Analyzer Tool Troubleshooting Connectivity Problems" (http://go.microsoft.com/fwlink/?LinkId=56285).