Answered by:
CRM 2011 Outlook Client will not authenticate

Question
-
I recently created a new CRM 2011 environment as per the install guide. It is set completely for IFD. The web acces works fine inside and outside the network. I upgraded the Outlook client, added the HomeRealmUrl, but it connect once, timed out while i was at lunch and will not recconect. Reinstalled many times. If I select CRM Online, it connects to our test CRM Online site fine.
There are no logs being generated to tell what is going on. It is talking to the CRM dicovery service becuase I am getting a Logon box, but then errors with "...cannot authenticate your credentials....". I totally unistalled and used the 4.0 version client, making the changes to the website as directed in the install guide, and that works fine. I am completely confused as to what is going on. Any thoughts are appreciated.
Saturday, February 26, 2011 2:34 PM
Answers
-
Our user manually changed the local time on a fresh PC, leaving the time zone as Pacific time (thanks Redmond)
Putting his time back and changing the time zone back to eastern (our time zone) did the trick.
- Marked as answer by Curt Spanburgh MVP ModeratorMVP, Moderator Friday, January 13, 2012 10:17 AM
Thursday, January 12, 2012 10:46 PM
All replies
-
Ok I think I solved this.
1. Remove the HomeRelmUrl the instructions tell you to add to the registry.
2. Enable tracing in the diagnostice tool for the client not as you are instructed on the Microsoft site.
3. Don't use the "CRM Online" option for IFD unless you are using Microsoft CRM Online a it tells you in the install guide.
4. Finally make sure the time difference in your Federation Server is not >5 minutes. Not sure if that was the final issue, but I saw something in the logs with that refernce.Not sure why they have suspect instruction the in the guide. Perhaps it is a different environment. Hope that helps someone.......
- Proposed as answer by Massoud Dehkordi Wednesday, May 18, 2011 5:27 PM
Saturday, February 26, 2011 7:04 PM -
Thanks for sharing. It was excatly removing the registry entry in my case.
You saved me a lot of time.
Wednesday, May 18, 2011 5:29 PM -
Our user manually changed the local time on a fresh PC, leaving the time zone as Pacific time (thanks Redmond)
Putting his time back and changing the time zone back to eastern (our time zone) did the trick.
- Marked as answer by Curt Spanburgh MVP ModeratorMVP, Moderator Friday, January 13, 2012 10:17 AM
Thursday, January 12, 2012 10:46 PM