HowTo: Internally redirect http for Outlook Web Access
Being a relatively small firm, we have just one public IP address. Before we apply for another, I would like to hear your opinion on this:
Until now, our web sites have been located on external web hotels, and http access to our IP address has been used for Outlook Web Access.
Last month, we have implemented our primary website on an internal server - needing to direct http access away from the Exchange server machine and to IIS on another server machine. That means Outlook Web Acces has become unreachable at the moment. Our firewall (NetScreen-25) has no known way of splitting the traffic on port 80 to different targets.
Question:
Is there any recommendable technique related to IIS and TCP that would allow for letting OWA sessions reach Exchange through IIS on the new server? (Virtual directories, host-header routing...)
Or:
Is there any recommendable way of letting OWA sessions reach the server running Exchange by using a different port number (say, 8080)?
TIA for advice.
Software/Hardware used:
Software/Hardware used:
ASKED:
February 22, 2008 11:25 AM
UPDATED:
February 22, 2008 5:22 PM
RELATED QUESTIONS
- Can I set up Outlook Web Access without a front-end Exchange server?
- The Server that contains information about your user account nd mailbox can't be found
- Setting up RPC over HTTP
- OWA login generates HTTP/1.1 503 Service Unavailable error message
- Exchange 2007 Public Folder permissions and PFDAVAdmin issue
Answer Wiki:
yes you can change the http port to a different port number, that is one way of doing it. Here is a MS article on it:
<a href="http://support.microsoft.com/kb/240753">http://support.microsoft.com/kb/240753</a>
It is also recommended that you change your OWA (Outlook Web Access) to be using a secure connection (https) instead of a none secure connection (http). By using a secure connection peoples domain usernames and passwords will not be transmitted in clear text between there laptops / home machines and the server. This has the added benefit of moving OWA from port 80 to port 443.
It's a fairly easy procedure to setup. Edit the website on the exchange server, and select the "Directory Security " tab. Select the Server Certificate tab. Run through the wizard to create a new certificate. It will create you a text file that you can then use along with a certificate authority (there are many to choose from) to create the certificate. After the certificate is emailed to you run through the same wizard and follow the prompts to import the certificate. Then on the "Web Site" tab enter 443 into the SSL box and click OK. Tell the firewall/router to allow port 443 traffic to your Exchange server and you should be all set.
People will now need to type in the https:// in front of the OWA domain name, to get to OWA.
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
