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

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 (AT) gmail (DOT) com> wrote

Thanks for the reply. Any suggestions on a method of testing access
to a specific port via a particular protocol? I've never needed to go
past using plain old ping.

On Sep 26, 11:48 pm, "Tibor Karaszi"
<tibor_please.no.email_kara... (AT) hotmail (DOT) nomail.com> wrote:

Sorry, that it a tad too much IP for me. Perhaps someone else can jump in here, or ask in a
networking group?

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


"Kevin Chambers" <KBChambers (AT) gmail (DOT) com> wrote