On Thu, 30 Mar 2006 01:16:01 -0800, pk
<pk@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have 1 SQL2000 setup with multiple instances. Have problems connecting ODBC
on a NT4 to a named instance. It can connect to the default instance though.
Tried both ServerName\instance name, and IP address\instance name. Network
connection is fine, can ping to the SQL Server. Connecting by TCP/IP network
libraries.
RE: Linked Server and Server Registration ... It may have to do with your MDAC version. ... Can you make an OSQL connection... from the SQL7 box to the SQL2K box? ... because older versions of MDAC don't know about named instances.... (microsoft.public.sqlserver.connect)
RE: Upsizing Access 2000 to SQL Server 2000 ... It might be related to your MDAC version, ... recognize named instances.... Cannot Connect to Instance of SQL Server 2000 ...Cindy Gross, MCDBA, MCSE ... (microsoft.public.sqlserver.connect)
Re: Version of MDAC for SQL 2005? ... The minimum version for named instances is 2.71. ... I would recommend the ... latest MDAC 2.8 SP1. ... Check out this blog about SQL Native Client.... (microsoft.public.sqlserver.clients)
Re: MDAC 2.1 and SQL Server 2000 ... But are there any issues specific to using it with SQL Server 2000, ... other than its inability to handle named instances?... > MDAC 2.1 is fraught with problems. ... (microsoft.public.data.ado)
hostname resolution failure : named instance on non-default port ... The Sql Server 2005 is a named instances which listens on a non-default port ... This is using the same Sql Server login as is used in the connection string... I haven't completely verified the following, but apparently for named instances which listen ... (microsoft.public.sqlserver.connect)
