May 15, 2008 at 7:09 am
All,
I'm trying to get a SQL Login on Server A to connect to a linked server (Server B). I need the SQL Login to connect as a given Windows login on Server B.
Server B is set up correctly on Server A as a lined server I think - I created the same SQL Login
on Server B to test and I can connect fine when I use the SQL Login as the "Local Login" and click "Impersonate"
The message I get when trying to connect as the remote Windows login is
Login failed for user 'DOMAIN\User'
I've definitely got the domain and password right.
Server A runs SQL 2000, mixed authentication
Server B runs SQL 2005, mixed authentication.
Is what I'm trying to do possible (ie SQL Login -> Remote Windows Login) ? Any ideas on getting around the error ?
May 15, 2008 at 2:32 pm
i have faced the same problem, using sql login on both server did it.
..>>..
MobashA
May 16, 2008 at 1:33 am
Thanks for that Mobasha.
That won't work for me though because I want to run a job on Server B that requires access to a network drive.
May 16, 2008 at 6:02 am
so u want serverA to use like a folder in serverB.
if so u can create table in serverB, use the linkserver to but a command from serverA to serverB,
create a trigger on serverB table and executing the command.
i know its not an easy thing but it might solve ur case.
..>>..
MobashA
May 19, 2008 at 5:13 am
Thanks for the suggestion Mobasha
I think I have a solution now.
I created a sproc on Server B to run the job using EXECUTE AS TheWindowsLogin
I then just link the SQL Logins between the servers (using Impersonate) and grant execute on the new sproc to the SQL Login.
Thanks for your help.
🙂
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply