Hi Team,
When the client run web client because they are using windows 7. They see not secure beside http:ms-dynamics:8080/DYNAMICSNAV110, and I tried to change it https but I was receiving “the site can’t provide secure connection” with https:ms-dynamics:8080/DynamicsNAV110 after follow the link below https://suvidhablogpost.wordpress.com/2014/09/03/securing-the-nav-web-client-connection-with-ssl/
With http:ms-dynamics:8080/dynamicsNAV110
This is the setting for https
After the setting for https:8080
After the setting for https:443
I discovered my web client was not installed. And I tried to install it but all in vein
Hi,
check the setup on NST for Web client. it has to be set to SSL and you need to have SSL certificate.
For test you can issue your own SSL certificate, but for production you better purchase SSL certificate from local authorities.
I installed NAV 2018 web Client, with the follow screenshot below
After I restarted the system there is no web client under the program file - Microsoft Dynamics NAV- NAV110.
But i have installed NAV 2017 with its web client but install NAV 2018.
What can I do to have NAV 2018 web client installed?
You are not telling everything that is needed - So how is your setup?
One NAV 2017 and One NAV 2018 on the server? (nothing is needed to install on the clients.)
The two webclients on the server is installed?
Your “only problem” is that it is not secure?
Do you have a SSL-certificate? - which is required to when a secure connection is needed?
Is the certificate installed as trusted Root Certificate on the server?
What is the DSNAME on the certificate?
Do you get the NOT SECURE warning both on the inside and outside of the network on the clientside?
/NAVspecialist
My first question was on not secure on the client side which DamJanZa gave beautiful advice on live/ production that I should purchase SSL, I generated self-certificate and my second question is I have installed NAV 2017 with client and web client installed but now I installed NAV 2018, it was only the client installed and I also installed separately web client but it does not installed.
Thanks.
As I am not sure on how your NAV 2017 was installed and how you did the NAV 2018 installation - Then my first guess would be that you have probably overwritten the NAV 2017 webclient installation with the NAV 2018 webclient.
You have to see if you have two folders ind C:\inetpub\wwwroot\ - if not it has been overwritten
Secondly you have to look into your config-file (web.config)
You must have a line with
<add key=”DnsIdentity” value=”” />
I appreciate your comments.
After I open the folder for DynamicsNAV100, I seen where to add <add key=”DnsIdentity” value=”” /> but it was different for DynamicsNAV110
Sorry, my mistake, in NAV 2018 and forward you have to take a look in the navsettings.json file
The reason for this is that you are having more than one certificate installed on the servicetier, so you have to tell IIS and NAV which one it is .
This is mine Certificate Name : DESKTOP-T6U5FJC.NAV2018.local, System Name : DESKTOP-T6U5FJC. Til with the same error
Try moving it from //DnsIdentity line to DnsIdemtity
the //line is a commentline…
I just noticed and it’s done. I’m running two NAV Instances separately from Microsoft Dynamics NAV Administrator where DynamicsNAV110 is for the webclient and the second one for the windows, both are looking at the same database. Once I change the Credential Type : UserName for the Instance DynamicsNAV110 and run the http://localhost:8080/dynamicsnav110/, it will displayed “There is a communication protocol mismatch between the client and the server” on my Local (System), immediately I change the Credential Type : Windows it will connect.
Stil having challenge with not secure with https://localhost:8080/dynamicsnav110 this site can’t provide secure connection while https://localhost:443/dynamicsnav110 Your connection is not private.
Thanks
