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.
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...)
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.
February 22, 2008 11:25 AM
February 22, 2008 5:22 PM