Here's a screenshot of the original error the user gets when testing the Linked server from within SQL Manamgement Studio: When I run a DCDIAG /q I do see some Kerberos errors, but I'm running into more walls trying to figure out why these occur and where theyr'e coming from: I'm troubleshooting the DC/Kerberos side a bit more.
sql-server-general windows-server-security Hoping someone has some other idea's of things I can try to get this working. I've checked my DC's and I don't appear to be having any replication issues, or Kerberos issues that I can see. They will then see the anonymous logon error, they have the same access I do and I can right-click and "test connection" and I get a "success" response. This error can also be replicated outside of a linked server query by simply running SMS and right-click the Linked server and "test connection". I have a dev environment where users are setup identically, and this issue does not exist for any users, so this is not a permissions issue. Some of my users can run the linked server query's and it works fine (myself included), others get the Anonymous login error, so for some reason it's not passing their logged in credentials across the SQL linked server. I have the correct SPN's created for both SQL servers, when I run "SELECT net_transport, auth_scheme FROM sys.dm_exec_connections WHERE session_id = " I see TCP / KERBEROS, so the SPN's appear to be working (otherwise I might see a NTLM request instead of Kerberos).
The domain service account has delegated privilege's to "any service". Reason: The password of the account must be changed.I have two SQL servers that both run their instances from a domain service account. Reason: The password of the account has expired. An unexpected error occurred during password validation. The password does not meet the requirements of the password filter DLL. The password does not meet policy requirements because it is not complex enough. The password does not meet policy requirements because it is too long. The password does not meet policy requirements because it is too short. The password cannot be used at this time. Login failed for user '%.*ls' Reason: Password validation failed. When a connection cannot be made because of authentication problems, one of the following SQL Server error codes will be available to the application to assist diagnosis and recovery.
0 kommentar(er)
