July 25, 2005 at 4:58 am
When the application is on the same computer as an instance of SQL Server 2000 then okay this is working fine but When the application is on a separate client, a network IPC, such as TCP/IP or Named Pipes, is used to communicate with SQL Server. then i have geting problem.
Please give me solution.
July 25, 2005 at 7:32 am
What sort of application is it? Are users connecting to the application using Windows authentication?
K. Brian Kelley
@kbriankelley
July 25, 2005 at 7:37 am
yes Windows authentication
July 25, 2005 at 7:48 am
You have a "double hop" issue.
If you are in an Active Directory domain, you have the option of using Delegation, but this has security concerns. You'll probably want to get with whatever group administers your Active Directory if you want to go down this road.
If you are on a Windows NT 4.0 domain or delegation isn't an option there are only three options left for you to consider:
1) Host the application on the SQL Server.
2) Make the connection to the application something other than Windows authentication.
3) Make the connection to SQL Server a SQL Server login rather than a Windows authencation connection.
INFO: Accessing SQL Server with Integrated Security from ASP (176377)
K. Brian Kelley
@kbriankelley
July 26, 2005 at 1:27 am
Hi, I witnessed this behavior as well using a linked server. The group was granted access to both Sql Server instances, the linked server was setup to use "Be made using the login's current security context". This setting doesn't work for AD groups without enabling delegation, the actual windows login is not passed during the connection setup and the login attempt fails. To fix your problem, either have the AD team turn on delegation , or configure a sql server authenticated login. Both have pros and cons.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply