Outlook Account Will Not Connect to Microsoft Exchange Server But OWA Works Fine

Dear Sir,

I am currently using Exchange 2013 and connected with Outlook 2010. One day, the outlook keep prompting for username and password. But OWA works fine.

Any advise for me?

Thank you.

With regards,
Wataw
WatawAsked:
Who is Participating?
 
ModernMattCommented:
Closed, 500 points refunded.

ModernMatt
Experts Exchange Moderator
0
 
Jon1999Commented:
Are you having this problem on just one computer or on multiple computers? Are you on a domain joined computer? Have you restarted the computer you are having the problem with?
0
 
WatawAuthor Commented:
Dear Jon,

Multiple computers, joined domain. restarted.

Thank you.

With regards,
Wataw
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Jon1999Commented:
Multiple accounts or just one?
0
 
Nick RhodeIT DirectorCommented:
Is there perhaps a proxy in place?

Check DNS and do a simple ping to see if the pointers are correct.

Open up outlook and do a ctrl+right-click on the outlook icon in the system tray.  View the connection status.  You can also run a test email auto-configuration to see if it is auto-discover by chance
0
 
hecgomrecCommented:
If this is the first time the connection is getting establish, please try to enter "DomainName\UserName" and pass.Word combination and select to save this credentials.

If this isn't the first time and the connection was lost, make sure the user credentials are valid.  log off the current user and log back in, open outlook and see if still ask for credentials.

Most of the times when outlook start asking for credentials around an organization is because exchange can't authenticate the users with AD.  If there were updates and the server were restarted to finish updates, most likely the exchange booted first while the DC was down or rebooting. Make sure your DC is fully operational before restarting your Exchange.
0
 
WatawAuthor Commented:
Dear All,

I have fixed the problem. It was because MS issued this patch and the servers AD and Exchange 2013 Server had installed it automatically.

http://www.infoworld.com/article/2897814/operating-systems/server-2003-admins-beware-microsoft-re-issues-botched-netlogon-patch-kb-3002657.html

Thank you very much.

With regards,
Derek NG
0
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.

All Courses

From novice to tech pro — start learning today.