YES I have Exchange 5.5 + Proxy working.
Try putting a hosts. file in the users c:\windows dir.
The problem is due to the Outlook client looking for EXCHANGE SERVER NAME
and you need to tell it the IP address.
All I did was write a hosts. file and put in EXCHANGESERVER
123.123.123.123. And it worked.
P.S try this without packet filtering first and then add PF if you need it.
Malcolm Joosse
Technical Director
Hotline Support Pty. Ltd. " Our Service is your Support "
malcolm@hotline.net.au
www.hotline.net.au
-----Original Message-----
From: Misha <misha@hern.org>
To: ntisp@emerald.iea.com <ntisp@emerald.iea.com>
Date: Thursday, 26 March 1998 19:43
Subject: PROXY 2.0/Exchange/Outlook problems
>I am having problems users trying to use Exchange services with Outlook
>from the external network and from remote locations.
>
>Proxy 2, packet filtering on, everything except for TCP/IP unbound from
>the external interface. Exchange server is on an invalid IP on the
>internal network. SMTP, POP3, NNTP clients work just fine from the
>outside, with ports 25, 110, 119 (and several others) of the Exchange
>server bound to the external interface of the Proxy server. Problem is
>external users need to access more than Internet mail and news, including
>Public Folders and address books.
>
>Using Outlooks Exchange Server service does not work at all. I know
>Exchange uses port 135 and 139, but I can only telnet to 135 on the
>external interface. 139 is rejecting connections, and I am not sure, but I
>have a feeling that the fact that the WINS client is unbound from the
>external NIC may have something to do with it.
>
>Has anyone gotten Exchange services for Outlook to work on the outside or
>is it just not possible?
>
>Misha
>IIS
>
>
> ----------------------------------------------------------
> NTISP Mailing List listserver@emerald.iea.com
>