Multi Domain Replication Security Issue

Discussion in 'microsoft.public.sqlserver.securitytools' started by asd, Jan 25, 2006.

  1. asd

    asd Guest

    Hello everyone,

    We have a bit of a problem with replication between two SQL servers
    belonging to different domains.

    Basically we have two active directory domains: DomA and DomB (neither of
    them is local domain).

    Each of then has a SQL Server 2000 Enterprise edition installed with SP3.

    There is a database on DomA that has to be merge replicated with DomB
    through dial-up connection.

    We establish the dial-up connection (RRAS is running on DomA) between the
    domains and create a pull subscription on DomB but when we start the
    synchronisation process we always get the error that server in DomA does not
    exist or access denied.

    Just to mention that the replication agent on DomB is set up to run with sql
    server login 'sa' (checked the password a hundred times).

    Any ideas appreciated. We would not mind switching to active directory
    enabled replication between the two is someone could give us guidelines.

    Thank you all in advance.

    Best regards,

    GAZ
     
    asd, Jan 25, 2006
    #1
    1. Advertisements

  2. Create an admin account on both servers with the same name and password.
    Have sql server agent run under this account on both servers. Use the
    impersonate the sql server agent option.
     
    Hilary Cotter, Jan 25, 2006
    #2
    1. Advertisements

  3. asd

    asd Guest

    Thanks for the aswer but unfortunately it does not work. We still get the
    same message 'SQL server does not exist or access denied.'

    We can ping the server in question with both the IP address and its name,
    but still we cannot run the replication.
     
    asd, Jan 25, 2006
    #3
  4. Is the sa account you are using in your agent to connect to the subscriber
    the publisher sa account or the subscriber one? It should be the publisher
    one.

    This could be a name resolution problem or a account problem. It sound like
    its not a name resolution problem as you can connect to the publisher and
    configure the pull. So it probably is an account problem.
     
    Hilary Cotter, Jan 25, 2006
    #4
  5. asd

    asd Guest

    Both sa accounts have the same password. Whatever we try there are no
    results. We shall try to create a clean domain B installation and start from
    scratch. Maybe we shall have better luck this time.

    Still, any ideas and suggestions are welcome.

    BR,

    GAZ
     
    asd, Jan 26, 2006
    #5
  6. is xp_cmdshell enabled on the subscriber?
     
    Hilary Cotter, Jan 26, 2006
    #6
  7. asd

    asd Guest

    Yes. It can be executed and it works like a charm. We are just in the
    process of setting up the new domain to try this from scratch. Let you all
    know how it went.

    BR,

    GAZ
     
    asd, Jan 27, 2006
    #7
  8. asd

    asd Guest

    We reinstalled the DomB and now everything works like clockworks. We haven't
    the foggiest what the problem was but for now ignorance is a bliss. We'll
    have to set up a new network soon with the same parameters and we'll keep a
    keener eye on things.

    Thanks everyone for your help.


    GAZ
     
    asd, Jan 29, 2006
    #8
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.