Topic: Exchange OWA behind E-smith

[Lynn]

Im using e-smith as a firewall, and decided to go ahead and put the website on it as well.

Problem is, to get to exchange's outlook web access, you have to have to use the url:

www.domain.com/exchange

www.domain.com gets you to the firewall, but is there anyway to have e-smith pass that particular page (/exchange) back to the server behind the firewall?

Thanks...

[Guck Puppy]

Search the forums for "ProxyPass"

[Chris Meredith]

I used proxy pass for a while, and thought it was noticibly slower.  I would recomend port forwarding a port other than 80 instead.

http://www.domain.com:88
forwarding to
http://internalserver:80

OWA tends to redirect URLs to the port it thinks its on, so you would be better off having IIS listen on the same port you use on the external side.

http://www.domain.com:88
forwarding to
http://internalserver:88

I have been using it that way for a while.  It works fine.  I also have Squirell Mail setup at another site on the firewall, and have it directed to the Exchange Imap server.  If all you want is you mail, not the contacts and calandars, that works great.

[Lynn]

That was great. Thanks for the tip.

I use the contributed port-forwarding page for server-manager. And it wouldn't let me enter the text you used:

http://www.domain.com:88
forwarding to
http://internalserver:88

It did however, let me forward port 88 to the internal ip of the exchange server using just the numbers:

88
192.168.0.x
88

Hope you understand what I mean. Anyway, after changing the port number the default website listens to using the Internet Information Services manager on the internal server, (to 88 as you suggested) it worked perfectly.

Way cool.

[Lynn]

Oh, one other thing I had to do.

After changing the port on the default website, then stopping it. It would not start back up. Warned the port was in use.

The Kerberos service listens on port 88, if its running.

I disabled the Kerberos service since its not used, and the default website started right up.

Anyone actually using Kerberos would need to pick another port for the website.

[Bobb Jenner]

Another thing you can do in addition to the port forwarding mentioned above is create a redirected web page. EG: create a web page at http://company.com/exchange/index.html that redirects you to  http://www.company.com:88/exchange/default.asp. Thay way users don't have to remember the port number (and you can easilly change it if needed).

[Donato]

Can anyone tell me how secure is to implement this solution? And if I can use a secure channel for this connection like E-Shith does (https)? Thanks