Hi Thomas
Since my last post I found out that I edited my hosts file wrong. So now the name NAVserver correctly resolves to the IP of the NAVserver of the Azure vm.
The error that i’m now getting is:
“Identity check failed for outgoing message. The expected DNS identity of the remote endpoint was ‘NAVserver’ but the remote endpoint provided DNS claim ‘mydomain.com’. If this is a legitimate remote endpoint, you can fix the problem by explicitly specifying DNS identity ‘mydomain.com’ as the Identity property of EndpointAddress when creating channel proxy.”
That is the same error I got before editing the CustomSettings.config of my users NAV windows client and using mydomain.com as the DNSidentity value.
But the Dev environment doesn’t use that CustomSettings.config file and I see no place to specify that in the options in the dev environment??
That is the only thing missing.