Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Other SQL Server Topics / September 2007

Tip: Looking for answers? Try searching our database.

Sql Native Client - Can't reach by instance name

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Kevin Chambers - 27 Sep 2007 00:31 GMT
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
Tibor Karaszi - 27 Sep 2007 07:48 GMT
My guess is that something is blocking port 1434 (udp) from that client to the Express instance.

Signature

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

> Hi there--
>
[quoted text clipped - 16 lines]
>
> KC
Kevin Chambers - 28 Sep 2007 21:50 GMT
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...@hotmail.nomail.com> wrote:
> My guess is that something is blocking port 1434 (udp) from that client to the Express instance.
>
[quoted text clipped - 21 lines]
>
> > KC
Tibor Karaszi - 29 Sep 2007 18:38 GMT
Sorry, that it a tad too much IP for me. Perhaps someone else can jump in here, or ask in a
networking group?

Signature

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

> 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
[quoted text clipped - 28 lines]
>>
>> > KC
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.