sql server connect: I've got a SQL2000 server that I need to connect to from a small number of
development boxes. If the dev box is running Windows 2000 SP5, I have no
problem establishing an ODBC connection. If I follow the exact same steps
in trying to establish an ODBC connection on a Windows XP SP2 box, I get:

"Connection failed: SQLState: '01000'
SQL Server Error 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001';
SQL Server Error: 17;
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist
or access denied".

Note that:
1) I get the identical failure on a second Windows XP SP2 box.
2) I've disabled the software firewall as this runs only on an internal,
firewalled network
3) I checked on the SQL server TCP/IP network configuration to see that it
is using Port 1433, and tried disabling the dynamic port in ODBC setup and
using 1433.
None of these have had any effect on the issue.

Anybody have any good suggestions? Seems a bit silly that I need to run
Windows 2000 to connect to a remote SQL 2000 server.

Thanks!

Hi Pierre,

Thanks for your post.

From your descriptions, I understood you are not able to connect SQL Server
via Windows XP SP2. If I have misunderstood your concern, please feel free
to point it out.

As we all know, Windows XP SP2 considers more security issues, we will have
to do some configuration before connect to the SQL Server. Please refer the
Knowledge Base article below for more information.

How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
http://support.microsoft.com/?id=841249

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!


Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

The articles describe opening up the Windows XP SP2 firewall to allow =
clients to access a SQL instance on the XP SP2 box. They do NOT address =
my issue, which is that using XP SP2 clients to access a SQL Server 2000 =
instance running on a remote Windows 2000 Advanced Server consistently =
fails .


[quoted text, click to view]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
[quoted text, click to view]
rights.

Hi Pierre,

Thanks for your reply.

I would love to rephrase my understanding, please kindly let me know if I
misunderstood it. You are using SQL clients in Windows XP SP2 to access a
remote SQL Server machine and get the error message "Server does not exist
or access denied".

I guess this is a configuration issue, as Microsoft Windows XP Service Pack
2 (SP2) includes Windows Firewall and the firewall disabled SQL Server port
defaultly. We have to configure XP SP2 first to enable these ports.

First of all, I have noticed you said " I've disabled the software
firewall", I just want to confirm the firewall you mentioned is Windows
Firewall. According to the KB article 841249 I gave, it include following
two links that I think you should follow to configure.

841251 How to enable SQL Server connectivity on Windows XP Service Pack 2
http://support.microsoft.com/kb/841251/

841252 How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
Server 2000
http://support.microsoft.com/kb/841252/

Secondly, If you have confirm all configuration in the KB above is set
correctly, I believe we will have to check the network between that two
computers.

- PING <SQL Server name>
- TELNET <SQL Server name>:1433

Let me know the result after executing above two.

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.