My users have begun to have issues accessing Outlook Web Access 2007 (OWA 2007) from outside the network. We can access it just fine using the following from inside the network: "https://servername/owa
". However, when they use the external name: "https://www.domainname.net/owa
" - they get: "Internet Explorer cannot display the webpage"
Here has what has changed recently: We just switched ISPs and we installed a new certificate.
Here is what I have done up to this point: The NATTING occurring by the firewall appears to be working. So, the domain name, which now points to the new IP address, seems to be connecting to the firewall IP and then NATTED correctly to the internal server. We know this because if you put in "https://www.domainname.net
" (with no /owa) - you ge a "page under construction". This would seem to tell me that we are getting to the web server. Additionally, just using the external IP address, you get the same results. If you put in "https://www.domainname.net/exchange
", you get hit with a username and password window. I know this used to be the correct directory in exchange 2003 but remmber, this is 2007.
I looked at the certficate and the correct domain name is listed. I tested it externally when we first purchased it as well. It is a UCC certificate and the Subject Alternative Names are all listed there.
The only thing I have been able to come up with is deleting and recreating the /owa directory but I'm a bit scared to do this (much less I don't know how to do it right). I seem to have found the Power Shell command to do this somewhere but what are the possible repercussions of doing so? Is this really the issue?