Microsoft KB Archive/178532

= XFOR: Configuring Exchange Internet Protocols with Proxy Server =

Article ID: 178532

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Exchange Server 5.0 Standard Edition
 * Microsoft Exchange Server 5.5 Standard Edition
 * Microsoft Proxy Server 2.0 Standard Edition

-



This article was previously published under Q178532



SUMMARY
The Microsoft Exchange Internet protocols can be configured to allow Internet clients to connect to the Microsoft Exchange Server information store through Microsoft Proxy Server version 2.0. Microsoft Exchange Server requires the addition of a configuration file, .ini, and installation of WinSock Proxy Client in order to work with Proxy Server 2.0. This is not necessary if Microsoft Proxy Server 2.0 is installed on the Microsoft Exchange Server.



MORE INFORMATION
WinSock Proxy Client allows you to bind any Internet protocol to the external network interface of Microsoft Proxy Server. After the Internet protocol is bound to the external network interface, it is available to clients outside the proxy server. The proxy server then monitors for connections on behalf of the information store.

When the configuration file is properly added and the appropriate Exchange service is restarted, the Exchange Server computer binds to the appropriate port on the network interface of the proxy server. This is easily verified by telnet to the respective port of the proxy server.

The respective ports are as follows:   POP3: 110, 995 for Secure POP3 (SSL) IMAP4: 143, 993 for Secure IMAP4 (SSL) LDAP: 389, 636 for Secure LDAP (SSL) NNTP: 119, 563 for Secure NNTP (SSL) Configuration is as follows:  Install and configure Microsoft Proxy Server. Install and test the WinSock Proxy (WSP) client on the Exchange Server computer by running a WinSock client application.

NOTE: The ping command, ICMP packets, is not passed by the proxy server. Use telnet or ftp.  Create a second Wspcfg.ini file for the Exchange store (Store.exe). Add the information below to this Wspcfg.ini file and place the file in the directory where Store.exe is located, typically Exchsrvr\Bin.

[STORE] ServerBindTcpPorts=(Appropriate port for protocol used, multiple                          protocols can be configured) Persistent=1 KillOldSession=1

Sample .ini entry for LDAP appears as follows:

[DSAMAIN] ServerBindTcpPorts=389 (636 for Secure) Persistent=1 KillOldSession=1  If dynamic packet filtering is enabled (recommended), the proxy server dynamically opens all necessary ports when they are requested. No special configuration is needed. Stop and restart the Exchange information store (or directory for LDAP). You should now be able to contact the Exchange Server computer by connecting to the proxy server's Internet IP address using an Internet client.</li></ol>

NOTE: In order to bind to Secure Sockets Layer (SSL) ports, you must use the ProxyBindIP= statement in addition to the other entries. Without such a statement the Exchange Server computer will not bind to the proxy server properly, and thus not allow secure passage of messages through the Proxy server using SSL.

Additional query words: XIMS XADM XGEN IIS PROXY NNTP IMAP4 POP3 LDAP TCPIP

Keywords: kbhowto KB178532

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.