Solved

Cannot Connect via Native 2005 or 2008 ODBC XP client to 2005 SP3 instance

Posted on 2010-09-02
4
488 Views
Last Modified: 2012-05-10
Cannot Connect via Native 2005 or 2008 ODBC XP client to 2005 SP3 instance named masdcvsql404\sql404, but can connect via odbc from different SQL server 2008 box via native client 2005.

It would seem the credentials are not the problem, nor the server-side set up. Am I missing something on the client side, do i need Studio manager Express to get some sort of tool to deal with instance name?
0
Comment
Question by:jeffreyrgauser
[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
  • 2
4 Comments
 

Author Comment

by:jeffreyrgauser
ID: 33589098
Actually, client was able to connect to this db when it was on a SQL2005 SP2 box with SQL 2000 client.  Studio Manager is not installed.
 
Do I need to request that server team enable some sort of listener for DBC specifically?
0
 
LVL 12

Accepted Solution

by:
NormanMaina earned 250 total points
ID: 33590683
on the problem machine can you connect using osql?

Try on command promt : OSQL - S instancename -U username

If that does not work then its a problem to do with firewall blocking the SQL Server port or antivirus doing that or maybe the client tools are not correctly installed.

If you can connect using OSQL then its a version issue...like trying to view an sql server 2005 instance using enterprise manager will not work.
0
 
LVL 7

Assisted Solution

by:lundnak
lundnak earned 250 total points
ID: 33596222
What port is the SQL Server instance, MASDCVSQL404\SQL404 listening to?  You can get this from SQL Server Configuration Manager.
You will want to test connectivity first.  Try this first.

telnet MASDCVSQL404 <port#>   **port # usually 1433  

If the telnet fails, then you have a network connectivity issue.  Possibly, a network issue or firewall issue.

If it works, change the ODBC connection to use TCPIP with the specific port.  It's possible that its trying to use Named Pipes.
0
 

Author Comment

by:jeffreyrgauser
ID: 33707760
Found issue to be preclusion by McAfee Access Protection Rules.  Company was not allowing tcp 1434.
0

Featured Post

Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

Question has a verified solution.

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

Many companies are making the switch from Microsoft to Google Apps (https://www.google.com/work/apps/business/). Use this article to learn more about what Google Apps has to offer and to help if you’re planning on migrating to Google Apps. It is …
Article by: Leon
Software Metering within our group of companies has always been an afterthought until auditing of software and licensing became a pain point. Orchestrator and SCCM metering gave us the answer and it was an exciting process.
The viewer will learn how to simulate a series of coin tosses with the rand() function and learn how to make these “tosses” depend on a predetermined probability. Flipping Coins in Excel: Enter =RAND() into cell A2: Recalculate the random variable…
The viewer will learn how to use a discrete random variable to simulate the return on an investment over a period of years, create a Monte Carlo simulation using the discrete random variable, and create a graph to represent the possible returns over…

756 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