Exchange Server 5.5 behind ISA _UPDATE

I got a lot of different response.  Here is the configuration

Proxy Server 2.0
Exchange Server 5.5 with SP4 behind Proxy Server.
OWA working and the IIS for OWA located on a third Server.
Two-Way trust with one other domain that uses our Exchange Server.
Public IP address assigned to Proxy with Firewall Up.

Now - I modified exchange server per the following, respectfully thanking
the guys at proxyfaq.networkgods.com although they are no longer maintaing
the FAQ.

Here is what I did on MSP 2.0 and Exch 5.5 for Exchange Server 5.5
SMTP/POP3/ (Located behind the Proxy)

*Note: The Exchange server is treated just like any other client behind
the proxy server.  It does not need to be configured with a valid Internet
Address.

The Winsock Proxy properties for client configuration is set to ?IP
Address?

The Winsock service is running and the Exchange server has the WSP client
installed

At least one address of an Internet DNS server is defined in the DNS
settings of the Exchange Server?s Network TCP/IP settings (configured in
the network control panel)

For SMTP the following is in wspcfg.ini file where the Msexcimc.exe file
is located.

[MSEXCIMC]
ServerBindTcpPorts=25
Persistent=1
KillOldSession=1
 
For POP3, NNTP, IMAP4 the following in wspcfg.ini file where the Store.exe
file is located.

[STORE]
ServerBindTcpPorts=110,119,143
Persistent=1
KillOldSession=1

The following ports correspond to the following services 

110=Pop3   119=NNTP   143=IMAP4

We do not use LDAP or Chat.  Our ISP hosts our DNS and has an an A and MX
recorded added for us which points to the external IP address of the Proxy
Server.

NOW THANKS FOR READING ALL THAT!

I hope that if I just upgrade the Proxy Server to ISA everything should
work - but what about the winsock proxy client (for MSP) and installed on
the Exchange Server?

I will approach this so conservatively - Will Clone the existing MSP
Server and upgrade it then test.

Any suggestions before I give up one Sunday working on all this???

Regards,
Don Coleman, MCSE
dcoleman@xxxxxxxxxx

Other related posts: