ODBC Connection Failing | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

ODBC Connection Failing

I am trying to setup a DSN entry to connect to a cluster.
The SQL Server IP is .244
The cluster IP is .182
The virtual IP is .180 I tried setting up a DSN connecting to .244. When I try it for a specific login it does not work. Verified the login is setup correctly.
The domains can talk to one another.
Not sure what else to try. This is a simple task that haves me confused.
What error do you get?
Refer to this KBAhttp://support.microsoft.com/kb/827422 for more information. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
We were able to get it to connect, but it takes 16 seconds.
Also, I verified the login is setup correctly.
Do you see any network contention during this period?
You might need to check whether ODBC tracing was on, this might slow down the connection process sometimes. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
Tracing is off. No one is using this SQL Server. Not sure what is going on. What about the host file on the SQL Server. Do I need an entry in there for the SQL Server IP or the virtual IP?
That might help either provide some reliable means for performing a reverse lookup of the SQL Server server’s IP address, use the SQL Server machine name instead of the IP address. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
Same thing when I use the SQL Server name.
Try reversing that andhttp://www.sql-server-performance.com/odbc_oledb.asp fyi, you say when you try with specific login it fails and have you tried using SQL Service account in this case. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
Connecting via DSN using SQL Server service acct worked using NT authentication (but it took 20 seconds to connect.
Using standard security it did not work. Got a login failed message.
When I try connecting to the serverinstance name, it does not work. I get SQL Server does not exist.
Ok, I was able to connect to the instance by editing the host file. I still cannot connect to the instance using standard security with the first username. I am still getting "login failed". Login is out there and looks good.
Is sql installed with mixed mode security?
Try connecting using port number with different network protocols… ex: servernameinstancename,portnumber
MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

The server is setup with mixed security. Did not work using servernameinstport.
Could it be something in the network cluster setup?

If the connection is reaching SQL Server then I don’t see any fix on network to setup.
Please post the correct error you are getting there. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
The real issue is when we try to connect via DSN from serverA to serverB on the same domain, it takes 16 seconds to connect. Standard security works fine and connects immediately. Windows security is taking 16 seconds.
Sorry for the confusion. No error is returned, just VERY slow connectivity.
Also, ODBC trace is NOT on.
Hm, slow connectivity is something you have to pursue through network also, as of now I don’t think anything we can do from SQL Server side. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
did you try different protocols when you are using trusted connection? MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

quote:Originally posted by KGautney
I was able to connect to the instance by editing the host file.
This indicate a DNS problem. Verify that both your DNS servers can resolve the SQL server name and the domain controllers correctly.
]]>