I've recently setup SSL on my exchange 2003 server, and I wanted to enable forms. After I enable forms and reset IIS, when I try to log back into OWA I get a page saying error 440 Login Timeout. Has anyone else seen this error message, and if so, have you been able to find a work around?
I ultimately would like be able to see the nice OWA logon page.
Make sure that this service is started on your Exchange server
HTTP SSL: This service implements the secure hypertext transfer protocol (HTTPS) for the HTTP service, using the Secure Socket Layer (SSL). If this service is disabled, any services that explicitly depend on it will fail to start.
If not, start it. Set it to start automatically after that. Problem should be gone.
IÆve had this same error. IÆve started some services on my server and I havenÆt had any problems since. Make sure the following services from your Exchange server are running, because they are all contingent upon each other in order for OWA to work properly.
HTTPS SSL Remote Procedure Call (RPC) Network News Transfer Protocol (NNTP) Microsoft Exchange IMAP4 IIS Admin Service
If you find that you needed to start any of those services, switch them to automatically start the next time, or you will have to start them each time you have to reboot your server, for whatever reason. Let me know if this works for you.
Thank you for the suggestions. However after trying them, I was still getting the error message.
I did notice, when I enable forms I get this message: "Exchange System Manager
Forms Based Authentication requires clients to use a SSL connection. If SSL encryption is not off-loaded to another source, complete the following steps:
-Configure SSL Restart the IIS service."
We only have one exchange server, and we have generated our own security certificate, and it is working properly.
Also, could you verify what settings you have in the directory tab for exchange, exchweb, and public in IIS? I have anonymous logon unchecked and basic authentication checked for all three.
IÆve had this same error, i checked that the Internet Guest Account was locked out. (Check IUSR_yournameserver in Active Directory) After i unlocked it OWA is rinnug ok again.
I had the same 440 and just fixed it. My issue was the version of oledb32.dll was older than what was required. I did an upgrade from Win2k to 2003 and the old .dll was still in there. I did a fresh install on another machine, booted my existing machine into safe mode w/networking, copied the .dll to the correct location, rebooted my machine, registered the .dll, rebooted and it worked. If any of you are running a 2.7.xxx version this could be your issue.
I gave it a try but I was unsuccessful. I followed step by step but I still get the error message. I remember seeing that article before, but I didn't pay too much attention to it because it was referring to OMA. It is strange, that this was the only article that could be found on Microsoft's website.
We may be getting another email server for redundancy purposes. Do you think it's almost a requirement to have a front and back end server setup in order for FBA to work?
This error was driving me nuts! I went as far as installing a second exchange server and that didn't resolve the issue. In any case, I got it fixed by removed forms based authentication, restarting iis, and then adding forms again. After that it all worked fine. Thanks for the tips, guys.
I gave it a try and no luck. At least it's helpful to know that I don't need to setup another exchange server.
What are your directory security setting in IIS? I have everything checked off except for basic authentication in exchange, exchweb and public folders. I also left my domain name blank, so that the user would have to type in the domain at logon, (for security purposes)
Here is my experience with the "440 login timeout" problem. My problem was that it stopped working after a period of time, which required a restart of the iis admin service.
If you set via GP a policy for "Allow logon locally" without IUSR_COMPUTERNAME it stopped working after a while (ca 12 hours). Disabling the GP policy will let the server control who can log on locally and everything worked fine.
You need make sure the anonymous box is checked under directory security for exchweb. Also double check that under the exchweb folder the bin and auth folders have the anonymous box checked.
This should fix your 440 issue. You have to have anonymous checked so the ISUR account can access those exchange folders (These are the default permissions with form based authentication.
I gave it a try, and still had no success. I made sure that both the Bin and Auth folders had anoymous access. For my exchange and public folders, I have set those to basic network authentication and I've also left the domain names blank, so that the user would have to type in the domain name when they logged in. Are those settings ok, or do they need to be changed as well?
Thansm, All you need to restart in this case is IIS. I currently have the same problem and I am working on resolving this - I have a support call open to Microsoft about it. I've even tried running setup.exe with the /reinstall switch to reinstall Exchange and I still get the same error whenever Forms Based Authentication is switched on. I'll keep you posted with anything I get from them.
Thansm, I've just tried taking off Forms Based Authentication and I get errors with a "loading" page - do you get the same if you take it off? If so you might want to try getting OWA working in normal mode first and you might want to take a look at this in general as it talks you through checking the settings for OWA: