?
Solved

can't connect from Query Analyzer

Posted on 2004-04-26
14
Medium Priority
?
238 Views
Last Modified: 2012-08-14
I get this error while connecting through Query Analyzer:
[Microsoft][ODBC SQL Server Driver] Timeout Expired

                                [OK]

The weird thing is that I can connect through the Enterprise Manager!
I tried setting the Login time-out in query analyzer to zero. but the error still occurs!

Please advise on how to resolve this. :D







0
Comment
Question by:killer5
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 2
  • 2
  • +2
14 Comments
 
LVL 3

Expert Comment

by:Frostbyte_Zero
ID: 10918693
If you are using Trusted Connection, try using SQL Server Authentication instead. If this resolves the problem, then the issue is probably due to the Domain Controller in your network.
0
 
LVL 6

Expert Comment

by:jchopde
ID: 10918742
You should use the "Client Network Utility" to setup your connection correctly (whether TCP/IP or Named Pipes or ...). SEM uses Named Pipes I think and QA may be using TCP/IP to spit out the Timtout Expired message. Regardless, using the client network utility should fix the issue.
0
 
LVL 1

Author Comment

by:killer5
ID: 10926220
i tried using the client network utility... but it didn't work.

before this problem, i had this issue:
http://www.experts-exchange.com/Databases/Microsoft_SQL_Server/Q_20953323.html

0
Moving data to the cloud? Find out if you’re ready

Before moving to the cloud, it is important to carefully define your db needs, plan for the migration & understand prod. environment. This wp explains how to define what you need from a cloud provider, plan for the migration & what putting a cloud solution into practice entails.

 
LVL 1

Author Comment

by:killer5
ID: 10927301
i tried using the client network utility... but it didn't work.

before this problem, i had this issue:
http://www.experts-exchange.com/Databases/Microsoft_SQL_Server/Q_20953323.html

after the issue above, everything worked fine. but after several days... i couldn't connect using query analyzer
0
 
LVL 1

Author Comment

by:killer5
ID: 10927303
i've already tried reinstalling SQL client
0
 
LVL 6

Expert Comment

by:jchopde
ID: 10927519
Have you tried SQL Auth via QA as Frostbyte had suggested ? If you are using TCP/IP for connectivity, can you ping the IP address of your SQL server ? (go to command prompt, type "ping <<ip address>>" and press ENTER) If you are using named pipes for connectivity, can you ping using the server name ?
0
 
LVL 1

Author Comment

by:killer5
ID: 10927678
yup... i've tried SQL Auth via QA.
i can ping it using the server name.

I got it working already... i connected to the server using the IP address instead of the server name.

but what's the logic behind that?
0
 
LVL 8

Expert Comment

by:plq
ID: 10930746
turn off named pipes so you just connect through tcpip. Do that on the server and the client

tcpip is faster anyway
0
 
LVL 3

Expert Comment

by:Frostbyte_Zero
ID: 10930843
Actually plq, NetBEUI ( the protocol used for NamedPipes ) is actually a smaller, but less routable protocol than TCP/IP.

The fact that your Windows OS can see the server by name does not necessarily mean that SQL Server can. Usually, if you enter an alias in the Client Config Utility using TCP/IP instead of NamedPipes you should get connected.

For instance, your workstation casn have an LMHOSTS file with the entry in it. SQL Server will not use the LMHOSTS entry to resolve the IP address.

So are you connecting to SQL Server now?
0
 
LVL 1

Author Comment

by:killer5
ID: 10957926
I got it working already... i connected to the server using the IP address instead of the server name.

but what's the logic behind that?
0
 
LVL 1

Author Comment

by:killer5
ID: 10957937
yup I can connect to the SQL Server now.
THANKS GUYS!
0
 

Accepted Solution

by:
modulo earned 0 total points
ID: 10990076
Closed, 125 points refunded.

modulo
Community Support Moderator
Experts Exchange
0

Featured Post

Moving data to the cloud? Find out if you’re ready

Before moving to the cloud, it is important to carefully define your db needs, plan for the migration & understand prod. environment. This wp explains how to define what you need from a cloud provider, plan for the migration & what putting a cloud solution into practice entails.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
In this article we will learn how to fix  “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.
Using examples as well as descriptions, and references to Books Online, show the documentation available for datatypes, explain the available data types and show how data can be passed into and out of variables.

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question