I have AD 2003 and Exchange 2003. I have 1 user with a problem. When he tries to open Outlook, he gets the following message "Cannot open your default e-mail folders. MS-Exchange is not available......." He has no problem logging into Exchange 2003 Web Mail. I can connect to his mailbox from my Admin account. He had this problem 10 days ago. I exported all of his email. Deleted his AD account and his Exchange mailbox. I created a new account for him, with a new ID, new email address, and added his old email address as a SMTP Alias. This seems to have fixed the problem. Yesterday the problem reappeared. If I login to a different system as him, I get the error message. I have never seen anything like this. Any Ides?

Hi, Is windows 2003 sp2 installed on the exchange server? http://msexchangeteam.com/archive/2007/07/18/446400.aspx Leif

Yes, SP2 is installed, but the problem is only occuring on 1 of over 100 accounts. This document seems to imply that the problem would be more widespread across accounts.

Can he get to his mailbox via OWA?

The user has no problem accessing his mailbox via OWA.

Does the user access the excahnge server using the DNS name of the server or the internal ip address? Could be a dns issue...

The user can ping the email server by both IP address and Domain Name. this problem occurs on any PC the user logs into.

Do you use roaming profiles? Have you tried recreating the profile if so...?

is your user hiden?

We are using exchange 2007, and have started experiencing the same issue on 4 different accounts. Could you find a solution for your problem yet?

I saw this on a couple of migrated accounts in the past where dismounting the mailbox database and remounting it fixed the problems. However, I saw this error this past week and we spent at least a day troubleshooting it. Finally, we deleted the mailbox from the account, deleted the user account, then created the user a new user account, then reconnected it to the mailbox. THEN it worked. We never really understood why that worked, but this was in E2K3. We just figured something was REALLY munged up on the permissions.

Did you ever find any resolution for this issue?