Replication with Publisher and distributor in different domains

Question

Replication with Publisher and distributor in different domains

Aashini Shah

Ten Centuries

Points: 1129
More actions
September 27, 2011 at 9:30 am

#258013

Hello,
I need to set up transactional replication where publisher and dedicated distributor are in different domains.
First of all, is it possible to have transactional replication possible with Pub and dist in different domains?
If yes, here is the more info.
Distributor is 2008 R2 version in domain A and Publisher is 2005 version in domain B. Distributor and subscribers are in the same domain so there is no connectivity issue there.
Both the domains are trusted.
Publisher has to use Distributor_admin account to connect to distributor.
But I am not sure under what domain or local account should the log reader and snapshot agent security configured while creating publication to make it work?
Thanks,
:unsure:

Viewing 10 posts - 1 through 9 (of 9 total)

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

Derrick Smith SSChampion Points: 10833 More actions · Answer 1

You will need to use a domain account for this. Pick one and give it the appropriate access on the publisher, and then set the log reader/etc to use that account.

Aashini Shah Ten Centuries Points: 1129 More actions · Answer 2

Derrick Smith (9/27/2011)
You will need to use a domain account for this. Pick one and give it the appropriate access on the publisher, and then set the log reader/etc to use that account.

I tried adding domain accounts to both the servers ( I mean domain A account to domain B and vice versa and made them sysadmin ). It has not worked so far.

I guess, if Publishr and distributor can exist in different domain for sure, I will try to figure out the permissions.

Can someone please confirm that Pub and dist can be on different trusted domains?

Thanks,

Aashini

Derrick Smith SSChampion Points: 10833 More actions · Answer 3

I've set it up that way in the past but if you're having issues on your network getting it to work you could always try using a SQL login instead of a domain account (since sql logins are independent anyway).

Derrick Smith SSChampion Points: 10833 More actions · Answer 4

Derrick Smith

SSChampion

Points: 10833

September 27, 2011 at 11:49 am

#1387384

edit - double clicked...whoops.

Aashini Shah Ten Centuries Points: 1129 More actions · Answer 5

Derrick Smith (9/27/2011)
I've set it up that way in the past but if you're having issues on your network getting it to work you could always try using a SQL login instead of a domain account (since sql logins are independent anyway).

Thanks Derrick

As long as I have confirmation from somene that it is possible, I will figure out the issue with connectivity. I just wanted to verify the cross domain thing as I have tried all kind of set ups in last 2 days- using sql logins rather than impersonating security, domain A login with sysadmin permissions, domain B login with sysadmin permission, full name i.e database.domain.edu\instance name, with and without port etc..So, i had tarted questioning whether this is the limitation of replication.

Funny thing is that I can ping Pub from distributor and dist from publisher. So, I never thought I will have such a hard time setting up this replication.

Oh well..Thanks for the reply. I really appreciate it.

Derrick Smith SSChampion Points: 10833 More actions · Answer 6

If nothing is working for you, it sounds like you might have some other issues...possibly network related.

Can you ping the publisher from the distributor using only the hostname (not the FQDN)? I've had to work around issues like that by adding a hosts file entry with a dummy name and the FQDN to the server I'm trying to connect from.

What errors are you getting when you try to connect with either a domain account or with a sql login?

It's absolutely doable and it might just be a simple config setting and not something you're doing.

Aashini Shah Ten Centuries Points: 1129 More actions · Answer 7

Ok. It's fixed now.

I had to go to replication related linked servers on publisher and distributor, retype the password for sql accounts to be used for connection and enable 'allow data access' option.

Never had to do this before but this is what it is.

Aashini

Jared SSC Guru Points: 61793 More actions · Answer 8

Just a note: If the servers are on 2 different domains, you will not be able to use a domain account because one will never authenticate to the other. SQL Server authentication is the only way to do this.

Thanks,

Jared

Jared
CE - Microsoft

Bipsy SSCrazy Points: 2207 More actions · Answer 9

Bipsy

SSCrazy

Points: 2207

October 3, 2011 at 2:09 am

#1389334

Set SPN for your domain user.