can't connect from Query Analyzer

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







LVL 1
killer5Asked:
Who is Participating?
 
moduloConnect With a Mentor Commented:
Closed, 125 points refunded.

modulo
Community Support Moderator
Experts Exchange
0
 
Frostbyte_ZeroCommented:
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
 
jchopdeCommented:
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
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
killer5Author Commented:
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
 
killer5Author Commented:
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
 
killer5Author Commented:
i've already tried reinstalling SQL client
0
 
jchopdeCommented:
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
 
killer5Author Commented:
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
 
plqCommented:
turn off named pipes so you just connect through tcpip. Do that on the server and the client

tcpip is faster anyway
0
 
Frostbyte_ZeroCommented:
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
 
killer5Author Commented:
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
 
killer5Author Commented:
yup I can connect to the SQL Server now.
THANKS GUYS!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.