Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Classic Client NavUserPassword
Modibo
Member Posts: 33
I have a Nav 2018 installation that works well using Windows as the client credentials. I changed the level of service to use NavUserPassword and updated the fingerprint with that of my public cert. Make the change to the clientusersettings.config file in the Windows appdata roaming folder to navuserpassword. When I run the rtc, it asks the user and the password. After entering these, it comes back after a long wait with an error
Identity verification failed for the outgoing message. the expected DNS identity on the remote endpoint was "pyramissrv.pyramisac.local"
, but the DNS provided for the remote ternangle point "pyramissrv.pyramisac.local"
Please help me
Identity verification failed for the outgoing message. the expected DNS identity on the remote endpoint was "pyramissrv.pyramisac.local"
, but the DNS provided for the remote ternangle point "pyramissrv.pyramisac.local"
Please help me
0
Answers
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!