XCLN: How to Force Static Mapping of SocketsLast reviewed: February 13, 1998Article ID: Q155831 |
The information in this article applies to:
SUMMARYThis article tells you how to allow the Microsoft Exchange Client to connect to Microsoft Exchange Server over an existing connection to the Internet and through a firewall. In order to do this, make the ports assigned to these connections static. This requires you to add entries to the registry.
MORE INFORMATIONThe computer must be restarted for these changes to take effect. To make the ports static: WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows NT. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
Further ExplanationA packet filter (or firewall) will deny connection attempts made to any port for which you have not explicitly allowed connections. Microsoft Exchange Server does use a well-known static port (port 135) to listen for client connects to the RPC Endpoint Mapper Service. However, after the client connects to this socket, Microsoft Exchange Server then re-assigns the client two random ports to use when communicating with the Directory and the Information Store. This makes it impossible to allow these through the firewall without forcing them to be statically assigned.
REFERENCESFor additional information, please refer to the Readme.wri file on the Microsoft Exchange Server version 4.0 compact disc.
|
Additional query words:
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |