Clients not connecting to SQL Server via TCP/IP ODBC

We have a Windows 2000 advance Server and SQL Server Enterprise 2000 running on the standard internal domain. when clients are trying to connect to SQL SERVER through TCP/IP ODBC
it gives error

Microsoft SQL Server Login
Connection failed:
SQLState: '01000'
SQL Server Error: 10053
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (PreLoginHandshake()).
Connection failed:
SQLState: '08001'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are you trying to connect to an instance of SQL Server?

What if you create teh ODBC connection by name and try that?
chandar_bhandariAuthor Commented:
i am trying to connect to Database Server via TCP/IP ODBC.

And what are you trying to say in second line.
Are you trying to connect to the default instance or a named instance of SQL Server? i.e. SERVERNAME or SERVERNAME\INSTANCE ?

In ODBC Connection Properties, Have you tried connecting with the name instead of the IP address?
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

chandar_bhandariAuthor Commented:
i am trying with servername not instance and i have tried with both server name and ip address also.

is there anyway to check 1433 port is used correctly or not in server?.
Can you use Enterprise Manager to connect remotely? If not, I suspect you have a firewall or something in the way.
Hello there,

I think you must be having some kind of firewall or any anti-virus, spyware or malware or zonealarm.
Please try to check them for the allowed ports.

Try pinging the server from the client PC and also make sure that allowed ports.

If the client have the SQLCMD utility, can you try the following
(you can also download the utility from microsoft)

sqlcmd -S servername\instancename (this is without password)
sqlcmd -S servername\instancename -U username -P password

Most of the time it happens because of the firewall and the accessible ports.

Please do let me know.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
chandar_bhandariAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.