XCON: Configuring MTA TCP/IP Port # for X.400 and RPC ListensLast reviewed: February 13, 1998Article ID: Q161931 |
The information in this article applies to:
SUMMARYThe Microsoft Exchange Message Transfer Agent (MTA) in versions Microsoft Exchange Server 4.0 Service Pack 4 (SP4) and 5.0 contains two new features that allow the MTA to be configured to use different TCP/IP port numbers for X.400 connectors and for RPC listens.
MORE INFORMATIONBy default, the Microsoft Exchange MTA will use TCP/IP port 102 to communicate with other X.400 MTAs. For example, if two Microsoft Exchange Sites are connected by an X.400 Connector with a TCP/IP MTA Stack, both MTAs will communicate over port 102 by default. However, this port number is now configurable with the addition of the following registry value:
RFC1006 Port NumberThis case-sensitive registry value is a DWORD and does not exist by Default. To add the registry value: WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.
The other additional registry setting allows the MTA to be configured to listen to remote procedure calls (RPC) on a specific port number. It is not necessary for all Microsoft Exchange MTAs to be configured 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 directly achieved by going directly to the port number that the End-Point Mapper reported for a specific server. This behavior can be examined by using a network sniffer such as Network Monitor to monitor the RPC communication between two MTAs. The following registry value determines what TCP/IP port a given MTA will use to listen for RPC communication:
TCP/IP port for RPC listensThis case-sensitive registry value is a DWORD and does not exist by default. To add the registry value: WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. but can be added using regedt32 to the following registry key:
For more information about the ramifications and guidelines for static port assignment of Exchange services, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q180795 TITLE: XADM: Intrasite Directory Replication Fails with Error 1720These two new features are available in Microsoft Exchange Version 4.0 Service Pack 4 (SP4) and in Microsoft Exchange Version 5.0.
|
Additional query words: firewall
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |