Hi RayMiller-7311,
Thanks for your reply.
I am guessing if this may be delegation or Kerberos issue.
We can using following query to check if the connection is using Kerberos:
select session_id,auth_scheme from sys.dm_exec_connections
If the connection is using Kerberos authentication, please make sure SQL Server service account was trusted for delegation in AD. Please refer to this doc which might help.
If the connection is not using Kerberos authentication, please check if both the following conditions are true:
- The client and server computers must be part of the same Windows domain, or in trusted domains.
- A Service Principal Name (SPN) must be registered with Active Directory, which assumes the role of the Key Distribution Center in a Windows domain. The SPN, after it's registered, maps to the Windows account that started the SQL Server instance service. If the SPN registration hasn't been performed or fails, the Windows security layer can't determine the account associated with the SPN, and Kerberos authentication isn't used.
To register the SPN for SQL Server Service account, please refer to this doc which might help.
Best Regards,
Amelia