Maintenance and Troubleshooting << >>

X.400 Connections

Connecting to other X.400 systems must be done carefully. Configuration varies depending on which type of X.400 system you are connecting to and the method you use. Common problems are related to incorrect configuration.

An address is missing or incorrect.

Reasons Actions
The address space is defined incorrectly. Use the Administrator program to check address space definitions.
Custom recipients have incorrect e-mail names in Microsoft Exchange Server. Create custom recipients with valid e-mail names or update the names of existing custom recipients.

Messages across an X.400 backbone lose rich text format.

Reason Action
The Microsoft Exchange Server MTA is not configured to pass Transport-Neutral Encapsulation Format (TNEF) information. Use the Administrator program to change the MTA configuration.

The Microsoft Exchange Server MTA can't connect to an X.400 MTA.

Reasons Actions
You are using different network stacks. Use a common stack.
The MTA name or password does not match the password used in the configuration. Verify the MTA passwords and configuration. Passwords are usually case-sensitive.
The network connection is down. Check the network connection. Find the network problem and fix it.

Unwanted binary attachments are being sent to an X.400 MTA.

Reason Action
The Microsoft Exchange Server MTA is configured to pass TNEF information. Disable TNEF in the X.400 Connector General property page.

Messaging fails when changing MTA conformance on X.400 Connectors.

Reason Action
Messages are either returned as NDRs or are lost. Verify that the MTA conformance option found in the X.400 Connector's Advanced property page matches what is used by the Microsoft Exchange Server or X.400 system at the other end of the connection. If a change is made, restart all the services on both servers. This will re-encode any messages in the queue waiting to be transmitted.