OWA Failed login

I have new domain that has been setup and when the users try to login via OWA its giving them page cannot be displayed.  They have no issues POP or through outlook.  When i look in the event logs i see failure audits for this user saying they are unable to login.

Can someone please help!!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


Is this with the second domain that you have set up, or is it with the one that was already established?

In IIS, have you set the security (directory security tab) so that you are authenitcating against the new domain not the old one?

If these users do not have an email address (it doesn't have to be their default address) in the Primary SMTP domain (as defined in your Default Recipient Policy), then they will not be able to use the default OWA Virtual Directory.  You would need to either give them another email address in your Primary SMTP domain, or create an extra Exchange Virtual Directory for the domain in Exchange System Manager.
lgropperAuthor Commented:
rj - this is a new second domain that was just setup.  I need to have both domains access OWA.

Lee - The default recip. pol. has both companyA and B setup in it.  So when the new user is created they get both addresses, i just change which is their primary.  Strange thing is that when i first set them up, it works for about 5 min... then i get page cannot be displayed.  <----- I just tried this again, and no such luck... straight to page cannot be displayed.

Please help!
HTML5 and CSS3 Fundamentals

Build a website from the ground up by first learning the fundamentals of HTML5 and CSS3, the two popular programming languages used to present content online. HTML deals with fonts, colors, graphics, and hyperlinks, while CSS describes how HTML elements are to be displayed.

lgropperAuthor Commented:
One other thing, would it matter that i am using SSL??
It should not matter if you are setting up using ssl or not. Does it work not using ssl, or have you ticked the must use ssl? Try it just using normal http to see if you get the same error.

One thing that you could make clear to me .. when you say you have two domains, are you talking about two email domains or two active directory domains? When I first read your email I presumed you meant AD domains but now I am not too sure

And do they still have both addresses after five minutes?  They probably do, but something may be removing them.
lgropperAuthor Commented:
This is still so weird.  the users are exactly the same as the users in the domain A.  its just they cannot access OWA.  This time i setup the users tey worked for about a week.  Then out of nowhere they stopped working again.
Which version of IIS are you using?  If it's IIS5 (i.e. Windows 2000 server), and your OWA uses Basic Auth, then your users will need the Logon Locally right on the OWA server.
lgropperAuthor Commented:
this is IIS6 on windows 2003 server with 2003 exchange.
lgropperAuthor Commented:
We are using ssl and the certificate is for domain A which works fine.  Could that be the issue? there is not certificate for domain B? IF so how could i correct that?
lgropperAuthor Commented:
This is an error i am getting on the exchange server,

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8270
Date:            15/02/2006
Time:            11:44:17 AM
User:            N/A
Computer:      MAIL1
LDAP returned the error [20] No Such Object when importing the transaction
dn: <GUID=11E6CCD0-6420-49AF-98B1-52023FB6B472>
changetype: Modify

For more information, click http://www.microsoft.com/contentredirect.asp.
lgropperAuthor Commented:
- Error: 20 - To resolve this issue, move the following groups to the default User container:
1. The Exchange Enterprise Servers group.
2. The Exchange Domain Servers group.
3. The Exchange Services group. See M822927 for more details

this seems to be the answer, but the accounts are in the defaut user container!
Your error is mentioned here:


See if the articles that Ed refers to (Q287137 and Q822927) are any help.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.