We help IT Professionals succeed at work.

ODBC Driver timout problem

tybe
tybe asked
on
Hello,

I'm trying to connect to SQL Server through the local area network, and I get a timeout problem.
Here is the complete description.

1. If I try to setup an ODBC datasource to SQL server:
- SQL State HYT00
- SQL Server error 0 (timeout expired)

2. I can connect from enterprise manager (If I force a connection).

3. I cannot connect from Query Analyzer.

4. My coleaques do not have connection problems.

Does anybody have an idea what causes the problem. I use a WIn 98 OS.

Thanks.
Comment
Watch Question

Commented:
Do you use the same protocol as your colleagues? See SQL server Client network utility for your Client Connectivity settings.
Which version of SQL server?

Author

Commented:
I use TCP-IP just as my coleagues. The point is that there are times when I can connect and 10 minutes after I'm not able to connect again. I'm very confused.

Author

Commented:
I use SQL Server 2000. I've found an article on SQL Magazine about the topic , but unfortunately I'm not a member.

http://www.sqlmag.com/Articles/Index.cfm?ArticleID=21751 

Connecting to SQL Server Through Query Analyzer

Since I installed the SQL Server 2000 tools on my PC, I've had problems using Query Analyzer to log in to my SQL Server 2000, 7.0, and 6.5 servers. Establishing a connection takes a long time, and in most cases, several tries. I frequently receive the error message ODBC SQL Server Driver Timeout expired. I've increased the logintimeout value in both Enterprise Manager and Query Analyzer to 45 seconds, but I still get the timeout error after only 15 to 20 seconds, not 45. When I use the SQL Server 6.5 isqlw utility, I always get a connection right away. What am I missing?


Commented:
Here the article from SQL Magazine :
Connecting to SQL Server Through Query Analyzer

Since I installed the SQL Server 2000 tools on my PC, I've had problems using Query Analyzer to log in to my SQL Server 2000, 7.0, and 6.5 servers. Establishing a connection takes a long time, and in most cases, several tries. I frequently receive the error message ODBC SQL Server Driver Timeout expired. I've increased the logintimeout value in both Enterprise Manager and Query Analyzer to 45 seconds, but I still get the timeout error after only 15 to 20 seconds, not 45. When I use the SQL Server 6.5 isqlw utility, I always get a connection right away. What am I missing?

Are the SQL Server 7.0 and 6.5 servers using named pipes only? If so, the problem might be that your SQL Server 2000 client is trying to use TCP/IP sockets by default. You can go into the Client Network Utility on your client machine and reset the default network protocol to named pipes. Alternatively, you can follow Microsoft's strategic direction by adding TCP/IP sockets to your SQL Server 7.0 and 6.5 servers.