I have one machine (mine) on a network that gets the above message running the same connect code that other machines run successfully. I am unable to use our FoxPro ADO application or Enterprise Manager. I pulled ODBCPING.EXE from the SQL Server disk and found out that I could PING the server successfully, but ODBCPING consistently failed with this message.

COULD NOT CONNECT TO SQL SERVER

SQLState: 08001 Native Error: 17
Info. Message: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

SQLState: 01000 Native Error: 10061
Info. Message: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).

We know that "SQL Server does not exist or access denied" is inaccurate because the same login is successful from other computers. Also when we add a new SQL Server Registration under Enterprise Manager, the server shows up on the list of choices.

Interestingly, based on a Knowledge Base article, we searched for TCPPORT in the registry, found it had a value other than 1433, changed the value and fixed the problem once. The problem returned soon after, but the correct value of 1433 was still in the TCPPORT registry setting. We are using Windows 2000 and SQL Server 2000 and have uninstalled and reinstalled the client tools.