|Component:||Microsoft Exchange Message Transfer Agent|
|Message:||The message transfer gateway that uses the network address <address> and the transport stack <text> could not be found. Check the configuration of the mail gateway. [<value> <value> <value> <value>] (10)|
This event relates to an X.400 connector. It is most frequently seen in a mixed Exchange 2000 – Exchange 5.5 organization. It can happen on both the Exchange 2000 and Exchange 5.5 servers.
On an Exchange 2000 Server, you will receive a set of phrases in the Event Description that is similar to the following:
The message transfer gateway that uses the network address [HEX NO. FOR IP ADDRESS] and the transport stack CN=TCP SERVERNAME,CN=MICROSOFT MTA,CN=SERVERNAME,CN=SERVERS,CN=NAO,CN=ADMINISTRATIVE GROUPS,CN=AGNAME,CN=MICROSOFT EXCHANGE,CN=SERVICES,CN=CONFIGURATION,DC=DCNAME,DC=COM could not be found. Check the configuration of the mail gateway. [BASE IL TCP/IP DRVR 11 256] (10)
This should be differentiated from the appearance of the description on an Exchange 5.5 server. On an Exchange 5.5 Server, you will receive a set of phrases in the Event Description that is similar to the following:
The message transfer gateway that uses the network address 91F5C11B and the transport stack /o=Org/ou=Site/cn=Configuration/cn=Servers/cn=LocalMTA/cn=TCP (LocalMTA) could not be found. Check the configuration of the mail gateway. [BASE IL TCP/IP DRVR 8 218] (10)
Exchange 2000 is connected to another server through an X.400 connector. The remote server is trying to connect with the local Exchange server. When a connection is negotiated in X.400, the IP address and MTA Name is passed. Both of these are compared to the MTA Stack of existing connectors. If they do not match, a reverse lookup is performed for the Fully Qualified Domain Names (FQDN) and compared again. If both fail the MTA refuses the connection.
The X.400 connectors may be configured with FQDN, rather than IP address or NetBIOS names. The MTA that has logged the errors is unable to resolve the IP address of the incoming connection to an FQDN, in order to locate the X.400 connector for the remote MTA.
When the remote MTA initiates the connection, it supplies its own IP address in the frame. The receiving MTA compares this address with the Address field on each of its X.400 Connector Property pages, in order to find the connector responsible for this connection. If none of the connectors has this address, the MTA logs the first 9301 event.
Besides being configured with FQDN instead of IP addresses, an X.400 connector may be referencing a deleted server. In this case, we would have a connecter to a non-existent server as the cause of the event.
Another known cause is using the IP address rather than the FQDN on the X.400 connector, but entering the wrong IP address.
In an environment where DNS is used for name resolution, X.400 connectors are configured with an FQDN rather than NetBIOS name or IP address. The MTA must therefore be able to make a successful DNS reverse lookup in order to find the correct X.400 connector and accept the connection request.
In order for the reverse lookup to be successful, the DNS server must have a PTR record for the remote server that maps its IP address to its FQDN.
If using an IP address rather than a FQDN, the reverse lookup procedure is bypassed.
If you are already using IP addresses rather than FQDN, check to make sure the correct IP address has been entered on the X.400 connector.
Ensure that the X.400 connector is not referencing a server which has been deleted.