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
Have anyone gotten NAV 2009 R2 Webservice Tier to work with NTLM if all tiers on seperate machines?
Eboy82
Member Posts: 25
Hi,
I and some other people have spent days trying to figure out, and we starting to believe that NTLM Support in 2009 R2 does not work if SQL and WS Service is not located on same physical machine. Can anyone confirm or reject this suspicion?
We have 1 SQL Server running on Network Service on Machine A)
We have 1 NAV RTC+WEB Service Tier running on Network Service on Machine B )
We have regular RTC Clients on Machine C)
We are facing an integration challenge, where we must allow some external PHP website to call the WEB Service layer. This has to be with NTLM as I understand, but if we enable NTLM in the customconfig file and restarts the service tier, webservice tier does not work from anywhere.
We get "Login failed when connecting to SQL Server"
We notice in event log of SQL Server on Machine A, that it display anonymous user, and not the user that was authenticated from Machine C's webbrowser.
In the event log of machine B, that it displays the credentials of the user, and says NTLMv2. But on Machine A, it says something about NTLM V1.
RTC Clients works just fine from Machine C, no matter if NTLM is enabled for webservice in custom.config file.
We are considering if above is true, to install service tier on SQL server as well, or make a proxy web-service. But we can't understand why it is not mentioned anywhere if it's true it doesnt't work with NTLM unless SQL + WS Service share machine.
I and some other people have spent days trying to figure out, and we starting to believe that NTLM Support in 2009 R2 does not work if SQL and WS Service is not located on same physical machine. Can anyone confirm or reject this suspicion?
We have 1 SQL Server running on Network Service on Machine A)
We have 1 NAV RTC+WEB Service Tier running on Network Service on Machine B )
We have regular RTC Clients on Machine C)
We are facing an integration challenge, where we must allow some external PHP website to call the WEB Service layer. This has to be with NTLM as I understand, but if we enable NTLM in the customconfig file and restarts the service tier, webservice tier does not work from anywhere.
We get "Login failed when connecting to SQL Server"
We notice in event log of SQL Server on Machine A, that it display anonymous user, and not the user that was authenticated from Machine C's webbrowser.
In the event log of machine B, that it displays the credentials of the user, and says NTLMv2. But on Machine A, it says something about NTLM V1.
RTC Clients works just fine from Machine C, no matter if NTLM is enabled for webservice in custom.config file.
We are considering if above is true, to install service tier on SQL server as well, or make a proxy web-service. But we can't understand why it is not mentioned anywhere if it's true it doesnt't work with NTLM unless SQL + WS Service share machine.
0
Comments
Follow ms guidelines and stay focused on delegation and spn in AD.
2009 are just stupid in 3 tier setup.
Thanks for the response, also with NTLM enabled and Network Services running both SQL/NAV?
What build no. if I may ask, this client is running 33046.
It's such a nightmare this setup with SPN,NTLM
With kind regards,
Povl
Indeed, but it is possible.