I am trying to implement OWA on Windows Server 2003 with Exchange 2007, accessible from the web. In order to do this I was informed I needed to enable forms authentication. Whether or not this is entirely true, I would still rather enable forms authentication.
I have purchased a Commercial Certificate and used the common name mail.mbnlaw.com. I enabled Outlook Anywhere and used the external host name of mail.mbnlaw.com. Under OWA properties the internal address is set to https://exchange.mbnlaw.mbnlaw.com/owa
. The external address is set to https://mail.mbnlaw.com
Authentication under OWA properties is set to Integrated Windows Authentication in both IIS and Exchange Management Console.
The firewall (WatchGuard) has port 443 opened for this server.
The domain mail.mbnlaw.com resolves to the correct public IP address when doing a nslookup. (The pubic IP address to the Exchange server.)
Now, when I try to open https://exchange.mbnlaw.mbnlaw.com/owa
it immediately gives the error: 440 Login Timeout.
I have reset the passwords, to match, for the IUSR_EXCHANGE and IWAM_EXCHANGE accounts and ran a script to sync these accounts on the Active Directory with IIS. I did an iisreset afterwards as well.
I am still getting the 440 Login Timeout error.
My question is, what steps do I need to take to publish OWA 2007 to the web using a third party firewall. If it is easier and if I am close to completing the above task, what else could I try to resolve the 440 Login Timeout error? I don't mean to pose two questions, but they are both related and I am giving you experts the option of picking the easiest route to getting OWA working on the web.