XFOR: X.400 Connection to ISOCOR MTA Is Closed with No Messages Sent--Event ID 668 (281744)
The information in this article applies to:
- Microsoft Exchange 2000 Enterprise Server
This article was previously published under Q281744 SYMPTOMS
An Exchange 2000 X.400 connection attempt to an ISOCOR X.400 mail system may not work, resulting in no message transfers. You may see Exchange 2000 message transfer agent (MTA) logging event ID 668 in the event log.
CAUSE
To set up an X.400 connection, the Exchange 2000 MTA tries to "bind" to the other X.400 MTA (in this case, ISOCOR). ISOCOR echoes back the Exchange 2000-specific information it receives with the bind request in its bind response. This causes the Exchange 2000 MTA to assume that the other MTA is an Exchange 2000 MTA. It then sends a system message that contains routing information to the ISOCOR X.400 MTA. This message represents the Link State Table information that is used inside the Exchange 2000 organization, and which should not be sent outside. ISOCOR cannot manage such messages.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:
Component: MTA
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.
| Modification Type: | Minor | Last Reviewed: | 7/12/2005 |
|---|
| Keywords: | kbbug kbfix kbQFE KB281744 |
|---|
|