DOCUMENT:Q295416 06-AUG-2002 [exchange] TITLE :XCON: How to Use the PortPing Utility PRODUCT :Microsoft Exchange PROD/VER::5.5 OPER/SYS: KEYWORDS:kberrmsg ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Exchange Server, version 5.5 - Microsoft Exchange 2000 Enterprise Server ------------------------------------------------------------------------------- SUMMARY ======= This article describes the PortPing utility that is located in the Microsoft BackOffice Resource Kit. MORE INFORMATION ================ You can use PortPing to verify that a computer is actively listening on a specific port. For example, you can use PortPing to verify that your server is listening on port 25 when you install an Internet Mail Connector on your Exchange Server computer, and then start the Internet Mail Service. When you use PortPing, you can type either the host name of the server or the Internet protocol (IP) address in the Target Server box. If you type the host name and PortPing fails, type the IP address. If you can reach the specified port when you type the IP address, but not when you type the host name, the name resolution service on the computer may not be working properly. When you run PortPing, if the remote port is listening, you receive the following message: Success! Pinged port x in y milliseconds. However, if the remote port is not open or if a firewall is blocking that particular port, you receive the following error message: Error Detected: Connection refused returned. In this error message, represents the error code. For additional information about the error code that you receive when you run PortPing, click the article number below to view the article in the Microsoft Knowledge Base: Q150537 Windows Sockets Error Codes, Values, and Meanings The following scenario describes how to use this information for troubleshooting purposes: Messages are backed up between two Exchange Server computers that are connected by an X.400 connector. The X.400 connector uses Transmission Control Protocol (TCP) port 102. To confirm that this issue is caused by network problems, run PortPing to that port number. When you start PortPing to make a remote call on the server to port 102, if the ping command does not come back successfully to port 102, you can confirm that X.400 mail traffic is not flowing. Additional query words: ====================================================================== Keywords : kberrmsg Technology : kbExchangeSearch kbExchange550 kbZNotKeyword2 kbExchange2000Search kbExchange2000EntServ Version : :5.5 Issue type : kbinfo ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 2002.