SQL Server SSPI handshake failed Error

One, error content
Logon Error: 17806, Severity: 20, State: 14.
Logon SSPI handshake with Error code 0x8009030c, State 14 while fading a connection with integrated security; The Connection has been closed. Reason: AcceptSecurityContext failed. The Windows Error code indicates the cause of failure. The logon attempt failed [CLIENT: 192.168.1.3]
Logon Error: 18452, Severity: 14, State: 1.
Logon Login failed. The Login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 192.168.1.3]
 
Second, report the cause of the error
The error message should be related to the domain account. The domain account is not trusted, so Windows authentication cannot be used.
It is commonly seen in 192.168.1.3 that user A was used to connect to the database (the case encountered was the domain account), and then the password of user A was changed, but the old password was still used in 192.168.1.3 to try to connect, resulting in an error in login verification.
In addition, user A’s domain account has been locked, and this error will be reported when logging in.
 
3. Solutions
Login 192.168.1.3 Server disconnects the previous user A
or
Log in to the database server and kill A user’s connection
 
reference
http://www.secretgeek.net/boring_sql_one
https://blogs.msdn.microsoft.com/docast/2016/02/11/common-sspi-handshake-failed-errors-and-troubleshooting/

Read More: