virajw2310
asked on
Exchange 2003 OWA over PIX 515
Hi
I need to provide OWA access to my roaming clients, they will be accessing published exchange probably a front-end server via a public network (via Internet). My exchange and ISA 2000 server is in "inside" interface of PIX 515, and using a TREND ISVW as my SMTP gateway which is in DMZ to forward all SMTP traffic to "inside" exchange server. But now all my roaming clients can not access WEBMAIL or OWA since there is no published server in our network. I was thinking having Front-End in "inside" network which will published over ISA, but our IT audit team is against to having connections to "inside" network. They are suggesting to use DMZ for WEB mail, but I am not convinced in their recommendation since there can loop poles as well. I hope exerts could help me in finding a solution to my requirement, as a option i can think of another web mail product but i was impressed with 2003 OWA interface. Please help me to find a proper solution without compromising security side of the network.
I need to provide OWA access to my roaming clients, they will be accessing published exchange probably a front-end server via a public network (via Internet). My exchange and ISA 2000 server is in "inside" interface of PIX 515, and using a TREND ISVW as my SMTP gateway which is in DMZ to forward all SMTP traffic to "inside" exchange server. But now all my roaming clients can not access WEBMAIL or OWA since there is no published server in our network. I was thinking having Front-End in "inside" network which will published over ISA, but our IT audit team is against to having connections to "inside" network. They are suggesting to use DMZ for WEB mail, but I am not convinced in their recommendation since there can loop poles as well. I hope exerts could help me in finding a solution to my requirement, as a option i can think of another web mail product but i was impressed with 2003 OWA interface. Please help me to find a proper solution without compromising security side of the network.
What do they mean by the "DMZ for WEBMAIL"? If they suggest to put a frond-end Exchange server in your DMZ, ask them to explain why they think this setup is more secure than putting an ISA server on the DMZ, on which you publish your OWA?
Keep in mind that a frond-end Exchange server (as any ohther Exchange server) is a domain member server in your AD and that it therefore requires access to that same AD. This means opening up ports between DMZ and internal network.
Should you place an ISA (or other reverse proxy server) in the DMZ, you can use a stand alone machine (no access to AD required), which publishes your OWA website. The reverse proxy server will point you to the Exchange server (if there is only on) or to the front-end Exchange server on your internal network. I believe this is a better practice than placing an Exchange FE on your DMZ.
And like Jim suggest above, use SSL instead of basic HTTP (either using a commercial certificate or by issuing your own - depending on the needs and policies of your company).
Cheers,
Kris
Keep in mind that a frond-end Exchange server (as any ohther Exchange server) is a domain member server in your AD and that it therefore requires access to that same AD. This means opening up ports between DMZ and internal network.
Should you place an ISA (or other reverse proxy server) in the DMZ, you can use a stand alone machine (no access to AD required), which publishes your OWA website. The reverse proxy server will point you to the Exchange server (if there is only on) or to the front-end Exchange server on your internal network. I believe this is a better practice than placing an Exchange FE on your DMZ.
And like Jim suggest above, use SSL instead of basic HTTP (either using a commercial certificate or by issuing your own - depending on the needs and policies of your company).
Cheers,
Kris
ASKER
Ganongj,
Thanks, but in your case where did you place your exchange and ISA? Even i would like to keep all servers inside network cos it will create more secure connection (I guess even we could filter our incoming traffic via ISA). And i would like to get some reference documents where i can refer before i do my installation.
Thanks
Viraj
Thanks, but in your case where did you place your exchange and ISA? Even i would like to keep all servers inside network cos it will create more secure connection (I guess even we could filter our incoming traffic via ISA). And i would like to get some reference documents where i can refer before i do my installation.
Thanks
Viraj
ASKER
Kris
I do agree with your point, but what is your advise in running ISA in "inside" and publish the OWA allowing HTTPS or SSL. But i am not sure how you could do this setup? Please advise accordingly.
Thanks
Viraj
I do agree with your point, but what is your advise in running ISA in "inside" and publish the OWA allowing HTTPS or SSL. But i am not sure how you could do this setup? Please advise accordingly.
Thanks
Viraj
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I had the same issue, I went with purchasing a certificate from Verisign and making OWA accessible through https. This is port 443 with very secure communications. Your audit team should see this as being ok.
Regards,
Jim