"J Jones" <JJones@discussions.microsoft.com> wrote in message
news:D850245C-4133-4CDF-861A-DEC1D1B82BB2@microsoft.com...
> Thanks Hilary - no, both machines are joined to a domain, albeit different
> ones. I can connect to the subscriber via named pipes from my local
> machine,
> but not from the publisher. I'm sure there's a firewall rule preventing
> the
> NP connection, but I'd prefer to use IP anyway. How do I tell replication
> to
> use IP instead of NP?
> Jeff
>
> "Hilary Cotter" wrote:
>
>> Yes, however is one of the machines part of a work group? You might be
>> running into a connection limit issue.
>>
>> --
>> RelevantNoise.com - dedicated to mining blogs for business intelligence.
>>
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.com
>> "J Jones" <JJones@discussions.microsoft.com> wrote in message
>> news:B6E4E191-28D3-406F-A3B3-D5136B5E235B@microsoft.com...
>> > I'm trying to setup merge replication and am running into the following
>> > error
>> > during syncronization to the subscriber:
>> >
>> > Named Pipes Provider: Could not open a connection to SQL Server [53].
>> >
>> > On the publisher, I can register the subscriber via tcp/ip without
>> > issue,
>> > but the Replication-specific connection appears (from the error above)
>> > to
>> > default to Named Pipes. Can I override this default named pipes
>> > behavior
>> > and
>> > just use TCP/IP?
>> > Thanks!
>> > Jeff Jones
>> > Atlanta, GA
>>
>>
>>