Connection Error SQL Server Error 10060 / 17

Hello,
I have the following error from one workstation connecting to a sql server :
SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/IP
sockets]Connection Open (Connect())
SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP soc
kets]SQL
Server does not exist or Access Denied.
My Server runs Windows 2003 with SQL Server 2000.
I used to have 4 Windows 2000 workstations connecting to the SQL server,
plus Windows 98 workstations and everything worked fine. Recently, the
server was 'hardened' and since then, two out of the 4 Windows 2000
workstations cannot connect to the SQL Server, giving me the error message
mentioned above. No problem has been experienced on the Windows 98
workstation.
Since only two Windows 2000 workstations (out of 4) are experiencing
problem, I cannot pinpoint the server as being 'faulty', it has to be the
machines but where could the problem lie? Of course, I could not install the
critical update patch (mentioned in this forum) on the workstations since it
is meant for the server and anyway, the server is not really the issue here
since other workstations can connect to the sql server.
I tried installing MDAC 2.8 on the 'faulty' workstations, changed nothing.
Is it a dll issue? a security issue?
Please help, this problem has lasted for nearly three weeks and is a real
handicap for the work.
Thanking you in advanceNanou wrote:
> Hello,
> I have the following error from one workstation connecting to a sql server
:
> SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/I
P
> sockets]Connection Open (Connect())
> SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP s
ockets]SQL
> Server does not exist or Access Denied.
> My Server runs Windows 2003 with SQL Server 2000.
> I used to have 4 Windows 2000 workstations connecting to the SQL server,
> plus Windows 98 workstations and everything worked fine. Recently, the
> server was 'hardened' and since then, two out of the 4 Windows 2000
How was the server "hardened"? Was a firewall rule established that is
only allowing the two workstations to connect? Was TCP/IP disabled?|||Nanou wrote:
> Hello,
> I have the following error from one workstation connecting to a sql server
:
> SQL Server Error 10060 [Microsof][ODBCSQL Server Driver][TCP/I
P
> sockets]Connection Open (Connect())
> SQL Server Error 17 [Microsof][ODBCSQL Server Driver][TCP/IP s
ockets]SQL
> Server does not exist or Access Denied.
> My Server runs Windows 2003 with SQL Server 2000.
> I used to have 4 Windows 2000 workstations connecting to the SQL server,
> plus Windows 98 workstations and everything worked fine. Recently, the
> server was 'hardened' and since then, two out of the 4 Windows 2000
How was the server "hardened"? Was a firewall rule established that is
only allowing the two workstations to connect? Was TCP/IP disabled?|||Thanks Tracy for your answer.
Yes a firewall is established but, no there is no limitation in the number
of workstations connecting to the server. TCP/IP is enabled.
Actually, I found the solution to the problem on the net itself. It seems
this connection problem can occur after a firewall is put into place.
http://www.webservertalk.com/printthread.php?t=976301
The fix that worked was to delete the entry for the SQL Server in the
following registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\ Client\ConnectTo\DSQUERY
See http://support.microsoft.com/default.aspx?kbid=328306
cheers,
nanou
"Tracy McKibben" wrote:

> Nanou wrote:
> How was the server "hardened"? Was a firewall rule established that is
> only allowing the two workstations to connect? Was TCP/IP disabled?
>