SMTP: Troubleshooting the TCP/IP Layer of the Mail Gateway

Last reviewed: October 20, 1997
Article ID: Q115492

3.00 MS-DOS kb3rdparty

The information in this article applies to:

Microsoft Mail Gateway to SMTP, version 3.0

SUMMARY

If the SMTP gateway cannot connect to the mail routing host or receive incoming mail, the TCP/IP layer may not be working properly. This article describes how to troubleshoot the IP and TCP layers.

Testing the IP Layer

To test the IP layer, use the PING command from the gateway PC up to the host and from the host down to the gateway PC:

Test the network adapter with the loopback IP address:
```
      ping 127.0.0.1
```
If this test fails then the problem is related to the NIC.
Test the connection on the local subnet:
```
      ping <ip address>
```
where <ip address> is the IP address of a host on the same subnetwork. If this fails then the subnet mask is configured incorrectly.
Test the connection to the default gateway:
```
      ping <gateway ip address>
```
where <gateway ip address> is the IP address of the default gateway, also known as a router. If this test fails then we have an incorrect IP address for the default gateway, or the gateway is down.
Test the connection to a remote subnet:
```
      ping <remote ip address>
```
where <remote ip address> is the IP address of a host on another subnet. If this fails, then the connectivity problem is most likely on the remote side.
Test the DNS name resolution:
```
      ping <host.domain>
```
where <host.domain> is something like smarthost.microsoft.com If this fails then either the DNS entry in the TCP/IP configuration is incorrect or the DNS server is having problems providing name service at this time.

If this works, you receive a response indicating how many packets were bounced off the destination host. Successful completion of these commands means the IP layer is working correctly.

Testing the TCP Layer

To test the TCP layer, use the TELNET command with a "25" after the host ID or IP address to specify the mail socket. Run it from the gateway PC up to the host and from the host down to the gateway PC:

   telnet tcpiphost.company.com 25
   telnet msmailgwy.company.com 25

   NOTE: You can't run the second command unless the gateway is running.

If this succeeds, you receive the response "220 ...." from the destination host. Type QUIT to end the test. Successful completion means the TCP layer is working.

   NOTE: If you use -cd (debug) and -lacsy (full logging) the 220
   response is recorded in the LOG file.

Additional reference words: 3.00 errors
KBCategory: kb3rdparty
KBSubcategory: MailGWSMTP
Keywords : MailGWSMTP kb3rdparty
Version : 3.00
Platform : MS-DOS

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.

Last reviewed: October 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.