The following information was taken from the Microsoft Support site Knowledge Base Article - 270836
XCCC: Exchange 2000 Static Port Mappings
The information in this article applies to:
· Microsoft Exchange 2000 Server
This article was previously published under Q270836
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 Description of the Microsoft Windows Registry
SUMMARY
This article descries how to enable Microsoft Exchange downlevel MAPI clients computers (either Exchange client computers or client computers that are using Microsoft Outlook in Corporate or Workgroup mode in Exchange 2000) to connect to Exchange 2000 over an existing connection to the Internet through a firewall.
If you are making these changes on an Exchange 2000 server that is installed onto a global catalog server, the steps in the following article must also be implemented. Click the article number below to view the article in the
Microsoft Knowledge Base:
298369 XADM: How to Configure a Global Catalog Server to Use a Specific Port When Servicing MAPI Clients
MORE INFORMATION
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.
To enable downlevel MAPI client computers to connect to Exchange 2000 over the Internet through a firewall, you must add entries to the registry to make the ports assigned to these connections static. To do this, follow these steps:
1.Start Registry Editor (Regedt32.exe).
2.Locate and click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters
3.Add the following entry for the Microsoft Exchange SA RFR Interface:
Name: TCP/IP Port
Value: REG_DWORD
Data Value: Port Number to assign
NOTE: Port assignments should be in the range 1024-5000 decimal. If you run the command NETSTAT -an from a command line, you can view all TCP/IP connections and listening ports in numerical format. You must use an unused port for the static mappings. E.g. I used ports 4997,4998 and 4999
4.Under the same key, add the following entry for the Microsoft Exchange Directory NSPI Proxy Interface:
Name: TCP/IP NSPI Port
Value: REG_DWORD
Data Value: Port number to assign
5.Locate and click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
6.Add the following entry for the Microsoft Exchange Information Store Interface:
Name: TCP/IP Port
Type: REG_DWORD
Data Value: Port number to assign
7.Quit Registry Editor.
8.Restart the computer for these changes to take effect.
After you have completed these steps, configure the packet filter (or firewall) to enable TCP connections to be made to these ports, as well as to port 135.
Hope this is of some use!
;-)
XCCC: Exchange 2000 Static Port Mappings
The information in this article applies to:
· Microsoft Exchange 2000 Server
This article was previously published under Q270836
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 Description of the Microsoft Windows Registry
SUMMARY
This article descries how to enable Microsoft Exchange downlevel MAPI clients computers (either Exchange client computers or client computers that are using Microsoft Outlook in Corporate or Workgroup mode in Exchange 2000) to connect to Exchange 2000 over an existing connection to the Internet through a firewall.
If you are making these changes on an Exchange 2000 server that is installed onto a global catalog server, the steps in the following article must also be implemented. Click the article number below to view the article in the
Microsoft Knowledge Base:
298369 XADM: How to Configure a Global Catalog Server to Use a Specific Port When Servicing MAPI Clients
MORE INFORMATION
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.
To enable downlevel MAPI client computers to connect to Exchange 2000 over the Internet through a firewall, you must add entries to the registry to make the ports assigned to these connections static. To do this, follow these steps:
1.Start Registry Editor (Regedt32.exe).
2.Locate and click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters
3.Add the following entry for the Microsoft Exchange SA RFR Interface:
Name: TCP/IP Port
Value: REG_DWORD
Data Value: Port Number to assign
NOTE: Port assignments should be in the range 1024-5000 decimal. If you run the command NETSTAT -an from a command line, you can view all TCP/IP connections and listening ports in numerical format. You must use an unused port for the static mappings. E.g. I used ports 4997,4998 and 4999
4.Under the same key, add the following entry for the Microsoft Exchange Directory NSPI Proxy Interface:
Name: TCP/IP NSPI Port
Value: REG_DWORD
Data Value: Port number to assign
5.Locate and click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
6.Add the following entry for the Microsoft Exchange Information Store Interface:
Name: TCP/IP Port
Type: REG_DWORD
Data Value: Port number to assign
7.Quit Registry Editor.
8.Restart the computer for these changes to take effect.
After you have completed these steps, configure the packet filter (or firewall) to enable TCP connections to be made to these ports, as well as to port 135.
Hope this is of some use!
;-)
