Select the product you need help with
XCON: Configuring MTA TCP/IP Port # for X.400 and RPC ListensArticle ID: 161931 - View products that this article applies to. This article was previously published under Q161931 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
SUMMARY
The message transfer agent (MTA) in Exchange Server version 4.0 Service Pack 4 (SP4), 5.0, and 5.5, and Exchange 2000 Server in mixed mode contains two features
that allow you to configure the MTA to use different Transmission Control Protocol/Internet Protocol (TCP/IP) port numbers
for X.400 Connectors and for remote procedure call (RPC) listening. NOTE: The information in this article only applies to Exchange 2000 in mixed mode. If Exchange 2000 is running in native mode, this information does not apply. MORE INFORMATION
By default, the Exchange Server MTA uses TCP/IP port 102 to
communicate with other X.400 MTAs. For example, if two Exchange Server
sites are connected by an X.400 Connector with a TCP/IP MTA stack, both
MTAs communicate over port 102 by default. However, you can configure this port number if you add the following registry value:
RFC1006 Port Number
This case-sensitive registry value is a DWORD value type, and does not exist by
default. To add the registry value:WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
An additional registry setting allows you to configure the MTA to listen to RPCs on a specific port number. You do not need to configure all of the Exchange Server MTAs to listen for RPC communication on the same port. RPC communication relies on the end-point mapper to relay the appropriate port number, so that further communication can then be achieved by going directly to the port number that the end-point mapper reports for a specific server. You can examine this behavior by using a network sniffer such as Network Monitor to monitor the RPC communication between two MTAs. The following registry value determines the TCP/IP port that a given MTA uses to listen for RPC communication: TCP/IP port for RPC listens
This case-sensitive registry value is a DWORD value-type and does not exist by
default. To add the registry value:
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
For additional information about the ramifications and guidelines for staticport assignment of Exchange services, click the article number below to view the article in the Microsoft Knowledge Base: 180795
These two features are available in Exchange Server version 4.0
Service Pack 4 and in Exchange Server version 5.0.
(http://support.microsoft.com/kb/180795/EN-US/
)
XADM: Intrasite Directory Replication Fails with Error 1720
Properties |


Back to the top








