Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
RTC-Acces through trusted domain
RDanylyschyn
Member Posts: 2
Hello,
we've installed a three-tier Navision structure (following the documentation, with SPNs and so on). This works very fine in this domain. But we have a second domain (with domain-trust) where also RTC-Clients should be placed (with access to the NRT- and SQL-Server).
SQL- and NRT-Service have two different domain accounts with different SPNs
Here the following problems are appearing:
1. ClientUserSetting.Config:
AllowNTLM=false
ServicePrincipalNameRequired=true
leads to the message: 'Die Konfiguration des Dienstprinzipalnames (Delegierung) wurde nicht ordnungsgemäss festgelegt. URL der Serververbindung: 'net.[url=tcp://xxxx.yyy.com/DynamicsNav/Service...']tcp://xxxx.yyy.com/DynamicsNav/Service...'[/url]
(Sorry, I've the message in german only. A rough translation:
The configuration of the serviceprincipalname (delegation) is wrong. URL of the server connection...)
2. ClientUserSetting.Config:
AllowNTLM=true
ServicePrincipalNameRequired=true
leads to the message: The login failed when connecting to SQL Server zzzz.yyy.com.
I think the SPN-configuration is ok since in the first domain the RTC-access is ok.
Has anybody a similar installation working? Or any idea?
we've installed a three-tier Navision structure (following the documentation, with SPNs and so on). This works very fine in this domain. But we have a second domain (with domain-trust) where also RTC-Clients should be placed (with access to the NRT- and SQL-Server).
SQL- and NRT-Service have two different domain accounts with different SPNs
Here the following problems are appearing:
1. ClientUserSetting.Config:
AllowNTLM=false
ServicePrincipalNameRequired=true
leads to the message: 'Die Konfiguration des Dienstprinzipalnames (Delegierung) wurde nicht ordnungsgemäss festgelegt. URL der Serververbindung: 'net.[url=tcp://xxxx.yyy.com/DynamicsNav/Service...']tcp://xxxx.yyy.com/DynamicsNav/Service...'[/url]
(Sorry, I've the message in german only. A rough translation:
The configuration of the serviceprincipalname (delegation) is wrong. URL of the server connection...)
2. ClientUserSetting.Config:
AllowNTLM=true
ServicePrincipalNameRequired=true
leads to the message: The login failed when connecting to SQL Server zzzz.yyy.com.
I think the SPN-configuration is ok since in the first domain the RTC-access is ok.
Has anybody a similar installation working? Or any idea?
0