- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsI am deliberating, debating, and looking for a solution to allow public access to Outlook Web Access (OWA) for our company. I would like to accomplish a high level of security, by use of existing resources, minimize expenditures, and a seemlessly implemention.
We currently have a Cisco Pix 515 firewall with 3 interface cards, one for Internal, External, and DMZ. We have a SMTP server (running Symantec Mail Security for Gateways) in the dmz that scans email for virus' and spam, and if clean it is sent internally to our Exchange 2000 std. server. I do not want to touch the EX 2000 server, as it houses about 800 mail clients, as well it currently hosts OWA. We are not currently using ssl to the OWA site, but I would like to implement it. Currently we are port forwarding from the external interface of the pix on port 80 to the internal owa site on the exchange server. No hardening of the IIS, etc. has been done.
I am thinking of a modular approach, and installing another server to host OWA externally (DMZ). I have looked at various MS documents on "front end" exchange servers, and it looks like if I went that route, I would have to install Exchange 2003 std. and make it a front end server, that would sit on the DMZ. We currently have a license for EX 2003 Std. I also have read alot of recommendations for using ISA to reverse proxy to the OWA front end server. I am not a fan of this, and again, want to use what I have. I am concerned however of opening too many ports to my internal servers.
I have also read of folks using Linux/Apache and MS ISA to reverse proxy. As far as using linux, I am not sure I could recommend this to my boss, because we are a large MS shop, and no one there really knows unix that well. I might could get this going, I have experience with several different flavors of unix in past years.
I would appreciate any suggestions, comments, recommendations, or sample configurations that might point me in the right direction if I do choose to go forward with the exchange 2003 std as a front end server, on the DMZ of my pix. Please let me know if I need to provide any further detail...
Thanks,
Bryan
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: jjoseph_xPosted on 2004-12-30 at 08:44:55ID: 12927005
Using an Exchange 2003 server in the DMZ as a front-end still requires that you open a boatload of ports from the DMZ to the Inside (for NetBIOS, Kerberos, LDAP, SMTP, DNS, RPC etc) and you'll need to make registry changes on your domain controllers so that they use the same fixed port for the RPC endpoint mapper.
The simplest solution probably is use ISA or Apache/Squid (for the linux inclined) as a reverse proxy. You'll only have to open either port 80 and/or port 443 on the firewall that way.
If you've not too comfortable with Linux proxies, then just stick with ISA Server (there's tons of documentation on how to implement OWA with it).