THE PROGRAM COULD NOT CREATE A CONNECTION TO THE SERVER. DO YOU WANT TO TRY AGAIN?

(0) Share

Report

Posted on by Community Member

Hello guys,

I'm still stuck on this and would really appreciate your help.

I have Navision 2016 installed on my server and client machines need to access it over a LAN. Client Machines on-site (where the server is located) have been connecting just fine but the other client machines in a different location have a problem establishing a connection with the server. I am implementing NavUserPassword as the credential type.

Anyone with a solution???

8244.nav.PNG

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (0)

Suggested answer

Mohana Yadav 60,993 Super User 2025 Season 2 on at

Like (0)

Report

Did you check by pressing No? which opens window to enter server address?

by default it connects to DynamicsNAV90 service and if our service name is different?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes Mohana, I've tried that several times where the "Server address" value is 172.17.10.3:7100/OLLIN2016.

And this is what my ClientUserSettings config file looks like:

<?xml version="1.0" encoding="utf-8"?>

<configuration>

<appSettings>

<add key="Server" value="172.17.10.3" />

<add key="ClientServicesPort" value="7100" />

<add key="ServerInstance" value="OLLIN2016" />

<add key="TenantId" value="" />

<add key="ClientServicesProtectionLevel" value="EncryptAndSign" />

<add key="UrlHistory" value="172.17.10.3:7100/OLLIN2016" />

<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="NavUserPassword" />

<add key="ACSUri" value="" />

<add key="AllowNtlm" value="true" />

<add key="ServicePrincipalNameRequired" value="False" />

<add key="ServicesCertificateValidationEnabled" value="true" />

<add key="DnsIdentity" value="NavServiceCert" />

<add key="HelpServer" value="BRANCHMGRPC" />

<add key="HelpServerPort" value="49000" />

<add key="ProductName" value="" />

<add key="UnknownSpnHint" value="(net.tcp://172.17.10.3:5100/Ollin/Service)=NoSpn;(net.tcp://172.17.10.3:7100/OLLIN2016/Service)=NoSpn;" />

</appSettings>

</configuration>

Was this reply helpful? Yes No
Suggested answer

IshwarSharma 729 on at

Like (0)

Report

If you haven't already then please check the service status in NAV administration is running and not stopped or pending start etc.

If the service is not running then please check for the possible causes which may have stopped the NAV service.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Ishwar, the service is up and running that is why client machines on-site (where the server is) can connect.

Was this reply helpful? Yes No
Suggested answer

Mohana Yadav 60,993 Super User 2025 Season 2 on at

Like (1)

Report

can you check whether you can ping the IP from command prompt?

please check event viewer to identify more details of error.

Was this reply helpful? Yes No
Suggested answer

Jan Veenendaal 510 on at

Like (0)

Report

Looks like a firewall/routing issue. Check if (a) the server address is routed correctly (like Mohana said, using PING or TRACERT), and (b) if port 7100 is blocked somewhere in between.

Was this reply helpful? Yes No
Suggested answer

4BzSoftware 6,073 on at

Like (0)

Report

Hi Eddie,

You need to allow incoming port 7100 (may be port 5100 as your history info) on NAV Server (172.17.10.3). Temporarily turn off the firewall for checking.

Was this reply helpful? Yes No
Suggested answer

Alexander Ermakov 28,096 on at

Like (0)

Report

If other client machines on-site are able to connect, then it might be a firewall issue, or the other client machines are not in the network where server is running, or there might be malware protection software preventing the connection.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks guys, but I've tried all your solutions and no reliable connection has been established, however, one login session was successful and I noticed that this was when I could remote connect to the server. After the remote connection broke client machines haven't been able to connect to the server anymore.

Was this reply helpful? Yes No
Suggested answer

Priyantha herath 10 on at

Like (0)

Report

please try below actions

(1) agin restart pc or vm

(2) login your Navations server and open nav administrator console then select your instance and right-click

then restart your instance. now you can log in in your system..

Was this reply helpful? Yes No