Did you try SQL Server IP address instead of server name in the DSN (for troubleshooting)?

>
>Thank you for the quick response.
>
>>What application do you use to access SQL Server?
>
>The driver I am creating is used by an application written in Visual FoxPro 9.0 sp2. If I try to run the application or run a SQLCONNECT() to the ODBC connection from the command window of VFP (on the effected client) I get the same error message.
>
>Interestingly enough, there is a Visual Basic 6.0 based application that uses ADO without error. I've spoken to the chap who wrote the code and all he does is set a connection string and then open the connection. The string he uses is, in theory, no different to the elements of my ODBC connection; incorporating Server Name, Database Name and a Trusted Connection. This works fine within the Visual Basic application.
>
>When creating my ODBC connection I specify the Server Name, click Next to a default of Windows Authentication and can get no further. Clicking Next just results in the error.
>
>>Can you access it from SSMS?
>
>I haven't tried to run SSMS on the client yet. Every other desktop machine in the building connect to the SQL servers fine. Either through SSMS (on the Developers' machines) or from the Visual FoxPro application through ODBC.
>
>The effected client is the only 64bit Windows 7 PC on the network at present. I have set up 2 others in the past but these were notebooks and are currently out on the road.