I am in the process of testing DynamicsNav 2013, for go-live roll out in about a week.
I am at the point of testing the Jet Essential Connection to the new Nav RTC and have hit a wall.
I have successfully configured the Data Source Settings using the IP address of the Dynamics Nav RTC server/instance.. However I continue to get a 401-unauthorized error when using the FQDN (fully qualified domain name).
At first this appeared to be a DNS issue, however DNS settings are correct and I can get to the data source from IE by using http://dynamics_RTC_servername:7047/DynamicsInstanceName/WS/systemservice at which point a username/password dialog pops up and entering the username/password I am using on the test server takes me to the default XML code as it should.
So I am guessing there is something in IIS that is causing this issue, does anyone have a clue what it might be?
Date
Votes
2 comments
-
Jet Reports Historic Posts Hi,
What type of authentication are you using for Dynamics NAV 2013? Windows, User Name, Nav User Password, or Access Control Service authentication?
Regards,
Hughes -
Jet Reports Historic Posts Windows level Authentication,
all users are set in groups, all groups have the NAV permissions, the groups are assigned as Windows Groups in Departments\Administration\IT Administration\General\Users
Groups get the Nav permissions, Users are added to the Groups in Active Directory and Windows Authentication is used (been this way since Nav 4.0 sp3).
–
As stated everything works correctly when the IP address is used, the issue presents itself when using the FQDN.. I thought it was a DNS issue, but all the DNS settings are fine.. It appears to be an IIS issue, I have enabled both anonymous and windows authentication on IIS for the Nav server and tried a couple different combinations of them being on/off, with no success, and yes the bindings are correct for the Port/NIC in IIS.
Please sign in to leave a comment.