password prompt for a few users after new Exchange 2010 certificate is installed...

I have Exchange 2010 SP1 running and I just put on a new certificate (3rd party) and then assigned the services to it. However, there are a few users that said Outlook is now continually prompting for username and password. I have restarted IIS after the install of the certificate, but is there something else I have to do on the clients to get it to accept the new cert?

I have the feeling that this is not unrelated since it started right after the new certificate went on...
LVL 1
willlandymoreAsked:
Who is Participating?
 
willlandymoreAuthor Commented:
When I reassigned IIS to be on the old certificate everything started working again. I'm not sure why Exchange is giving me this behavior, but that's why it's happening
0
 
askurat1Commented:
I would try clearing the browser data on the pc  and restart outlook. Also try restarting the server if possible.

You may have to reconfigure outlook settings.
0
 
lamaslanyCommented:
Is there any chance you've affected the supported authentication mechanism?  For example changed from Basic to NTLM/Windows Integrated?  
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.

 
willlandymoreAuthor Commented:
no, no change to that. The difference would be that the CN is another one, but the old server alias is on the certificate as well
0
 
willlandymoreAuthor Commented:
autodiscover seems to be overwriting the outlook settings as well because if you change it to the CN on the cert and they restart it is okay, but then there are some users that it changes the settings back to the way they were
0
 
Brian GeeCommented:
Here is an article composed by one of our EE Experts here:

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2300-Outlook-continually-prompting-for-username-and-password.html

Despite noting Exchange 2007, I'm sure that the information therein will be helpful with Exchange 2010 as well.
0
 
willlandymoreAuthor Commented:
yeah, I've seen that article via another website but the DNS, autodiscover and everything else seems to be okay. The only thing that changes was the Common Name on the certificate. However, the old one was still listed on the certificate, it just wasn't the common name
0
 
willlandymoreAuthor Commented:
worked
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.