 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / General / Security / December 2005unable to run store procedure on remote server (win2k3sp1, sql2k sp4)
Hi all Need some help on this, and I could not find an answer after going through newsgroup/google. I have 2 servers, both on win2k3sp1, and sql2k sp4. I am having problem doing RPC of store procedures from either server to the other when I am using window authentication in query analyzer (both are on the same domain, using same domain user name login). the error I am getting is : could not connect to server 'dev2' because 'null' is not defined as a remote login at the server. However if I use sql login in the query analyzer, things are fine. I've checked and make sure both are registered to each other as the remote server and checked RPC and using remote login mapping use "same name". I've also tried on local security policy to all impersonation of the particular domain user on each machine. I've rebooted both machines after the settings changes etc.. It seems the remote login mapping is not working at all. any idea/help is very much appreaicated . thanks in advance. Justin Hi Have you tried dropping the remote sever login and seeing what happens? John > Hi all > [quoted text clipped - 22 lines] > > Justin Hi John How do I drop the remote server login? e.g. from server A's sql query analyzer to do a query to run server B's store procedure. I don't think I can drop any server login in doing so. Justin > Hi > [quoted text clipped - 28 lines] >> >>Justin Hi The notation is a bit confusing!!! Check out sp_droplinkedsrvlogin in Books Online to drop them, and sp_helplinkedsrvlogin to show them. From sp_addlinkedsrvlogin in BOL: Rather than having to use sp_addlinkedsrvlogin to create a predetermined login mapping, SQL Server can automatically use the Windows NT security credentials (Windows NT username and password) of a user issuing the query to connect to a linked server when all these conditions exist: a.. A user is connected to SQL Server using Windows Authentication Mode. b.. Security account delegation is available on the client and sending server. c.. The provider supports Windows Authentication Mode (for example, SQL Server running on Windows NT). John > Hi John > [quoted text clipped - 36 lines] >>> >>>Justin Hi John thanks for the hint, though by dropping the linkedsrvlogin did not help in my case, I did managed to get around by manually addremotelogin and addlinkedsrvlogin and do some user mapping in them. now it works, so it seems to be the problem with addlinkedsrvlogin or maybe one of the three condition was not met, I suspect the condition b could be the cause, but I am not sure how to verify it. I figure it could very much to do with some security related setting/policy in my win2k3. thanks very much again. at least now I get something working. Cheers Justin > Hi > [quoted text clipped - 56 lines] >>>> >>>>Justin Hi Justin If both servers and the logins are on the same domain then B should be ok! It sounds like the accounts did not have logins on both servers? John > Hi John > [quoted text clipped - 74 lines] >>>>> >>>>>Justin Interestingly, they are using the same domain login account. so I suspect it is to do with the w2k3 setup etc. Justin > Hi Justin > [quoted text clipped - 82 lines] >>>>>> >>>>>>Justin |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.