Setting up OWA in Extranet

[IndyGill]

Im trying to setup OWA (Outlook Web Access) into my intranet site which using SSL and Windows Login. My web server has an external IP, however my Exchange Server does not. I want to be able to view my /exchange web from my live web server. So I tried to do a redirect page from my intranet site eg. Response.redirect(

http://exchangeserver/exchange)

this only works if im on the LAN, however if Iog onto to it externally it does not work as it does not know were

http://exchangeserver

/exchange is.

Do I have to give my /exchange virtual an external IP or is there another way around this?

By the way im using Windows 2000 and Exchange 2000. I would be grateful for any help on this

Many thanks

 

[Tumpy613]

The

HTTP://Exchangeserver/exchange

does not have a vaild external DNS entry for routing therefore you cannot connect. External address will help...

 

[IndyGill]

I was wondering is there was anyway i could move the /exchange virtual to my live web server, or some way of trusting my local IP on my exhange server to be included in my site which is on the live web sever without giving it an external IP?

 

[Evilbart]

use portforwarding (your website runs on port 80, run the iis on your exchange on eg port 88 and forward your port 88 on your firewall to your exchange server
users can type

http://www.domain.com:88

to access OWA
( or have a front-end/back-end setup)

just a suggestion

/Bart

 

[securityforums]

Two good options suggested by bart there, you can port forward on pretty much any decent firewall, am I detecting no firewall here

If you only have one public IP which is in use for the webserver, why not port forward as suggested but do this over SSL

 

[IndyGill]

Thanks guys

I have a Watchguard Firewall and i think this should have these capabilities. I like the sound of of the port forwarding.

Many thanks once again

 

[securityforums]

Indy I have a watchguard too, a firebox II.

In policy manager, create a new rule called OWA, and then when creating the ports you can set the internal natted port to be different to the external.

So like in the previous posts you could forward port 88 through to 80 but this means people would have to remember the new address.

Personally I think you should go for SSL, and allow 443 through only from the firebox to the exchange server

 

[IndyGill]

My site on the web server also uses SSL which is over port 443.

I am looking to use the same SSL Certficate on my Exchange Server, so does this mean that I will have to designate a different SSL port for my excahnge server in order to do this redirect at the Firewall.

Does it matter that SSL works on another port other than 443??

Thanks for all your help.