I'm working on some scripts that will run on a monitoring server and connect to several data servers to return information such as job status, etc. We also use linked servers for replication, etc.
We use mixed authentication, however, I would like to change our linked servers to use the current security context based on AD authentication instead of connecting with the 'sa' account. When I set a linked server to use the current security context, I get:
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. (.Net SqlClient Data Provider)
We manage our Windows security through AD groups rather than adding individual AD logins to SQL. So if I'm connected to a server through Enterprise Manager using Windows Authentication, it sees me as a part of the DBA group rather than an individual AD user. Since my individual Windows account hasn't been added under the remote server's logins, could that be causing this?
I'm pretty well just grasping at straws here, but I want to move away from using the 'sa' account for our remote connections. Any advise is most welcome.
March 27, 2009 1:56 PM
March 28, 2009 3:28 AM