440 Login Timeout at Outlook Web Access

By ralfeus ·
I have installed new Exchange environment (1 CCR mailbox cluster, 2 CAS servers and 2 HT servers). All servers run Exchange 2007 SP2 Update Rollup 2 on Windows 2003 R2 SP2.

When I set FBA at OWA VDs at CAS servers I get immediately an error "440 Login Timeout". When I turn off FBA and set any other authentication type it works fine.
The problem is same at both CAS servers.
I have already tried all common solutions mentioned in KB (;EN-US;941201) and other sources:
0. Recreated OWA VDs
1. Reset password for IUSR_* and IWAM_* accounts
2. Checked authentication methods for OWA, Bin, Auth and controls (in my case it's directories
3. Checked permissions on all these folders
4. Reinstalled IIS and CAS role on one of CAS servers.

Nothing helps.
I deployed custom ASP.NET application on same server and configure it to allow anonymous authentication. It works fine.
I compared authentication methods on each directory and NTFS permissions with ones at another environment (working one). Everything is same. So I'm out of ideas.
Is there anything else can be done to fix it?
Thank you in advance.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Common Issue with Exchange 2003, 2007, 2010

by uganr In reply to 440 Login Timeout at Outl ...

This is a very common issue with Exchange and OWA.
This error occurs due to two accounts in active Directory: IUSR_(dc name) and IWAM_(dc name) which either gets locked or has their password expire.

I've had this countless times on my client sites.
The resolution I use can be found here:

Related Discussions

Related Forums