I'm getting this error message when I try to sign into SQL 2016, using Windows Authentication, from a Windows 10 Pro machine, using SSMS 17:
"The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server, Error: 0)"
This appears to have begun shortly after upgrading SQL 2016 to SP1. And I appear to be the only one affected.
From the same Windows 10 Pro client machine, using SSMS 17, I can sign into another SQL Server 2016 on the same domain, using Windows Authentication, and into a SQL Server 2008, also using Windows Authentication.
The SQL 2016 in question is on Windows Server 2016. And from the Windows Server 2016 where the SQL 2016 lives I can sign into the server just fine using Windows Authentication.
I'd be appreciative of any help or tips that could point me in the right direction.
Thank you!