How to get out on Communication protocol mismatch between the client and the server?

derek
Member Posts: 22
Hi,
Couple of last days I'm trying to get NAV2016 (CU4), Office 365 and Azure Active Directory to work together.
I have done installation as documentation says, but so far without success. I'm also used Best Practices Analyzer for debugging, but it can't help on this issue.
When I have VPN connection active on client computer, then I can open NAV with SSO login (ClientUserSettings: "Server" value is IP address).
If I close the VPN and change the "Server" value to localhost. After that SSO login goes right, but the NAV says: "Communication protocol mismatch between the client and the server". When I use this same ClientUserSettings on NAV server, then I could open the connection. Only difference with ClientUserSettings file and NAV Service is ClientServicesCredentialType. On NAV service it is NavUserPassword and on client it's AccessControlService. With the documentation this should be ok.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="Server" value="localhost" />
<add key="ClientServicesPort" value="7046" />
<add key="ServerInstance" value="DynamicsNAV90" />
<add key="TenantId" value="" />
<add key="ClientServicesProtectionLevel" value="EncryptAndSign" />
<add key="UrlHistory" value="localhost:7046/DynamicsNAV90" />
<add key="ClientServicesCompressionThreshold" value="64" />
<add key="ClientServicesChunkSize" value="28" />
<add key="ClientServicesKeepAliveInterval" value="120" />
<add key="MaxNoOfXMLRecordsToSend" value="5000" />
<add key="MaxImageSize" value="26214400" />
<add key="ClientServicesCredentialType" value="AccessControlService" />
<add key="ACSUri" value="https://login.windows.net/XXX.onmicrosoft.com/wsfed?wa=wsignin1.0&wtrealm=http://dynamicsnavwinclient/&wreply=http://dynamicsnavwinclient/" />
<add key="AllowNtlm" value="true" />
<add key="ServicePrincipalNameRequired" value="False" />
<add key="ServicesCertificateValidationEnabled" value="true" />
<add key="DnsIdentity" value="RootNavServiceCA2" />
<add key="HelpServer" value="NAVO365" />
<add key="HelpServerPort" value="49000" />
<add key="ProductName" value="" />
<add key="UnknownSpnHint" value="(net.tcp://localhost:7046/DynamicsNAV90/Service)=NoSpn" />
</appSettings>
</configuration>
Have anyone clue on this kind of case?
Couple of last days I'm trying to get NAV2016 (CU4), Office 365 and Azure Active Directory to work together.
I have done installation as documentation says, but so far without success. I'm also used Best Practices Analyzer for debugging, but it can't help on this issue.
When I have VPN connection active on client computer, then I can open NAV with SSO login (ClientUserSettings: "Server" value is IP address).
If I close the VPN and change the "Server" value to localhost. After that SSO login goes right, but the NAV says: "Communication protocol mismatch between the client and the server". When I use this same ClientUserSettings on NAV server, then I could open the connection. Only difference with ClientUserSettings file and NAV Service is ClientServicesCredentialType. On NAV service it is NavUserPassword and on client it's AccessControlService. With the documentation this should be ok.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="Server" value="localhost" />
<add key="ClientServicesPort" value="7046" />
<add key="ServerInstance" value="DynamicsNAV90" />
<add key="TenantId" value="" />
<add key="ClientServicesProtectionLevel" value="EncryptAndSign" />
<add key="UrlHistory" value="localhost:7046/DynamicsNAV90" />
<add key="ClientServicesCompressionThreshold" value="64" />
<add key="ClientServicesChunkSize" value="28" />
<add key="ClientServicesKeepAliveInterval" value="120" />
<add key="MaxNoOfXMLRecordsToSend" value="5000" />
<add key="MaxImageSize" value="26214400" />
<add key="ClientServicesCredentialType" value="AccessControlService" />
<add key="ACSUri" value="https://login.windows.net/XXX.onmicrosoft.com/wsfed?wa=wsignin1.0&wtrealm=http://dynamicsnavwinclient/&wreply=http://dynamicsnavwinclient/" />
<add key="AllowNtlm" value="true" />
<add key="ServicePrincipalNameRequired" value="False" />
<add key="ServicesCertificateValidationEnabled" value="true" />
<add key="DnsIdentity" value="RootNavServiceCA2" />
<add key="HelpServer" value="NAVO365" />
<add key="HelpServerPort" value="49000" />
<add key="ProductName" value="" />
<add key="UnknownSpnHint" value="(net.tcp://localhost:7046/DynamicsNAV90/Service)=NoSpn" />
</appSettings>
</configuration>
Have anyone clue on this kind of case?
0
Answers
-
Hi,
I think your question is "how can I fix this error when I use single sign on without vpn?"
It would seem to me that the NAV service should be on AccessControlService.
NavUserPassword is mentioned in combination with Azure BUT not for the Azure active dir and single sign on.
Let us know what you find...
Good luck.\\The truth exists in seven versions.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions