I've setup a new SQL server and am unable to connect to it with SSMS from any machine other than the local machine. When I do, I get an "Unable to generate SSPI context" error.
Googling this tells me the problem is usually that SQL was unable to register a server principle name. However, I do not believe this is the case for a couple reasons:
1. I'm running SQL under a domain account that all our other SQL Servers use, so I know that account should have permission to register an SPN.
2. The SQL Server log contains this entry:
"The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/<machinename>.<FQDN>:<instancename> ] for the SQL Server service."
On shutdown, there is a similar message saying the SPN was successfully unregistered.
3. setspn <serviceaccount> lists:
4. There are no entries in the Windows event logs regarding SPNs.
5. If I shutdown SQL, setspn no longer lists the entry for this server. When I restart SQL, it lists it again.
So all those things tell me SPNs are being registered OK. I have never changed the account SQL runs under, so I doubt there are duplicate SPNs.
Server OS is Windows Server 2008 R2, SQL is 2008 R2 Standard, SP1. There is only a named instance of SQL installed - no default instance.
Anyone have any ideas?