General discussion
May 27, 2004 at 11:50 AM
imakedeals4u

How to Leverage OWA via a Web Server?

by imakedeals4u . Updated 22 years, 4 months ago

Setting up a 2003 network and having a problem with OWA redirection .

Previously I loaded exchange on my web server, but have now seperated them for obvious reasons.

Here’s a quick lowdown:

Have a single IP with a Watchguard Firewall routing the traffic.

Incoming HTTP(Web) traffic is directed to internal ip *.*.*.251 via firewall

Incoming SMTP (Mail) is directed to internal ip *.*.*.253 via firewall

On Web server there is a Host header of mail.domain.com with a permanent URL redirect to main.domain.com

On Exchange 2003 server, the default website is pinned with the main.domain.com Host header.

Set DNS up on internal AD server.

When I tested OWA internally, it worked like a charm…

Outside, it is not and, in hindsight, assume it is because the IIS server is supplying the external browser with the the Exchange server dns name and port 80 is closed to the outside world.

I have seen plenty of articles that address using a ISA server, but just don’t have the funds.

Been searching knowledge base and can’t find a “best practice for internal redirect off a single external IP”…

So any ideas?

Your input will be greatly appreciated.

Thanks!

This discussion is locked

All Comments