

This static CD-based web site is representative of the www.microsoft.com/y2k site as of September 15th, 1999.

XCON: MTA Generates 9301 Events on Incoming Connections

The information in this article applies to:

Microsoft Exchange Server, version 5.5 Service Pack 1

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

The Microsoft Exchange Server message transfer agent (MTA) will generate Event ID 9301 when receiving an incoming connection from a multihomed server.

CAUSE

The MTA depends on the selection of the Virtual Server IP address by the transport when making an outside connection. The server being contacted will only have one IP address or one server name defined for X.400 connectors. Any incoming connections that do not match the list of IP addresses or server names will generate the 9301 Event ID.

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For more information, please see the following article in the Microsoft Knowledge Base:

Q191014 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack

The English version of this fix should have the following file attributes or later:

Component: Message Transfer Agent (MTA)

   File Name      Version
   -------------------------
   Dbserver.sch   5.5.2431.0
   Dcprods.cat    5.5.2431.0
   Ems_rid.dll    5.5.2431.0
   Emsmta.exe     5.5.2431.0
   Info4log.cfg   5.5.2431.0
   Infodlog.cfg   5.5.2431.0
   Infollog.cfg   5.5.2431.0
   Infotlog.cfg   5.5.2431.0
   Mtacheck.exe   5.5.2431.0
   Mtamsg.dll     5.5.2431.0
   P2.xv2         5.5.2431.0
   X400om.dll     5.5.2431.0
   X400omv1.dll   5.5.2431.0

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5 Service Pack 1. This problem was first corrected in Exchange Server 5.5 Service Pack 2.

MORE INFORMATION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

After installing the updated version of the MTA, the functionality is initiated by creating a new key name with the link's Relative Distinguished Name (RDN), and add a new value.

WARNING: Using the raw mode of the Exchange Server Administrator program (admin/r) incorrectly can cause serious problems that may require you to reinstall Microsoft Windows NT Server and/or Microsoft Exchange Server. Microsoft cannot guarantee that problems resulting from the incorrect use of raw mode can be solved. Use raw mode at your own risk.

To find the links RDN:

Start the Exchange Server Administrator program in Raw mode by typing the following at a command prompt:
c:\exchsrvr\bin\admin /r

Double-click on Site, then Configuration, then Connectors, and on the right side, select the X.400 Connector. On the File menu, select Raw Properties to open the X.400 Connector raw properties.

In the Object Attribute column, select Obj-Dist-Name, and in the Attribute value box, scroll to the right until you locate the last "\cn=" value. This will be the RDN that you use to create the registry key name.

Start Regedt32.exe and create the registry key name using the RDN of "TCP to MTA B" as in the following example:
```
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMTA
   \Parameters\TCP to MTA B 
```

Under the new registry key name, create a new string registry value called "Stack IP Address Override" that must be configured under the registry key named after the Link RDN (for example: "MSExchangeMTA\Parameters\TCP to MTA B\"Stack IP Address Override").

The string value of the key will be the IP address the MTA will use when creating outgoing connections, and is configured in standard dot notation, for example: 1.23.45.67. This IP address is used as the From IP address used when sending outbound connections, and therefore allows only one particular IP address on the multi-homed host to be used for the given connector.

You must then configure all connectors attaching to the multihomed server to use this address.

The MTA will still listen with the bind set to any incoming socket, so inbound connections to any IP address on the computer will be picked up.

Keywords          : exc55sp2fix 
Version           : WinNT:5.5 SP1
Platform          : winnt 
Issue type        : kbbug