Share
ReportHi,
I am struggling to configure the Outlook client (Office 2010 x86, Windows 7) at my customer. They are using two domains to authenticate their users.
Domain A (rad.lan) Domain B (ocw.local) has a one-way trust configured between them. CRM is installed in the rad.lan domain and running under HTTPS (no IFD configured).
The web client works perfectly fine but I am unable to configure the Outlook Client which results in an SSPI negotiation failed error.
- CRM 2016 SP1
- HTTPS (443, no IFD)
- Host header in DNS is a c-name and resolves correctly (same in IIS & deployment manager)
- Correct date/time zones
- Correct certificates
I have tried forcing credentials on my laptop (connected through VPN) using both credential manager and editing the configuration file (to use custom credentials instead of default Windows) but this also result in an access is denied error when searching for organizations.
Now the implementation guide states that users from another domain cannot configure the Outlook Client and that this is an unsupported scenario (without stating which is supported):
Users in a different domain cannot install Dynamics 365 for Outlook
If the user domain account is in a domain different from the Dynamics 365 organization, the user will receive an error message (see below) when installing Dynamics 365 for Outlook. This is not a supported scenario.
Error message:
There is a problem communicating with the Microsoft Dynamics 365 server. The server might be unavailable. Try again later. If the problem persists, contact your system administrator.
The caller was not authenticated by the service.
Can anyone clarify on this? Am I forced to implement IFD to make this situation work?
Kind regards,
Jeroen de Wit
*This post is locked for comments
All responses (
Answers (
9,265
