Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/169159

From BetaArchive Wiki
Knowledge Base


X.400 connector configuration checklist

Article ID: 169159

Article Last Modified on 4/10/2007



APPLIES TO

  • Microsoft Exchange Server 4.0 Standard Edition
  • Microsoft Exchange Server 5.0 Standard Edition
  • Microsoft Exchange Server 5.5 Standard Edition



This article was previously published under Q169159

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry


SUMMARY

The following checklist is intended to help you configure X.400 connectivity between servers that are running Microsoft Exchange Server, or between an Exchange Server server and a third-party X.400 message handling system.

This checklist is not intended to replace observations that you might make on previously operational connections that may point to the actual problem. Instead, this checklist is intended to help you set up a successful configuration between message transfer agents (MTAs).

Note In this article, the term "server" refers to a server that is running on Microsoft Windows NT that has Microsoft Exchange Server Enterprise Edition or Microsoft Exchange Server Standard Edition with the X.400 connector installed. Alternatively, the term "server" refers to a computer that is running a third-party X.400 message handling system.

MORE INFORMATION

To verify connectivity between two MTAs, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

  1. Verify that each host can ping the IP address of the other.
    • If each host cannot ping the IP address of the other, resolve the network issue.
    • If each host can ping the IP address of the other, decide whether you want to use the host name instead of the IP address. If you want to do this, go to step 2. Otherwise, go to step 3.
  2. If you want to use the host name instead of the IP address of the target MTA, ping the host name.

    Note The domain name system (DNS) supports host name resolution. Alternatively, a "hosts" file may be used. The "hosts" file for computers that are running Microsoft Windows NT Server is located in the following folder:

    winntdir\System32\Drivers\Etc

    The format for this file is as follows:

    IP address, TAB, host name

    Determine whether the host name returned an IP address.

    • If the host name did not return an IP address, resolve the problem with name resolution.
    • If the host name returned an IP address, go to step 3.
  3. Configure the Exchange Server MTA to support a 2K transport protocol data unit (TPDU). To do this, start the Windows NT Registry Editor, and then move to the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \MSExchangeMTA\Parameters

    Find the Supports 2K TPDU registry value, set the type to DWORD, and then change the value to 0x1 (1 hexadecimal).
  4. Verify that the administrators who want to configure a given MTA record have the following information for the MTA to which they want to connect:
    • Remote host name

      This entry is case sensitive, and it cannot be longer than 32 characters. On an Exchange Server server, the remote MTA name is specified on the General tab of the Exchange Server X.400 connector.
    • Remote MTA password

      This entry is case sensitive, and it cannot be longer than 64 characters. On an Exchange Server server, the remote MTA password is specified on the General tab of the Exchange Server X.400 connector. For the simplest configuration, select the default settings. When you do this, the "no password" setting is set.
    • T selector

      This value is optional. On an Exchange Server server, this value is specified in the Outgoing OSI address information on the Stack tab. This value cannot be longer than 32 text characters or 64 hexadecimal characters.

      This value is very important, and it must match the corresponding value that is specified in the configuration for the MTA on the other host. This value is used for the T selector that is specified on the Stack tab of the Exchange Server X.400 connector.

      If the remote administrator wants to specify an S selector or a P selector, the remote administrator should do this after successful messaging is established. The selector that is supported in the X.400 link options depends on the mode of the MTA, as follows:
      • 1988 mode supports a T, an S, and a P selector.
      • 1984 modes support only a T selector.
  5. On an Exchange Server server, use the Override tab to specify the local MTA and the password. The Exchange Server MTA uses the name of the computer that is running Windows NT Server on which Exchange Server is installed for the MTA name.

    Note If no incoming password is necessary, you do not have to use the Override tab. In this case, to use a password is redundant because the T selector provides sufficient security.
  6. Use the Connected Sites tab to configure the address space that will be associated with a target Exchange Server server.

    Use the Address Space tab only on an Exchange Server server that connects to a third-party MTA. The administrator of the third-party MTA provides the X.400 address that is associated with the third-party MTA. Alternatively, the administrator requests that you specify a wildcard (*) character for the Country code in the address space that is configured on the Address tab of the Exchange Server X.400 connector.

    When you use the wildcard character in the address space, a match is found for all X.400 recipients who are not local to the Exchange Server server.
  7. Configure the information on the Advanced tab of the Exchange Server X.400 connector to match the mode of the third-party MTA. The X.400 Allow MS Exchange contents link option should always be disabled when you connect to a third-party MTA.

    Note To locate this option, click Help on the Advanced tab.

    Typically, third-party MTAs require that the Two way alternate option be disabled. The Allow BP-15 (in addition to BP-14) option is available when a message is sent to a 1984 X.410 third-party MTA or to a 1988 mode third-party MTA.
  8. Create a custom recipient on both hosts. Alternatively, send a message to a user on the third-party host by using a one-off address in the To line.

    An example of a one-off address is as follows:

    [x400:c=us;a=attmail;p=organization;o=locale;s=lastname;g=firstname]

  9. If the test in step 8 fails in either direction, follow these steps:
    1. In the Exchange Server Administrator program, select the server object, and then click Properties on the File menu.
    2. Click the Diagnostics Logging tab, and then increase the MSExchangeMTA X.400 Interoperability and APDU logging settings to Maximum.

      When you do this, you enable logging to the Bf0.log file, to the Ev0.log file, and to the Ap0.log file in the Mtadata folder.
  10. Repeat the test in step 8.

    If you still need help, contact Microsoft Customer Support Services (CSS). To do this, visit the following Microsoft Web site:



Additional query words: X.400 isocor emx retix mailbus foreign exfaqcon XCON

Keywords: kbexpertiseadvanced kbhowto kbsetup kbtshoot KB169159