Re: Subscriber cannot "see" Publisher - and it's going to stay that wa

The obvious case where direct communication is required is when 2PC is used
between the subscriber and publisher - immediate updating subscribers. This
is not publisher -> subscriber as you mention, but still a direct
communication path is required, albeit in the opposite direction. Apart from
that I think you're fine although I don't have a remote distributor here to
test this.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .


.

Relevant Pages

  • Re: The process cound not enumerate changes at the subscriber - Invalid character value for cast
    ... both the subscriber and publisher. ... DBMS: Microsoft SQL Server ...
    (microsoft.public.sqlserver.replication)
  • Re: Problems replicating over internet....Still....
    ... to your Publisher to download the snapshot and transactions. ... We can't test connectivity using ping, but you can ftp from the subscriber ... go to Client network utility. ... Server, ...
    (microsoft.public.sqlserver.replication)
  • Re: Merger Replication - SQL2000
    ... we are unable to get a new subscriber up ... Manually removed the subscription from the subscriber and the publisher. ... with new snapshot ... we were unable to get merger replication to ...
    (microsoft.public.sqlserver.replication)
  • Re: Rows do not match between Publisher and Subscriber. (Possible
    ... You backed up the publication database, ... the subscriber does not have the schema and data in place option). ... Looking for a SQL Server replication book? ... synctran_commands from the publisher to the subscription manually. ...
    (microsoft.public.sqlserver.replication)
  • Re: Applying snapshot fails
    ... on both the publisher and Subscriber and check the status and SRV_ID. ... sp_dropserver 'severname' and then sp_addserver 'servername' with the local ... ||> replication working with a publisher/distributer and a subscriber. ...
    (microsoft.public.sqlserver.replication)