http://www.microsoft.com/technet/prodtechnol/exchange/exchange55/plan/ekmgem
.asp?frame=true
I think you will find a majority of us here don't really endorse the
OWA/DMZ scenario, as you end up having to punch so many holes in the FW that
it ends up essentially negating any security benefits
What would be the preferred method in here? Putting IIS on the exchange
server and running it in the private network?
_
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives:
Well, that's one option.
Another would be to setup a separate box with IIS and install OWA on it
inside the private network. Do the standard IIS hardening, etc, and you are
good to go.
I don't know how many users you are serving and what the usage would be,
but I have setup OWA for 100 user
That is my preferred method.
With Exchange5.5, OWA connects to Exchange using MAPI. MAPI by proxy if
you will. Putting the OWA server internal only requires opening port
443 for HTTP-SSL through to the OWA server.
W
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Yea baby!
-Original Message-
From: William Lefkovics [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 20, 2003 3:06 PM
To: Exchange Discussions
That is my preferred method.
With Exchange5.5, OWA connects to Exchange using MAPI. MAPI by proxy if
you will. Putting the OWA server
5 matches
Mail list logo
