Re: Sql Native Client - Can't reach by instance name



My guess is that something is blocking port 1434 (udp) from that client to the Express instance.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Kevin Chambers" <KBChambers@xxxxxxxxx> wrote in message news:1190849489.301302.39570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi there--

I'm connecting to SQL Server Express from MS Access via ADO on a
number of older workstations. Of three workstations, two connect just
fine with a connection string like this:
Provider=sqlncli;Network Library=DBMSSOCN;Initial Catalog=MyDb;Data
Source=server\sqlexpress;Integrated Security=SSPI

However, on one machine (W2K), the above does not work, but this does:
Provider=sqlncli;Network Library=DBMSSOCN;Initial Catalog=MyDb;Data
Source=server,2295;Integrated Security=SSPI

There appears to be a problem with getting the connection redirected
to the named instance. It seems like the native client driver should
be all I need for this to happen, but it ain't. Anyone know what's
missing here?

Thanks in advance for any help.

KC


.



Relevant Pages

  • Re: Connection Error: ADO.Net and SQL Server 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... I can connect to the server through an ODBC connection ... It is very puzzling because this client doesn't seem to have anything ...
    (microsoft.public.sqlserver.connect)
  • RE: Error 17835 - When encryption and Shared Memory are enabled
    ... Did you encounter this error when you connected to your SQL Server ... Did your SQL Server instance use a certificate explicitly specified by ... you configure your client connection settings "Force Protocol Encryption" ...
    (microsoft.public.sqlserver.connect)
  • Re: Losing connections with SQL 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... SQL Server automatically detects if the client falls into the sea or gets ... Does the Connection pooling mechanism do this on its ... Upgrading our app is a really big task, ...
    (microsoft.public.sqlserver.connect)
  • Re: netbios and named pipes sql replication.
    ... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
    (microsoft.public.sqlserver.replication)
  • Re: Problem connection to SQL Server with ODBC
    ... What protocols are being used by the client and what is the ... Are you using an alias for the connection? ... SQL Server Clients May Change Protocols When They Try ...
    (microsoft.public.sqlserver.connect)

Loading