Push replication, firewall, woe is me

  • I have the following set up:

    server1 - wink2k server - inside the firewall, live database, created a local admin user and made the SQL Server agent run with it. Made the user an sa and gave it database owner on the replication database.

    server2 - win2k3 server - in the dmz. Want this to maintain a copy of the live database, but no updates. created a local admin user, named it the same as on server1, gave same permissions everywhere, same password.

    I am able to register server2's sql server in EM, although I had to up the timeout to 90 seconds. I can import a database using EM from server1 to server2. Server2 has a hosts file with the ip address of server1, but ping is disallowed.

    I am attempting a simple push replication. The schema and data are on server2 (I simply imported it using EM rather than FTPing) The replication starts and shows "Connecting to subscriber 'server2'" and at exactly the timeout (even if I set it to 10 minutes) I get a failure of "The process could not connect to Subscriber 'server2'" and the error is "SQL Server does not exist or access denied.", not a timeout error.

    I went into the distribution database on the distributor, and changed the push to a no sync, didn't make any difference.

    Pretty much everything I've seen with people having problems with a push also had problems getting the server registered in EM. I'm at a loss and I have to get this working. Any ideas?

  • Try an anonymous pull subscription. It's what I've had to do with a firewall between my distributor and subscriber.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Read up on the protocols and ports that SQL Replication uses. By default SQL Replication uses UNC file sharing, but can be configured to use FTP. I'm guessing that if your SQL Servers are on different sides of the DMZ then you are not going to have SMB traffic (Windows File Sharing) allowed between them.


    Julian Kuiters
    juliankuiters.id.au

  • See this posting.  It probably has to do with the server names between the publisher and subscriber.

    Although you successfully registered the server(subscriber); the name that you registered the subscriber as (on the publisher) should be exactly as it exists at the subscriber.  Since you are going through a firewall into DMZ then you'll probably need to create an alias on the publisher; then register the subscriber using the alias.

    http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=7&messageid=132613#bm132783

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply