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/
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:
- SQL Server “login failed for user ‘domain account”. [sqlstate 28000] (error 18456). “Problem solving
- SQL server error 15404 solution
- SQL Server 2008 login 4064 error solution
- SQL 2005 remote connection error (provider: SQL network interface, error: 28 – the server does not support the requested protocol
- Solution to SQL Server Error: 4064
- SQL Server 2008 R2 MSSqlServer failed to start. Error code 17058
- SQL Server 2008 18456 error and SA unable to login solution
- Prompt SQL server error 15023 solution memo when modifying user mapping
- Unable to install SQL Server (setup.exe), VS Shell installation has failed with exit code 1638.
- failed: Error during WebSocket handshake: Unexpected response code: 400
- SQL Server 2005, unable to log in, forget sa password, 15405 error!
- gnutls_handshake() failed: A TLS fatal alert has been received
- 12-web security — error injection based on SQL Server — and, convert, cast
- Deployment project websocket failed: error during websocket Handshake: unexpected response code: 400
- JDBC connect to Sql Server to connect to the database–The TCP/IP connection to the host localhost, port 1433 has failed
- Solution of error converting data type varchar to datetime in SQL Server
- WebSocket failed: Error during WebSocket handshake: Unexpected response code: 400
- git clone https:// gnutls_handshake() failed: The TLS connection was non-properly terminated.
- failed: Error during WebSocket handshake: Unexpected response code: 200
- SSL handshake failed: SSL error: illegal key usage detected in the certificate