We currently have a problem with a client terminal server connecting to a SQL server via ODBC SQL Server driver.
We have a SQL 2000 server running on Windows 2003, service running as a domain user account.
5 Terminal servers (2x Server 2000, 3x Server 2003) and a bunch of XP client machines connect to this via an in-house application through an ODBC System DSN.
Yesterday, one of the Server 2000 boxes refused to connect, trying to reconfigure the DSN gives "SQLState HY000, SQL Server Error 0, [ODBC SQL Server Driver] Cannot generate SSPI context". The server can however connect to other ODBC connections.
We have tried reinstalling MDAC 2.6 (over the top) and removing/readding the machine to the domain to no avail. I've checked everything is setup the same as the other win2k TS (services etc) and they are. Nothing appears to have changed, nothing relevant in event log on client or server.
Everything I can find points at SPN, however with the other machines connecting fine I can't see this being the case. The SQL server though doesn't have an SPN set, probably due to running as a domain user account.
The problem would appear to be with the client, but I'm out of ideas for where to go with this one. Any help appreciated.