Re: Problems replicating over internet....Still....

From: Hilary Cotter (hilaryk_at_att.net)
Date: 07/14/04 

Date: Wed, 14 Jul 2004 15:52:11 -0400

Let's back up for a second.

To replicate over the internet your Subscribers have to be able to connect
to your Publisher to download the snapshot and transactions.

So, at a network level they need 1) connectivity, 2) name resolution.

We can't test connectivity using ping, but you can ftp from the subscriber
to the publisher. So we know you are able to connect to something over the
internet. The question is are you connecting to the right device. It sounds
like you. I take it when you connect to your publisher using FTP you see the
snapshot files belonging to your publisher.

To ensure you are connecting to the correct device/publisher, connect to
your publisher and get its IP address. Then on each subscriber go to
%windir%\system32\drivers\etc. Open up the hosts file and enter the
publisher server name and its ip address in the form

PublisherServerName 123.123.123.123

Now you know that you have connectivity and the correct name resolution.

This is at the network level. Now we have to set everything up so that the
SQL Servers can talk to each other.

On your Publisher, go to Client network utility. Go to Tools, Microsoft SQL
Server, and select Client Network Utiltity. Click on Add, and enter your
publihser server name, and its host name. Repeat this for all of your
Subscribers, and select tcp/ip and enter the subscriber name and publisher
name.

When you are done this register all of your SQL Servers in Enterprise
Manager.

Then on your Publisher still, connect to a Subscriber in EM, and try to pull
the Subscription.

HTH 

-- 
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"DD" <DD@discussions.microsoft.com> wrote in message
news:97560760-5A3D-475F-92F7-5C9141DE98E0@microsoft.com...
> Hilary,
> Thanks as always for the help.  I can't wait for your book to be
available.  :)
>
> Regarding our network admin...it was quite difficult for him to open up
1433.  Though, I suppose I should have had him open an alternate port and
then set that alternate port in SQL too.  By the way...I have read things
about port 1434....is that necessary too??
>
> From the subscriber....I am connecting to the publisher using a name -
fully qualified, as in ServerName.Domain.Com.
>
> Your statements about the Publisher and Subscriber having to know about
each other is a bit confusing.  I understand that is how it works when
everyone is in the same domain...but in our case, the client/Subscribers are
connecting via the internet and using an anonymous pull subscription.  In
this case,when I use EM on the client, I cannot even see the
Publisher/Server in order to register it in EM.
>
> So, this brings up a point/question....especially since you also mention
the SQL Client Network Utility (as Paul did).....are we required to somehow
install the Sql Tools on all of our subscriber/clients so we can then set up
the connection to the Publisher/Server properly?  Right now...all of our
clients are using MSDE, which as you know does not come with any of the Sql
Tools - EM, QA or CNU.  I thought that it was against MS licensing policy to
distribute these tools to an MSDE client.
>
> Perhaps what we are attempting to accomplish is beyond the abilities of
Sql Server?  I thought that we could set up Publication and configure it for
anonymous pull subscriptions across the internet.  Is there another way to
do this?
>
> Thanks
>  - DD
>
> > Your Publisher and Subsciber have to know about each other. If you are
> > pulling from your Subscriber, both servers must be registered in EM. You
> > should make an entry for both servers in the hosts file (if you are
using EM
> > on the Subscriber), and then use the name in the Client Network Utility.
> >
> > When the host file, and CNU are both configured, register both servers
in
> > EM.
> >
> > Then you should be able to pull anonymous publications. If your
publication
> > is not anonymous (ie named) you will have to enable the subscriber in
Tools,
> > Replication, configure publihsers, subscribers, distributors, in the
> > Subscribers tab.
> >
> >
> > -- 
> > Hilary Cotter
> > Looking for a book on SQL Server replication?
> > http://www.nwsu.com/0974973602.html
> >
> >
> > "DD" <DD@discussions.microsoft.com> wrote in message
> > news:BB0DCFB2-B2D4-4C9F-8FF7-0325522E39C6@microsoft.com...
> > > I cannot ping the publisher/server because the network admin has
turned
> > off or disabled the ability for people to ping that server.  I can,
however,
> > go to a command prompt on the client and get to that publisher/server
via
> > ftp or even telnet (with the proper port).   My question....does the
fact
> > that ping has been disabled mean that replication won't work?
> > >
> > > I have not entered an alias on the client for the publisher's IP
address.
> > Nor have I created an entry in the Hosts file on the client/subscriber.
Is
> > this accomplished via the sql client network tool/utility?  If so....how
is
> > this normally done when you have hundreds of subscribers (anonymous
pull)
> > that do not have SQL Server tools installed?  We use MSDE for the
client.
> > >
> > > Thanks for the help.
> > >  - dd
> > >
> > > "Paul Ibison" wrote:
> > >
> > > > DD,
> > > > have you entered an alias on the client for the IP address. Can you
ping
> > the
> > > > publisher - by IP and by HostName. If not by Hostname then add an
entry
> > into
> > > > the HOSTS file on the subscriber.
> > > > HTH,
> > > > Paul Ibison
> > > >
> > > >
> > > >
> >
> >
> >

Relevant Pages

  • Re: SQL2000 - Merge Replication - Timeout error
    ... The timeout is in your publisher and distributor server, ... Then, update the database statistics. ... Run profiler on the subscriber to see what is going on? ...
    (microsoft.public.sqlserver.replication)
  • Re: Upgrading merge replication to 2005
    ... Subscriber to a merge publication can be any version no later than the ... So it would work with a SQL 2000 publisher and SQL 2000 ... Subscriber, but not a SQL 2005 Subscribers. ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • 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....
    ... Perhaps what we are attempting to accomplish is beyond the abilities of Sql Server? ... I thought that we could set up Publication and configure it for anonymous pull subscriptions across the internet. ... > on the Subscriber), and then use the name in the Client Network Utility. ...
    (microsoft.public.sqlserver.replication)
  • Re: Still having DMZ Problems
    ... can connect to the Publisher in the DMZ, ... this particular Subscriber server is publishing to this DMZ server (One way ... being able to retrieve info about publications on the DMZ Server AND I get an error message about not being able to retrieve info about the Domain account that is the Service startup account for Sql Agent on the Subscriber. ...
    (microsoft.public.sqlserver.replication)
Loading