Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

More on Replication

Status
Not open for further replies.

jcrivera

Technical User
Sep 14, 2000
46
PR
This is my scenario:

I got two SQL Server 7 servers (let's name them A and B).

The firewall has been defined so that server A can't see server B (for data security reasons); however, server B can see server A.

The replication has been configured in such a way that server A is the publisher and server B is both the distributor and the subscriber at the same time.

Now, I got a serious trouble with the Publication Wizard:

If I attempt to run the wizard from server B, the wizard says "No, server B is not the publisher". OK, fine. Let's then define server B as a publisher, too. Then when I attempt to run the wizard again, although both servers are publishers, the wizard doesn't let me to see server A's databases (only those of server B). Trapped.

On the other hand, if I attempt to run the wizard from server A, it works fine up to the point in which I press "Finish", then the wizard begins to configure the parameters. Then, given I specified that server B is the distributor, the wizard cannot complete given the server A can't see the server B. Trapped again.

Could anyone tell me if I'm doing something wrong? Or it's impossible to setup a replication strategy with this network limitations?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top