Currently, I've got OWA working internally no problem, my problem is external access to OWA. Right now my firewall is currently set up to route all HTTP & HTTPS traffic to my internal web server. I've got one E2k server which is also internal. I've tried using host header names in IIS on the web server and redirecting specific URL for OWA like http://webmail.domain.com to the E2k server but since it's internal, the redirect doesn't work. Instead of the redirect option in IIS, I thought about using A share located on a different server option but I haven't fully explored this option yet. Another option that I've thought about is changing the port numbers in Exchange for HTTP/HTTPS and add routing in the firewall based upon the new port number http://webmail.domain.com:8080 but the users probably wouldn't remember to put the port number at the end of the URL so that probably isn't an option. Any suggestions would be appreciated Thanks
Choices - install OWA on the web server as a FE/BE solution (easiest) or create a new virtual directory on the web server pointing at the live OWA server (you need a share on the live OWA to do this and then need to check the permissions). "Vic York" wrote in message news:9856BF46-66E3-41BD-BCF8-28ED71F54181@microsoft.com... > Currently, I've got OWA working internally no problem, my problem is > external > access to OWA. > > Right now my firewall is currently set up to route all HTTP & HTTPS > traffic > to my internal web server. I've got one E2k server which is also > internal. > > I've tried using host header names in IIS on the web server and > redirecting > specific URL for OWA like http://webmail.domain.com to the E2k server but > since it's internal, the redirect doesn't work. Instead of the redirect > option in IIS, I thought about using A share located on a different server > option but I haven't fully explored this option yet. Another option that > I've thought about is changing the port numbers in Exchange for HTTP/HTTPS > and add routing in the firewall based upon the new port number > http://webmail.domain.com:8080 but the users probably wouldn't remember to > put the port number at the end of the URL so that probably isn't an > option. > > Any suggestions would be appreciated > > Thanks >
