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
2009 3 tier NTLM authentication error
leegeorgeHughes
Member Posts: 26
Hello,
Im currently ](*,) here and was wondering if someone could help?
I have a site that is running 2009R2 classic client but we are using the service tiers for outlook synchronisation and a mobile warehousing add on, all of these service tiers run correctly and are stable.
The service tiers are installed on a different machine to the SQL server, and are using the same domain account to run as the sql server is.(all of the original service tiers have SPN's setup and so does SQL - these have been working correctly for 2+ years)
I have setup a new service tier (and the relevant SPN's) as we need to call a codeunit via webservices using PHP so have had to enable WebServicesUseNTLMAuthentication" value="True" but when i try to connect to the webservice WSDL using a browser I get the error "The login failed when connecting to SQL Server XXXXXXXXXX'
If i look at the event viewer on the SQL server I see that "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 192.168.1.105]" which suggest that impersonation isn't being used when connecting to SQL
If i connect the RTC client to the new Service Tier using the same windows login as Im am trying to use in the browser it connects to the database successfully.(which sort of suggest that delegation is working on the new service tier at least for port 7046)
I appreciate that the RTC client uses a different port (7046) to the WS (7047) but i have set SPNS for both ports.
Does anyone have any gems of wisdom that will help me please??
Many Thanks
Lee
Im currently ](*,) here and was wondering if someone could help?
I have a site that is running 2009R2 classic client but we are using the service tiers for outlook synchronisation and a mobile warehousing add on, all of these service tiers run correctly and are stable.
The service tiers are installed on a different machine to the SQL server, and are using the same domain account to run as the sql server is.(all of the original service tiers have SPN's setup and so does SQL - these have been working correctly for 2+ years)
I have setup a new service tier (and the relevant SPN's) as we need to call a codeunit via webservices using PHP so have had to enable WebServicesUseNTLMAuthentication" value="True" but when i try to connect to the webservice WSDL using a browser I get the error "The login failed when connecting to SQL Server XXXXXXXXXX'
If i look at the event viewer on the SQL server I see that "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 192.168.1.105]" which suggest that impersonation isn't being used when connecting to SQL
If i connect the RTC client to the new Service Tier using the same windows login as Im am trying to use in the browser it connects to the database successfully.(which sort of suggest that delegation is working on the new service tier at least for port 7046)
I appreciate that the RTC client uses a different port (7046) to the WS (7047) but i have set SPNS for both ports.
Does anyone have any gems of wisdom that will help me please??
Many Thanks
Lee
0