Microsoft KB Archive/325564

From BetaArchive Wiki
Knowledge Base


XCON: RPC Communication Does Not Work as Expected After You Install Exchange Server 5.5 SP4

Article ID: 325564

Article Last Modified on 10/28/2006



APPLIES TO

  • Microsoft Exchange Server 5.5 Service Pack 4



This article was previously published under Q325564


SYMPTOMS

Remote procedure call (RPC) communication is affected, and mail backs up in the queue, if the following conditions are true:

  • The Exchange Server computer and Exchange Server cluster are separated by the network address translation (NAT) service.
  • The Exchange Server computer and Exchange Server cluster are within a site or in different sites that are connected with site connectors.
  • The communication occurs between an Exchange Server computer and an Exchange Server cluster.


-or-

  • The communication occurs between two Exchange Server computers, neither of which is in a cluster.

The message transfer agent (MTA) may log the event ID 9318 message with error code 1722s on both servers within a site or on both ends of the site connector. The MTA may also log the event ID 9322 message with error code 1722 on one or both ends of the site connector.

NOTE: This issue may occur if you upgrade from Exchange Server 5.5 Service Pack 3 (SP3) to Exchange Server SP4.

CAUSE

In the current implementation of MTA core code, NAT is not supported in RPC communication in the cluster and non-cluster server scenarios that are listed in the "Symptoms" section.

This issue occurs because of design changes to Bind and bind_back strings in the MTA core code. Before MTA build 2651.75, MTA used IP addresses to bind_back. After MTA build 2651.75, MTA uses fully qualified domain names (FQDNs). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

251318 XCON: Message Transfer Agent Uses Node IP Address Instead of Cluster IP Address


WORKAROUND

To work around this issue, turn off the NAT service. For Exchange Server computer or clusters that are connected with site connectors, create an X400 connector, and then configure the address. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

197378 XCON: MTA Generates 9301 Events on Incoming Connections


Keywords: kbprb KB325564