May 8, 2006 at 3:52 pm
I just moved a database from 2000 to 2005 and I have the users set up with NT authentication. Everyone is set up the same and works fine except for one individual who gets the following error:
Error: 17806, Severity: 20, State: 2.
SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.11.93]
Error: 18452, Severity: 14, State: 1.
Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.11.93]
Has anyone else ran accross this?
Thanks
May 8, 2006 at 3:58 pm
You might want to see if the user can log on from a different workstation.
I've found SSPI errors tend to be due to something screwed up in AD, either the SQL Server, the workstation, the user, or a combination of them. MSDN has a couple of decent articles on SSPI connection errors and how to troubleshoot them as well.
May 9, 2006 at 9:01 am
This means that the user can not be authenticated whatever the reason is. The reason could be that he can not be authenticated by the domain controller, maybe he logged in with the cached credentials to his workstation and his domain login or passord expired. This issue mostly manifest itself when someone is working using VPN. Or he logged in as a local user etc.
Regards,Yelena Varsha
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply