I have a problem with one of my backend Exchange 2003 mailbox servers. When users who have mailboxes on this server try to logon to OWA, they can't logon, they immediately receive a timeout error. Users who access OWA who have mailboxes on any other Exchange server have no problem, they can logon into OWA fine. Let me describe the environment: I have over 50 Exchange servers, some 2003 and some 2007 (in the process of migrating to 2007). (note: I can't migrate to Exchange 2010 at this time because our archiving solution does not support 2010 yet). When users access the webmail url, the Exchange 2007 CAS servers answer the request and then pass the request back to the appropriate mailbox server for the user. All other Exchange 2003 and Exchange 2007 mailbox servers work fine; users are able to logon fine to OWA. There is one Exchange 2003 server, however, that users cannot logon to. When a user who has a mailbox on the problem Exchang server tries to logon using the webmail URL, they receive an immediate Session Timed out error on the OWA logon screen (they can't logon at all). If you point your browser to go directly to the problem Exchange mailbox server by IP address and try to get to OWA that way, you get a logon box correctly and you try to logon, and it starts to bring you into OWA, but then you get the logon box again and again, and this repeats over and over again. You can see a partial OWA screen in the background (inbox, etc.), but the logon box just keeps reappearing on top of that. I have compared the IIS settings and don't see a difference. Any advice? I am getting some very aggravated users. Thanks.Janice

That's a hard one to diagnose in a forum such as this. It's a hard one to diagnose even when you're connected to the server. Myself, I'd move these mailboxes to a new Exchange 2010 server.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

As I originally stated, I can't move these users to Exchange 2010 because our archiving product won't support Exchange 2010. I can't migrate 45,000 to Exchange 2010 until our archiving product is ready for that version.Janice

hello, please consider below articles for your refrence on this http://msexchangeteam.com/archive/2007/02/07/434523.aspx and http://msexchangeteam.com/archive/2007/09/10/446957.aspx Thank you Dhruv

Hi Janice, Any update for your issue? Other information for you: http://msexchangeteam.com/archive/2008/12/31/450340.aspx Regards! Gavin

I second that. I would build a non-production mirror of your issue and troubleshoot that way.

Your Exchange 2003 virtual directories have an issue as you cannot logon by ip address either. You can rebuild your IIS directories http://searchexchange.techtarget.com/tip/Repairing-damaged-OWA-virtual-directories-in-Exchange-Server-2003 Will definately help .. Even removing IIS , then rebuilding it ( or running exchnage setup - a sort of DR could restore OWA , also you may need to reapply windows sp, other way is to take the backup of iis from iss manager and restore an one if you have one )

I second that. I would build a non-production mirror of your issue and troubleshoot that way.