We help IT Professionals succeed at work.

Connect to SQL server 2000 with TCP/IP not working

Waxed asked
Last Modified: 2012-08-13

I have a SQL 2000 box which works fine with Named Pipes.
I'm trying to connect via TCP/IP. However, I get a connection error message of SQL Error : 10054 and SQL Error 11 even when trying to connect locally when testing a System DSN against the database.
Tried other databases on the same box and get the  same connection error.

TCP/IP is installed in SQL Server Network Utility, default port.
Still no luck.
Watch Question

have you tried to turn off the windows firewall?

go into the command prompt, and type

netstat -an

to see if the ports are open. you can also use a port monitoring tool like tcpview

is the sql server installation upgraded to the latest version? before a version sql server 2000 blocks tcp/ip connections due to a security problem.


I have
TCP               LISTENING
Don't see the local socket.


SQL SP4 installed.
no windows firewall.
Box is Win2k/SP4

hey waxed,

Sorry for the latency.

have you checked the sql server logs for further info on the error? I have read several ms forum threads and articles on the subject, it seems like nobody got a proper solution or the cause of the problem, seems to be an odbc issue with tcp/ip connections. may be related to the network libraries, re-installation of some components may work here.

Due to the error message, you can connect to the server, but your connection is getting reset by the server. So the server listens to the ports and get connections.

At first, we haven't talk about the details on the server configuration. The tcp/ip may be enabled but not for the network interface the software tries to connect, so try this one;


Secondly, try to directly connect using Enterprise Manager, to see if the problem is related with ODBC or a command sent by the application at the first connection.

It may be related with the instances, here is a good compiled list of connection issues, mostly valid for sql server 2000:

Here is why it may be the result of an action :

There are also some threads related to this problem in Experts Exchange, they can give an idea, but they are mostly resolved in a different way, like moving the databases to another software, anyway here they are for your info:


In my opinion, it is probably related to network configuration, existance of unused protocols (named pipes etc), instances, or broken network library.

Please let me know any improvements. Good luck.

Unlock this solution and get a sample of our free trial.
(No credit card required)

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.