XCON: Microsoft Exchange will not Allow Incoming X.25 Connection

 Last reviewed: July 18, 1997
Article ID: Q157966
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SYMPTOMS

When the Microsoft Exchange Message Transfer Agent (MTA) receives an inbound X.25 connection, it mail refuse the connection due to an incorrect X.121 address even though the addresses match on both sides.

CAUSE

Microsoft Exchange Server version 4.0 improperly overwrites the inbound X.121 address field with the Incoming Facilities Data field and this causes the X.121 addresses not to match when a session attempt is made.

RESOLUTION

If the Facilities Call Data field does not have to be used, the field can be left blank and the inbound X.121 address will be unaffected.

STATUS

Microsoft has confirmed this to be a problem in version 4.0 of Microsoft Exchange. This problem was corrected in the latest Microsoft Exchange 4.0 Server U.S. 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: sp3 x25 eicon mci att
Keywords : XCON kbbug4.00 kbfix4.00.sp3
Version : 4.00
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: July 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.