You have to be careful drawing the line between over- and under-provisioning that SQL Login's permissions on server A. Anyone who uses that Linked Server will now be accessing server A as the SQL Login that you entered the credentials for in your Linked Server object. The downside to that solution is that you have to ensure the SQL Login you choose has the appropriate access on server A that supports all your use cases of the Linked Server. This makes it no longer a double hop, from a security perspective. Because now, no longer would it try to pass-through the currently authenticated user's security context, rather it would use the one of the specified SQL Login. One workaround to this issue, when one doesn't want to deal with Kerberos authentication, is to setup your Linked Server to use a dedicated SQL Login, as noted in my linked DBA.StackExchange answer:Īlternatively, if you changed that to "Be made using this security context" and entered the credentials for a SQL Login (as opposed to a Windows Authentication Login) that has access to server A, then that would solve your issue too. There's a ton of information on troubleshooting these issues, among each of the answers posted there. And search more of iStocks library of royalty-free vector art that features Accessibility graphics available for quick and easy download.
#Microstockr istock login fail download
Also please see my related question where I also exhibited a Kerberos issue myself. Download this Login Fail Line Icon vector illustration now.
Please see my answer to the same kind of question recently posted on here, where it was a Kerberos issue. When a Linked Server object works when directly queried from ServerA to ServerB but returns the error " Login failed for user 'NT AUTHORITY\ANONYMOUS LOGIN'" when queried from a third machine, that's usually a sign of a double hop issue as a result from one of the aforementioned root causes.
Likely your two servers are not properly setup correctly either with SPNs or Kerberos delegation, which are usually the two root factors at play for this kind of error and the symptoms you mentioned. 1 We are getting the above error on a SQL 2012 server running Windows Server 2008R2 when connecting using an application and a service account.
0 kommentar(er)
