Hello,
I have one strange problem with some users accessing OWA on Exchange 2007 - they get incorect username or password error. I really hope someone can give some hint.
Configuration:
1. server: Exchange 2007 SP1 on Windows 2003 server R2 64bit SP2 (new instalation)
2. server: Windows 2003 server SP2 as 1st domain controler
3. server: Windows 2003 server SP2 as 2nd domain controler
AD is in Windows 2000 native mode. All servers are in one subnet (LAN).
Problem:
- If I create new user accout and new user mailbox I can access to this user maibox without any problem (OWA and outlook).
- If I create new mailbox for already exsisting user, I can access to this user mailbox from outlook but not from OWA. When I try to login I get "incorrect username or password". All data is for sure correct and it is in format domain\username, password.
To make things even more strange, there are same (three or four) exsisting usernames that do not have any problems accessing OWA. In three days I couldn't figure it out in what is difference.
So far i have:
- checked user and mailbox properties (n-times)
- removed and recreated mailbox of affected user
- in event viewer on exchange server there are no errors or warnings
- in exchange instalation log there were some errors saying that compression on IIS sould be disabled. In IIS config ->web sites properties->service -> compression for application and static files is disabled.
- If I set full access permisions (on problematic mailbox) for username that has OWA access, I can connect to problematic mailbox over OWA. ( I login to OWA with nonproblematic username and then I connect to problematic mailbox.)
For any usefull idea I would be really gratefull.
Best Regards,
Davorin
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hello and thank you for your answer.
ALL mailboxes were created on exchange 2007 server as there is installed Exhange management console. (New mailbox->existing user->chose user from AD list->chose exch. database->create.)
In Exchange management console are listed both domain controlers, but first "in line" is 2. server which also has all 5 FSMO roles. Dcdiag showed no issues.
I think that is ok.?
Hi,
The time diference is not the problem. All three servers have the same time.
Global catalog is on both domain controlers. Is that OK?
I have found out that the 2.nd domain controller is pointing 2.nd DNS server setting (ipconfig) to 4.th server, which has DNS server installed but is not integrated in DNS domain. (this server was recently demoted as DC). 1.st DNS server is installed on 2.nd server (all FSMO roles). We will set the 2.nd DNS on 2.nd DC and remove DNS from 4.th server.
I really hope that this is causing the problem.
I will let you know the results.
Regards, Davorin
Hello all,
I'm glad to tell you, that I figured it what was the problem - problematic users had defined in group policy rights to login only to their computer. When the restriction was removed everything worked just fine.
Maybe only one other thing to check if you have problems loging to OWA. All AD structure from root to the user should have Inherit permissions turned on.
Geyybecca and consultkhan, thank you for your help!
Best regards, Davorin
Business Accounts
Answer for Membership
by: GeyybeccaPosted on 2008-02-19 at 07:22:04ID: 20929156
Which server are you creating the mailbox from? which DC is it connecting to?
Which one of the two DC's hold the infrastructure master role? which of these two servers are Global cataloge servers? most likely one of these will be your issue