General discussion


How to Leverage OWA via a Web Server?

By imakedeals4u ·
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 with a permanent URL redirect to

On Exchange 2003 server, the default website is pinned with the 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.


This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to How to Leverage OWA via a ...

I debated trying to give a suggestion to this... I'll ask this, what URL are you using publically e.g. not on the LAN, to connect to the Exchange server?

Collapse -

by BlitzSonik In reply to How to Leverage OWA via a ...

OWA uses port 80 as the default port. You can change the default port to something else if you don't want to open port 80 to the outside. You do this in IIS (Internet Services Manager). Check this link for more information. Hope this helps!

Back to Software Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums