We solved this by disabling Windows Defender Credential Guard
We are seeing an issue with SQL Linked Servers and Windows 11. Kerberos doesn't seem to be passing credentials
All of our existing Windows 10 computers work fine, but the newer Windows 11 computers throw the anonymous error on the linked server. Kerberos is configured correctly along with SPN's. We can't seem to figure out why Windows 11 can't do a double hop using Kerberos.
Actually, I think that is more an effect of some connection pooling going on.
In any case, I don't have any access to any environment where I can test this, but I wanted to check out auth_scheme, so that the problem is not in that end. Hopefully, someone who works in a domain environment and knows Kerberos well can chime in.
Sign in to comment