Possible gateway problem

[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-08-09

The Microsoft® Exchange Server Analyzer Tool sends a test message to a user-defined external account from the server that is running Exchange Server. The Exchange Server Analyzer then scans the message tracking logs of the server to determine whether any issues were found with the delivery of the test message.

As a part of this scan, the Exchange Server Analyzer queries the EntryType property for the Exchange_MessageTrackingEntry Microsoft Windows® Management Instrumentation (WMI) class under the root\MicrosoftExchangeV2 namespace to determine why one or more message tracking log entries were created.

The Exchange Server Analyzer displays an error if the following conditions are true:

  • The message tracking log can be scanned successfully.

  • The test message did not successfully transfer out of the queue.

  • A non-delivery report (NDR) was not generated.

  • A value of 1034 exists for the EntryType property.

  • The message reached the specified local Exchange outbound gateway server.

This error may indicate that there is a connection problem between the user-specified local Exchange outbound gateway server and the remote server.

To resolve this error, use the NSlookup utility to review possible issues with Domain Name System (DNS) resolution. For connection and protocol issues such as Host unreachable errors, use Telnet.exe to try to connect to the destination computer. To troubleshoot protocol errors, increase diagnostic logging for the MSExchangeTransport service for the Simple Mail Transfer Protocol (SMTP) component, and review the logs for errors. Alternatively, you can use the Network Monitor (Netmon.exe) tool to obtain information about network connection errors.

For more information about how to modify logging settings, see "How to Modify Logging Settings for MSExchangeTransport" in the "Troubleshooting Mail Flow and SMTP" section of the Exchange Server Transport and Routing Guide (http://go.microsoft.com/fwlink/?LinkId=47579).

For more information about how to troubleshoot SMTP queues, see the following Exchange resources: