Diagnosing Connection to SQL Server

The only thing i can think of is that the client computer is windows server 2003, and has various roles setup:

I don't know why these services are setup, but for the time being i can't shut them off. Would it be any of these, and if so, is there a way to disable any of the aspects of them, that might be blocking SQL.

Any advise truly appreciated!

asked Nov 15, 2012 at 20:00 875 5 5 gold badges 25 25 silver badges 48 48 bronze badges

another thing: I'm able to create ODBC connections from other clients fine. It does appear that the problem lies with this particular client, either with the roles setup, or perhaps something else. Thanks!

Commented Nov 15, 2012 at 20:05

5 Answers 5

Found the issue. For some reason, even though SQL was not in use on the client, it was installed, and by going to All Programs -> Microsoft SQL Server -> Client Network Utility, i found that the protocal TCP/IP was using port 4717. I have no idea why that port was in use, and even further, i'm not sure why it would even matter - I was just setting up an odbc connection, and not using sql server (on the client) at all. Either way, I changed this to the typical port (1433), and like boom, ODBC connection works like charm!

answered Nov 15, 2012 at 20:44 875 5 5 gold badges 25 25 silver badges 48 48 bronze badges

I needed to go to SQL Server Configuration Manager, at SQL Server Network Configuration, on Protocols for SQLInstancename. The Named Pipes and TCP/IP protocols were disabled. Enabled them, and restarted the service, and connection was made instantly almost without clicking to test haha. Your answer has led me to find this, thanks.

Commented Dec 15, 2020 at 14:34

Is it possible that the server in question has not been configured to use named pipes?

CAUSE
The most common reason that this connection attempt failed is that this DSN or ODBC data source attempted to make a connection using the TCP/IP sockets Net-Library, which is Dbmssocn.dll. Because the SQL Server is not listening for incoming connections for TCP/IP sockets clients, the connection fails. From ISQL/w, the second error message stated above would be returned. The OS Error is 10061, and the function call that failed was ConnectionOpen(connect()).

WORKAROUND
By default, SQL Server will listen for incoming connections made by Named Pipes clients. Named Pipes is the default IPC mechanism for clients to connect to a SQL Server version 4.2, 6.0, and 6.5 server. The Named Pipes DLL is Dbnmpntw.dll, and it should be located in the Windows\System or Winnt\System32 directory. The TCP/IP sockets netlib DLL is Dbmssocn.dll, and also should be in the Windows\System or Winnt\System32 directory.The most common resolution to this problem is to configure the client computer to connect using Named Pipes. Configuring Named Pipes If the Microsoft Data Access Components (MDAC) ODBC drivers have been installed on the computer, you can make this change in the second step of the Create New Data Source wizard.

NOTE: You can download MDAC drivers from:

http://msdn2.microsoft.com/en-us/data/aa937730.aspx To configure the client, start the Create New Data Source wizard, click the Client Configuration button, and perform the following steps, based on the version of the SQL Server ODBC driver you are using:

For SQL Server ODBC Driver version 3.50

Click the Net Library tab and use the drop down list box to set the default network (Net Library) to Named Pipes. On the Advanced tab, remove any advanced entries that reference the server you are connecting to. Click Done.

For SQL Server ODBC Driver version 3.70

In the Network Libraries section of the Edit Network Library Configuration dialog box, select Named Pipes. Click OK.

If you do not have the MDAC ODBC drivers installed, you can use the SQL Server Client Configuration Utility tool to set the default Net-Library to Named Pipes. You can install the client utilities from the SQL Server CD from the i386 directory.