Unable to connect to SQL Server thro Query Analyzer

[RiyaKumar]

Hi,

Iam getting the following error when I try to connect to SqlServer2000 through Query Analyser in the client m/c.

SQL State : 'HYT00'
'[odbc sql server driver] Timeout expired'

We are able to connect to SQL Server from our XP systems but not from the windows 2000 clients. The SQL Server 2000 is in Windows 2003 small Business server. Can someone help to identify the problem?

Thanks.

 

[mrdenny]

OK, that's odd. Here is the standard list of things to check.

1. Can you telnet from the not working stations to port 1433 on the SQL Server?
2. Can you connect to the file share of the SQL Server from the not working stations?
3. Do the not working machines have firewalls installed?
4. Do you have some sort of GPO preventing access from nonXP stations?
5. Do you have any sort of firewall on the line between the non-working stations to the SQL Server?
6. Do you have a firewall on the SQL Server?

Let me know.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[RiyaKumar]

Thanks a lot for the reply.

Checked the following..

1. Didn't know how to check telnet connectivity
2. Yes, we could connect to the fileshare
3. No firewalls in the not working systems
4. No GPO
5. No firewall in the network.
6. No firewall in the system with SQL server.

Moreover, the now-not working system was working last week i.e. we were able to connect to the sql server. I checked for any new installations in the SQL Server system and the client systems which are not working. But we didn't install anything new except that these systems were shutdown for the weekend and restarted on Monday.

Thanks

 

[SQLBill]

Did you upgrade to XP Service Pack 3? If so, that automagically turns on the Windows XP firewall (built in to XP) and TCP port 1433 is blocked. (Along with other ports that MS so diligently thought to block for XP users).

-SQLBill

Posting advice: FAQ481-4875

 

[mrdenny]

To check the telnet from a command prompt run;

telnet {servername} 1433

If you get a blank screen with a blinking curser you connected, if it gives you an error you didn't connect. Check the windows personal firewall, check for firewalls that come with anti-virus software, etc.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[SQLBill]

Ooppss, I should have said 'Did you upgrade to XP Service Pack 2'.

-SQLBill

 

[RiyaKumar]

Thanks for the replies!

We did few things and the Windows 2000 systems could now connect to the SQL Server!

We created a system DSN (using ODBC) to the SQL2000 Server and modified the 'Client configuration' option to use Named Pipes in the ODBC Administrator. This seem to create an entry for the server in the Alias Option of the Client network utility. And now we are able to connect to the server using Query Analyser.

-Riya

 

[RiyaKumar]

By the way, Telnet to port 1433 is working. Does that mean that we need not force the client to connect using named pipes?

 

[mrdenny]

You shouldn't need to force named pipes since you can connect on port 1433.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[stef315]

I have a problem connecting when I go to setup the ODBC connection using TCP/IP. If the configuration screen where you select connection method does not have a checkbox for Dynamically Determine Port, then it's an old connection/ODBC Driver/whatever (excuse my ignorance here). So, I use my SQL CD and install connectivity only. After that, I can setup the ODBC using TCP/IP instead of Named Pipes.

I'm not sure if that is related but it seemed similar to me.