I have just setup a new Exchange 2003 box, and I have OWA working internally with HTTP. The old OWA was setup to use https and will still work if I change the firewall Port translation to its IP address. How do I setup the HTTPS on the new exchange box so I can just point to the new IP address through the firewall?

Here is a step-by-step...Note if you are wanting to use the same external name from the original OWA server, then export the certificate and import on the new server and then configure IIS. http://www.petri.co.il/configure_ssl_on_owa.htmTim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

This did not work. Before these steps I could get to the page using http://chiron/exchange (chiron is the name of my Exchange server), but when I use https after these steps I get the following error: Internet Explorer cannot display the webpage What you can try: It appears you are connected to the Internet, but you might want to try to reconnect to the Internet. Retype the address. Go back to the previous page. Most likely causes: •You are not connected to the Internet. •The website is encountering problems. •There might be a typing error in the address. More information

What is the name that is in your SSL cert that is assigned in IIS? Also, is IIS set to require SSL? If so, you will have to use https and not http.Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

The SSL cert is assigned to the external name (entra), and IIS is set to require SSL on the Exchange folder in the Default Web Site.

So you will need to use https://externalname(in_cert)/exchange . Does that work? Have you switched DNS to make sure it is going to the correct server? Can you get to it by IP: https://IPaddress/exchage ?Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

What needs to be switched on the DNS? If I only use HTTP, then it can get through the firewall but I don't want business logins over an unsecure connection.

Hi, If you only have one public IP you might still have port 443 in a NAT to the old OWA server. Please check up on that since HTTP is working and HTTPS isn't. Also the DNS record that is created in the External DNS also has to point to the correct public IP that you are forwarding through your firewall. /Martin Exchange is a passion not just a collaboration software.

HTTP and HTTPS (443) are both part of the same NAT rule, so I figured that when I switch the rule it covers both. The external DNS (not ours) points to "entra", which is the same for HTTP or HTTPS.

You need to change the HTTPS rule on your firewall to point to the LAN IP of your new Exchange 2003 Server. I have seen in some cases, you must delete and recreate the rule for it to take effect or a reboot of the Firewall. This all assumes your Public Static IP has not changed which is not clear in your post.MVP Exchange Server