I've seen OWA issues when any of these are true: 1. The domain account was not completely configured correctly. For example, UPN field was not populated. 2. When I checked the mailbox in PowerShell, it said it was a LegacyMailbox (on Exchange 2007). Have to apply the security settings on the mailbox to convert it. 3. When the Associated External Account permission is set to another account than the one they are logging in (to OWA) with. They can have mailbox permissions and open Outlook, but OWA won't allow them in.
On Wed, Feb 11, 2009 at 10:53 AM, Chris Blair <chris_bl...@identisys.com>wrote: > Having some problems with an Exchange user. We are running Exchange 2007, > with the all updates. The day started out by this user (our CEO of course) > not being able to login to Outlook at home using Outlook Anywhere. Next we > tried OWA, which gave an error saying it couldn't open the mailbox. > > > > I ended up deleting his AD account, creating a new user with the same name > and then reconnecting the Exchange mailbox to the new account. This then > allowed him to login to OWA, but not Outlook. Outlook continues to prompt > for a username and password. I then type in his AD credentials, and after a > second the login box pops back up. > > > > I have tried different version of Outlook, 2000, XP, 2003, and 2007, all > prompt for a username and password. No matter what I enter it always comes > back to a login prompt. > > > > Thanks! > > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
