You’re offline. This is a read only version of the page.
Hi,
We are currently implementing Nav 2015 on Azure and all is going well. We now have more people working on it so I thought I could just setup a new machine with the Nav development environment installed. The new server connects to the database perfectly fine and so does the client, once the config file is changed.
The issue I am having is when the development environment calls the client it uses incorrect instance parameters. Instead of using hostname.domain.com it just uses the hostname. I am assuming its getting this information from the database. If I change it to the FSDN it says "The Server Instance specified in the option windows is not available for this database" then changes it back. If I hard code the ip and hostname or create a dns server and add the entry I get the following error:
The client could not establish a connection to the Microsoft Dynamics NAV Server Reason = "Configuration setting 'Dnsidentity' has invalid value Description= "identity check failed for outgoing message. The expected DNS identity of the remote endpoint was 'hostname' but the remote endpoint provided DNS claim 'hostname.domain.com'.
Anyone know how I can resolve this>
*This post is locked for comments
Yes can connect fine as long as I use the FQDN. Its when I am in the development client, its doesn't use the FQDN and wont connect, it also wont let me change it.
Are you able to access the RTC client ? on the NST instance what is the server address used ?
Yes they are all correct apart from the 49000 Help which I cant add to Azure.
Can you check the endpoint on Azure and make sure you have all of the below defined
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,188
Super User 2024 Season 2
#2
Martin Dráb
230,030
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (