Replication to server with different Port

I have a SQL server running on a remote location that has a different port
enabled to connect other than the default one, which means that when I want
to register I have to specify the port number as well eg.
Server1\InstanceName,4001 .
I am trying to carry out merge replication between the server and the MSDE
on my box. I have set up the pubisher, registered the SQL Server from
Enterprise Manager on my machine and on setting up the subscriber I am able
to view the publication in the list of registered servers. Creating the
subscription works fine, but when I try to sync , I get the error 'The
process could not connect to Distributor 'Server1\InstanceName' . I feel that
this is because of the port since it is not mentioned in the message and SQL
is trying to use the default port. Is there some workaround for this?
Jax,
for a named instance, there is no default port - it is assigned at creation
from the list of available ports, and your port number won't necessarily be
the same as mine, for the first named instance. Usually the port number is
not specified in the replication definition, and it is dynamically picked up
(hence the slammer virus on UDP, port 1434 ). Do you have 1434 blocked? If
not, then please try designing without the port number and see if this
works.
Also, The SQL Server Agent service (SQLServerAgent) at the client should not
use the LocalSystem account. It needs to use a standard domain account.
Finally, please check that the agents use impersonation.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

replication on port 80 with sqlServer 2005

Can replication be done over port 80 with SQL Server 2005?
This would remove the "hotel firewall blocks port 1433" scenario.......
Thanks
You can run SQL server on any port including 1433, or 80. Causes havoc with
web servers running on this port though.
Hilary Cotter
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
"astro" <astro@.bcmn.com> wrote in message
news:3HZlf.1272$7S.24@.tornado.rdc-kc.rr.com...
> Can replication be done over port 80 with SQL Server 2005?
> This would remove the "hotel firewall blocks port 1433" scenario.......
>
> Thanks
>
|||that makes sense...but how do you deal with traveling sales staff that need
to replicate on their hotel connection when all ports except 80 (web) and 25
(smtp) and 110 (pop3) have been locked down? Has anyone else ran into this?
Or maybe this is some other issue.....
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OAc0HoM$FHA.272@.TK2MSFTNGP09.phx.gbl...
> You can run SQL server on any port including 1433, or 80. Causes havoc
> with web servers running on this port though.
> --
> Hilary Cotter
> 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
> "astro" <astro@.bcmn.com> wrote in message
> news:3HZlf.1272$7S.24@.tornado.rdc-kc.rr.com...
>
|||I've noticed limitations are enforced if you enable web access in your
publication: first is the dynamic snapshots are not created or used as new
subs try to sync, 2nd you can use logical record, were replication can treat
joined tables as a transaction (order hdr/lines for example)
the new prepared dyn snap shots are awesome, our initial sync times went
from 40mins to ~ 2mins!! (and it was 2+ hours on sql2000) and its all
automatic...
also if you have the pub web enabled, yet still sync through the tradition
means (which you can, you can change it in the sub), dyn snapshouts still do
not work...
"astro" <astro@.bcmn.com> wrote in message
news:3HZlf.1272$7S.24@.tornado.rdc-kc.rr.com...
> Can replication be done over port 80 with SQL Server 2005?
> This would remove the "hotel firewall blocks port 1433" scenario.......
>
> Thanks
>
|||sorry correction-- *CAN'T* use logical records
"S c o t t K r a m e r" <sckramer2000@.hotmail.com> wrote in message
news:d10dc$439bed58$a227293d$4609@.ALLTEL.NET...
> I've noticed limitations are enforced if you enable web access in your
> publication: first is the dynamic snapshots are not created or used as new
> subs try to sync, 2nd you can use logical record, were replication can
> treat joined tables as a transaction (order hdr/lines for example)
> the new prepared dyn snap shots are awesome, our initial sync times went
> from 40mins to ~ 2mins!! (and it was 2+ hours on sql2000) and its all
> automatic...
> also if you have the pub web enabled, yet still sync through the tradition
> means (which you can, you can change it in the sub), dyn snapshouts still
> do not work...
> "astro" <astro@.bcmn.com> wrote in message
> news:3HZlf.1272$7S.24@.tornado.rdc-kc.rr.com...
>
|||I'll have to look at this.....
Thanks.
"S c o t t K r a m e r" <sckramer2000@.hotmail.com> wrote in message
news:d10dc$439bed58$a227293d$4609@.ALLTEL.NET...
> I've noticed limitations are enforced if you enable web access in your
> publication: first is the dynamic snapshots are not created or used as new
> subs try to sync, 2nd you can use logical record, were replication can
> treat joined tables as a transaction (order hdr/lines for example)
> the new prepared dyn snap shots are awesome, our initial sync times went
> from 40mins to ~ 2mins!! (and it was 2+ hours on sql2000) and its all
> automatic...
> also if you have the pub web enabled, yet still sync through the tradition
> means (which you can, you can change it in the sub), dyn snapshouts still
> do not work...
> "astro" <astro@.bcmn.com> wrote in message
> news:3HZlf.1272$7S.24@.tornado.rdc-kc.rr.com...
>
|||cool!
sql2005 Merge replication speed is amazing now, makes sql2000 seem like the
stone age!!
"astro" <astro@.bcmn.com> wrote in message
news:hDhnf.9358$Dk.8912@.tornado.rdc-kc.rr.com...
> I'll have to look at this.....
> Thanks.
> "S c o t t K r a m e r" <sckramer2000@.hotmail.com> wrote in message
> news:d10dc$439bed58$a227293d$4609@.ALLTEL.NET...
>