This post was formerly published at my beloved old blog "On the quest of a DBA's adventure......"
Try to look at the problem on the SSPI handshake issue. The following error message was reported from time to time:
“"SSPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed"”
Checked on Google, there are a number of forum posts pointing the problem may resulted from that 0x80090311 error refers to "No authority could be contacted for authentication" which means the user cannot contact AD to get a Kerberos ticket. Let check with my network admin buddy to see if anything to do with AD and Kerberos. It is not necessary something you can rectify here, because it could be the user just ignore the password policy in regards to password change and Kerberos just has enough with their neglect and kick them off.
Here are some articles on Kerberos troubleshooting:
Forum post on SQL Server 2005 connection problems from SQL Server Central
Blog post on Kerberos Adventures - Useful Information Links from Michael Stephenson's blog
Blog post on Troubleshoot Connectivity Issue with SQL Server Express 2005 from MSDN Blog - SQL Protocols
No comments:
Post a Comment