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.

chandar_bhandariAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
marirajuConnect With a Mentor Commented:
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.

Cheers
0
 
St3veMaxCommented:
Are you trying to connect to an instance of SQL Server?

What if you create teh ODBC connection by name and try that?
0
 
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.
0
Take Control of Web Hosting For Your Clients

As a web developer or IT admin, successfully managing multiple client accounts can be challenging. In this webinar we will look at the tools provided by Media Temple and Plesk to make managing your clients’ hosting easier.

 
St3veMaxCommented:
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?
0
 
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?.
0
 
St3veMaxCommented:
Can you use Enterprise Manager to connect remotely? If not, I suspect you have a firewall or something in the way.
0
 
chandar_bhandariAuthor Commented:
THANKS
0
All Courses

From novice to tech pro — start learning today.