October 27, 2005 at 5:18 am
We are having a problem of users not being able to connect to our SQL SErver 2000 SP4 server via ODBC using TCP. It keeps giving the following error:
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.
I tried using Windows NT & SQL Authentication when setting up this ODBC DSN. Both gave the same error. We can connect to SP3 servers using this method so that led me to believe there was an issue with SP4.
Has anyone read anything about this? I haven't been able to find anything as of yet.
Thanks!
John
October 28, 2005 at 8:09 am
John,
On the client, what protocols are enabled in the SQL Server Client Network Utility? Is the server aliased in the same utility for a different protocol?
Just some things I would check.
October 28, 2005 at 9:48 am
I'm thinking I remember something from upgrading my SP3 install to SP4 where it turned off various network protocols by default with the upgrade.
Like Okafor said check the SQL Server Client Network Utility.
From Enterprise Manager, Right click on your server name and choose properties. Click the Network Configuration Button.
October 28, 2005 at 9:54 am
TCP/IP & Named pipes are the protocols that are listed as enabled on the server. Port 1433 for TCP/IP.
I don't believe the server is aliased as anything else.
Interesting, I changed the DSN to use Named pipes instead of TCP/IP & I was able to connect.
Thanks,
John
October 28, 2005 at 10:09 am
Since that is the case, I would now check the server settings and make sure TCP/IP is set on the server.
October 28, 2005 at 10:16 am
I did check the server & TCP/IP & Named pipes are enabled. At least under the server network utility they are. There isn't another place I need to check, is there?
John
October 28, 2005 at 10:19 am
October 28, 2005 at 10:23 am
I don't think so. On the server, I checked & it was the default port. On the client, I checked & it was the same port.
October 28, 2005 at 10:30 am
ok another off the wall question... Do you by any chance have McAfee AV installed on the client. Out of the box it comes with a bunch of port blocking things you have to look out for. Also check Windows filewall and or anything else you may have on your client that would be blocking that port.
October 28, 2005 at 10:55 am
No McAfee. We are using Norton AV. I will have to check the windows firewall but I don't think it is blocking the port.
May 5, 2006 at 2:45 pm
hi Laker 42, I have similar problem with ODBC connection over TCP/IP . Did you get any solution. Thanks. Walter
May 5, 2006 at 3:25 pm
Dumb question but how are you referencing the server for TCP/IP. Is it by the name or by a DNS entry or the IP?
Have you tried using the IP itself to see what happens if using any other reference?
May 8, 2006 at 3:58 am
Walter,
I never did find a solution to this besides having the user use named pipes instead of TCP/IP. Only had this issue with one user so I am not exactly sure what happened.
Antares,
We did try using the IP address as well but it did not make a difference. It would still not connect via TCP/IP.
John
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply