"J Jones" <JJones@discussions.microsoft.com> wrote in message
news:F06A523E-1877-4635-B1F9-6F2C35223155@microsoft.com...
> For the life of me, I cannot figure out where to change the replication
> connect string to the subscriber from named pipes to tcp/ip. On the
> publisher, I have the subscriber registered in SSMS using tcp/ip and it
> connects just fine, but the merge replication syncronization fails each
> time
> because the publisher is attempting to use a named pipe connectionto the
> subscriber. I believe it's a firewall or routing issue somewhere in our
> corporate networking infrastructure, because I can create a named pipe
> connection to the subscriber from my local machine without issue.
>
> Where is the replication-specific connect string info stored, and how do I
> change it to tcp/ip?
> Thanks!
> Jeff Jones
> Atlanta, GA
>
>

"Hilary Cotter" wrote:

> can you
> 1) drop the subscriber from SSMS on the publisher.
> 2) create an alias using SQL Configuration Manager specifying the IP address
> 3) recreate the subscription
> --
> 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:F06A523E-1877-4635-B1F9-6F2C35223155@microsoft.com...
> > For the life of me, I cannot figure out where to change the replication
> > connect string to the subscriber from named pipes to tcp/ip. On the
> > publisher, I have the subscriber registered in SSMS using tcp/ip and it
> > connects just fine, but the merge replication syncronization fails each
> > time
> > because the publisher is attempting to use a named pipe connectionto the
> > subscriber. I believe it's a firewall or routing issue somewhere in our
> > corporate networking infrastructure, because I can create a named pipe
> > connection to the subscriber from my local machine without issue.
> >
> > Where is the replication-specific connect string info stored, and how do I
> > change it to tcp/ip?
> > Thanks!
> > Jeff Jones
> > Atlanta, GA
> >
> >
>
>