XADM: TNS Resolution Causes Buffer Overflow

 Last reviewed: April 15, 1997
Article ID: Q157691
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SYMPTOMS

Federal sites needing to use Tactical Name Service (TNS) instead of Domain Name Service (DNS), will encounter the following issue. When Microsoft Exchange looks to connect to another SMTP server, it queries the TNS for an MX Record (SMTP address). If the address is present, everything works fine. If the address is not present, the TNS server sends its own IP address. If the Server hardware is an old UNIX computer, with a total input buffer of 200k, the Microsoft Exchange mail headers will cause a buffer overflow.

MORE INFORMATION

Basic TNS information:

  1. It is run on a special version of UNIX that the U.S. ARMY developed.
2. It includes only 1 zone. 3. It only listens on one IP address. 4. It dynamically registers hosts. 5. It does not support MX priority/preference values. 6. It does not support SOA records.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

Additional query words:
Keywords : kbbug4.00 kbfix4.00.sp3 kbusage XADM
Version : 4.0
Platform : WINDOWS

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: April 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.