This kind of mistake is really a headache, if you encounter it is not a headache, please first look at Microsoft to give the error of this KB811889.
In general, I encountered this kind of error is directly give up, rerun Sysprep and then install the required software again. However, I have no way to return this time. It took several days to try to solve a SQL mirror problem, and the result of SQL Mirror resolved, resulting in this "cannot Generate SSPI Context" error.
Had to try to solve it.
There are a lot of articles on the Internet, many ways to solve problems. It's the one that solved my problem. The strange thing is that I didn't use Kerberos, just NTLM, but I solved the problem.
The SQL instance that the client is not connected to in my environment is lyncdb1n, and the account that runs the instance is midrange\administrator. Run the following command to view the SPN for the SQL service under my account.
You can see that there is no problem with the instance.
After this configuration, the problem is resolved. SQL Server is already connected to the client.
Resources
===================
That "cannot Generate SSPI Context" headache
http://coffeeandsql.com/2014/05/10/that-cannot-generate-sspi-context-headache/
"Cannot generate SSPI context" error message when connect to local SQL Server outside domain
Http://blogs.msdn.com/b/sql_protocols/archive/2005/10/19/482782.aspx
SQL Server connectivity, Kerberos authentication and SQL Server SPN (Service Principal Name for SQL Server)
http://mssqlwiki.com/tag/cannot-generate-sspi-context/
Client Connection SQL Report "Cannot Generate SSPI Context" error