An Interesting Issue : ODBC | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

An Interesting Issue : ODBC

Hi All,
This is a really wierd one…Thers a Win 2000 machine, where I am trying to create ODBC for a database DAB in sql server DAXFC01(SQL 2000). It keeps on saying "Access denied or Server does not exist" and the ODBC fails. But that DB/SQL server is used by 100s of others and it works fine. I have reinstalled the SQL Client, tried using Named pipes, changed ports in TCP/IP mode of connection, used Alias names in the "Client Network utility". I have also pinged that server from this machine , and its not a firewall block.
ODBCs to other servers get created proper. ONLY this server it is not. Please let me know your opinion Thanks
Thanks,
Anand.K
[email protected] "What would you attempt to do if you knew that you could never fail"
-Robert Schuller
Found another post regarding the same in page:2.
Will go thru those resolutions and see.
Thanks Thanks,
Anand.K
[email protected] "What would you attempt to do if you knew that you could never fail"
-Robert Schuller
http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=5302 for followup. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Hi , The Telnet fails, and even Query Analyzer wont recognize the server. But it is able to connect to other SQL servers. So i believe this is some network block to that specific server. The confusing factor is : This specific workstation is able to PING the server, (meaning thers no network block right?[?] Can we renew the IP and try may be ?
Thanks Thanks,
Anand.K
[email protected] "What would you attempt to do if you knew that you could never fail"
-Robert Schuller
Ping is a different protocol than sql server traffic. If you can ping but not telnet on name nor IP then the sql port is most likely blocked in a firewall. If telnet work on IP but not name you have a name resolution problem. Verify the sql server port as well, it might not be the default 1433.
And also check for any DNS issues associated with the Firewall rules. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>