Stop my public IP from being being redirected to Outlook Web Access
I have a firewall that I can control via its http web management console by visiting my public IP address http://184.191.34.7. I also have my Exchange server’s Outlook Web Access configured to be accessed by connecting to https://184.191.34.7/owa.
I would like to access my firewall using HTTPS (https://184.191.34.7) instead of HTTP, but when I add the “S” I’m automatically redirected to the OWA website. How can stop Exchange from automatically redirecting my public IP address to OWA. Do I need to change this in IIS? Is this an Exchange setting? Can anyone point me in the right direction or offer suggestions on what settings I may need to change? Thanks!
I would like to access my firewall using HTTPS (https://184.191.34.7) instead of HTTP, but when I add the “S” I’m automatically redirected to the OWA website. How can stop Exchange from automatically redirecting my public IP address to OWA. Do I need to change this in IIS? Is this an Exchange setting? Can anyone point me in the right direction or offer suggestions on what settings I may need to change? Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Would a "compromise" not be to change the https management listening port on the firewall from 443 to (say) 444 ?
If you change the management port you would have to access the router via https://184.191.34.7:444 which may not be desirable.
Look at IIS. You need to look at the site manager for the OWA site, and uncheck the require SSL box. That should fix your problem. You also need to remove the port forwarding rule for port 443 on your firewall. Of course, make sure you understand that is a less secure thing to do. Maybe changing the port is an option? What type of firewall do you have?
ASKER
Everyone's comments were helpful, but the problem was solved by enabling HTTPS management within the firewall. There were options within the WAN interface that needed fine tuning. Once this was corrected, the firewall was visible via HTTP, HTTPS and HTTPS:port#.
ASKER
Exactly what needed to be done, unfortunately I didn't have the settings configured correctly
Does OWA and Activesync still work?
Alan