After a recent outage, all of our Outlook 2007 clients in cached exchange mode are getting prompted for a network password. How do I figure out why this is happening?

If I go into the client and change the security from the default of Negotiate Authentication to NTLM it stops prompting for a password.  However I need to figure out why this is happening so I dont have to do it this way as we are getting ready for a large Outlook rollout.  I read Outlook 2k7 uses NTLM by default so why would a network outage change this?
AITAsked:
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.

Exchange_GeekCommented:
On the Exchange Server which authentication do you have for /Autodiscover ?
0
AITAuthor Commented:
Integrated windows and basic
0
Exchange_GeekCommented:
Please remove Basic Authentication, let your users be authenticated once they logon to their windows server.

Post unchecking the check box, please run iisrest and test once more
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

AITAuthor Commented:
We found that someone had put a dns zone in that was screwing stuff up.  After this was deleted, the login prompts went away.  I am intrigued by your recent suggestion.  Out of the box it has these checked.  Were you suggeting this as a way to fix the problem or as a best practice?  Let me know
0
Exchange_GeekCommented:
Well its always a best practice to have WIA checked - unless you have people from outside ur network logging in.

Wow, that was a pretty innovative solution for such an issue.
0
AITAuthor Commented:
I think there was more to this, and yes I agree, it is a little quirky.  Thanks for your input
0
Exchange_GeekCommented:
Just trying my best to help you with my bit of exp, however thanks for providing the solution hinting to DNS - I wouldn't actually look at that since I wouldn't have any one touch my DNS servers without knowing what they are doing.

But hey it is a different sort of solution :)

Take Care

God Bless.
0

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
AITAuthor Commented:
I totally agree with you, and it is a point of contention.  And, yes, I am chuckling a little
0
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
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.