|
|
|
Grasshopper
 
Group: General Forum Members
Last Login: Wednesday, December 17, 2008 8:18 PM
Points: 12,
Visits: 45
|
|
Good day!
Don't know much about security, but I've created my web service function to return a dataset from SQL Server 2000. When I invoked the function it is giving me this error in the page although I can generate a dataset and connect to the db, only when invoking the web service that I'm getting this.
Need help please.
Thanks
|
|
|
|
|
SSCarpal Tunnel
Group: General Forum Members
Last Login: Today @ 9:04 AM
Points: 4,458,
Visits: 9,192
|
|
usual reason for this error is the sql instance is set to only accept windows authenticated logins but you are trying to connect with a sql authenticated ID. check the properties on your sql instance.
If this is your problem will need to change authentication mode to windows and sql authentication, which will require a sql bounce to take effect.
...or connect with a windows id, which is more secure
---------------------------------------------------------------------
proud member of the 'et al' fraternity.
|
|
|
|
|
One Orange Chip
Group: Administrators
Last Login: Today @ 6:59 AM
Points: 29,490,
Visits: 11,662
|
|
|
|
|
|
SSCommitted
Group: General Forum Members
Last Login: Today @ 4:35 AM
Points: 1,718,
Visits: 3,137
|
|
I'm having the exact same issue when using a linked server on a SQL Server 2005 instance (target is a SQL 2000 instance).
The exact error is:
OLE DB provider "SQLNCLI" for linked server "server\instance" returned message "Communication link failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
Msg 18452, Level 14, State 1, Line 0
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
The user getting this error is able to successfully connect to the target instance on SSMS, while logged on the source sql 2005 instance where the linked server is created.
The linked server is created by the following command (note that security is configured for windows integrated auth., NOT SQL auth.):
EXEC sp_addlinkedserver 'server\instance2k', N'SQL Server';
The user is getting the error above after running:
select * from [server\instance2k].DBNAME.dbo.TableName;
I find this issue odd because, as I mentioned, the user is able to connect with no problems to server\instance2k on SSMS, while logged on the sql2005 instance.
I strongly suspect this is the exact same problem as that posted initially on this thread.
|
|
|
|
|
One Orange Chip
Group: Administrators
Last Login: Today @ 6:59 AM
Points: 29,490,
Visits: 11,662
|
|
|
|
|
|
SSCommitted
Group: General Forum Members
Last Login: Today @ 4:35 AM
Points: 1,718,
Visits: 3,137
|
|
Connections are made using the login's current security context.
So in the following query, the login running the query is the same account in whose context the connection is attempted:
SELECT * from [server\instance2k].dbName.dbo.tblName;
The puzzling thing is that the same user is able to connect to instance server\instance2k through SSMS, while logged on the instance hosting the linked server.
|
|
|
|
|
SSCrazy Eights
Group: General Forum Members
Last Login: Thursday, November 17, 2011 4:09 PM
Points: 9,359,
Visits: 8,864
|
|
Marios Philippopoulos (3/22/2008)
Connections are made using the login's current security context.
So in the following query, the login running the query is the same account in whose context the connection is attempted:
SELECT * from [server\instance2k].dbName.dbo.tblName;
The puzzling thing is that the same user is able to connect to instance server\instance2k through SSMS, while logged on the instance hosting the linked server.
In your case it is pretty clear what the problem is (not so clear for the OP, who had less detail). What you are running into is almost certainly the "Two Hop Rule", which is that under windows domain security, an impersonated security context cannot re-impersonate (that is, it cannot generate the same impersonation on another server).
This is relevant because when you connect from a client to the SQL Server, it impersonates you to generate the security context. In order to get to the linked server using Trusted connections, the security context of your server session would have to be re-impersonated on the target server, and that is not allowed. So even though you can connect directly from your client to both servers, you cannot connect from you client to the first server and then through that to the linked server, because that would be a two-hop impersonation.
The way to test to see if this is really the problem is to find a way to get a session on your SQL server without it having to be impersonated and then try to connect to the linked server from there. I know of two ways to do this:
1) Log on to your server at the console or through Remote Desktop, then run your client to connect to the SQL server on the same box; then connect through it to the Linked Server; it should work now. OR..
2) Write a stored procedure that tries to connect to the linked server and run it using the SQL Agent making sure the the Run As.. is set. (Actually, I am not sure that this still works under Sql2005..)
If you ask Microsoft, they will say that the solution to this problem is Kerberos, but I have yet to see anyone successfully use Kerberos to address this problem in a complex multi-domain corporate enterprise network.
The solution that everyone ends up using is SQL Logins for server-to-server communications. Not ideal, and not a secure as anyone would like, but it does work.
-- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
Proactive Performance Solutions, Inc. "Performance is our middle name."
|
|
|
|
|
SSCommitted
Group: General Forum Members
Last Login: Today @ 4:35 AM
Points: 1,718,
Visits: 3,137
|
|
It is indeed as you say.
When running the same SELECT linked-server query while RDP'd directly on the source server (the server instance to which the linked server is added) it works! The error occurs when running the query while connected remotely to the server (through SSMS).
So it looks like it is indeed a double-hop integrated authentication issue.
We are running this query from a SQL job so we just need to give the SQL Agent account sufficient privileges on the target instance for it to be able to view the data.
|
|
|
|
|
SSCrazy Eights
Group: General Forum Members
Last Login: Thursday, November 17, 2011 4:09 PM
Points: 9,359,
Visits: 8,864
|
|
|
|
|
|
SSCommitted
Group: General Forum Members
Last Login: Today @ 4:35 AM
Points: 1,718,
Visits: 3,137
|
|
rbarryyoung (3/24/2008)
Marios: Glad I could help. I lost many days to this problem the first time that I tripped over it.
Thank you!
This problem rears its ugly head in many different ways. It occurs when I attempt to open an SSRS report on my local workstation that connects through Windows auth. to a production instance and surveys user-database permissions. To resolve I need to create a special SQL login with sysadmin permissions on the instance! The alternative would be to map that login to EVERY single user database with db_datareader permissions, something hard to pull off logistically (and messy).
So at the moment I'm stuck with a less than ideal scenario, and I want to try the Kerberos-auth option...
|
|
|
|
