I am trying to create an ODBC Connection from a new installation of Windows 7 Professional 64bit to a SQL 2008 Server that is registered on the same domain. When using SQL Authentication the connection works, however the application that uses the ODBC connection requires Windows Authentication to be used.

It is important to note that I am using the 32 bit connection manager to set my ODBC data sources. (c:\windows\sysWOW64\odbcad32.exe) to avoid conflict between a 64bit DSN and my 32 bit SQL Server.

When I try to use Windows Authentication I receive the following message:

Connection failed:
SQLState: 'HY000'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver] Cannot generate SSPI context

Now I've received this error message elsewhere due to DNS issues but in this case I have done all that I can to eradicate DNS as being the cause. The client PC can resolve the server name and IP via DNS. I've also checked and double checked the DNS servers and flushed the cache, just to be sure.

I've scoured the internet over the past couple of days, looking for a solution to the problem; I've processed and digested http://support.microsoft.com/kb/811889 along with responses from this forum and also results from Google.

The time on the client, the SQL Server and the domain controller are all the same; likewise the SQL Service account has permission to read and write the Server Principal Name (of which there are no duplicates).

Nothing jumps out from either the SQL logs or the clients event logs.

I have 3 SQL Servers all on the same domain and all accessed from a number of desktops running Windows XP or Windows 7, the client I am working on gets the same message regardless of which of these 3 servers are connected to.

I find myself well and truly stumped. Can anyone recommend any other avenues of investigation for me to follow?

Many thanks in advance for any help or suggestions that can be provided.