Active Directory replication between sites

[Guest]

Hi,

Windows 2003 AD, Single Forest, single domain.I think there maybe something
incorrect with my understadning with AD replication between sites. I go into
AD sites and services and drill down into the sites until I find NTDS
settings. I highlight this on the left and on the right there appears a SITE
link. So I double click this site link and the transport is "IP". I thought
it could perform RPC between sites, so then I try and change it to RPC...the
replication stops working, and eventually it switches itself back to "IP". Is
there something I am doing wrong here?? I would like to use RPC for the
transport dialogue box all the time...
Any help would be greatly appreciated.
Thanking You
Elvis

 

[ptwilliams]

IP *is* RPC.

It's short for RPC over IP; and SMTP over IP.

By default, everything uses RPC.


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

Hi,

Windows 2003 AD, Single Forest, single domain.I think there maybe something
incorrect with my understadning with AD replication between sites. I go into
AD sites and services and drill down into the sites until I find NTDS
settings. I highlight this on the left and on the right there appears a SITE
link. So I double click this site link and the transport is "IP". I thought
it could perform RPC between sites, so then I try and change it to RPC...the
replication stops working, and eventually it switches itself back to "IP".
Is
there something I am doing wrong here?? I would like to use RPC for the
transport dialogue box all the time...
Any help would be greatly appreciated.
Thanking You
Elvis

 

[Herb Martin]

Hi,

Windows 2003 AD, Single Forest, single domain.I think there maybe something
incorrect with my understadning with AD replication between sites. I go into
AD sites and services and drill down into the sites until I find NTDS
settings. I highlight this on the left and on the right there appears a SITE
link. So I double click this site link and the transport is "IP". I thought
it could perform RPC between sites, so then I try and change it to RPC

pt indicated this, but I will elaborate a bit....

Both Intrasite and Intersite replication use RPC/IP
(it's IP and using the RPC for comminuction over that
protocol)

Technically SMTP can be used for Intrasite replication
but that is used by so few it is not worth considering for
small domains without very special circumstance.

Microsoft TENDS to call the Intrasite RPC/IP just "RPC"
and to call INTERsite RPC/IP just "IP".

What you have likely done is try to use intrasite replication
for a Intersite sitelink and thus broken it.

We practially NEVER have to mess with IntraSite replication
protocols -- they just work.

....the

replication stops working, and eventually it switches itself back to "IP". Is
there something I am doing wrong here?? I would like to use RPC for the
transport dialogue box all the time...
Any help would be greatly appreciated.

Yes, don't do that. <grin>

 

[Ryan Hanisco]

Elvis,

Remember that RPC in itself is not routable. That is why a single site that
traverses subnets across a router runs into problems. The solution is to
designate sites and encapsulate RPC in IP. This allows Intersite
replication.

When using SMTP to replicate this can replicate the major objects, but not
all of the attributes. this is useful in specific circumstances where you
need the objects but have access to the main site for the full attribute
set. This is why this is almost never used. Why replicate, when you'll
have to go tot the core to authenticate anyway.

 

[Herb Martin]

Elvis,

Remember that RPC in itself is not routable.

RPC is only "not-routable" in the sense that it is
NOT a "network layer" protocol and so has nothing
to do with routing directly.

It is CERTAINLY routable in the sense that when
running with IP (as it is in all AD replication using it)
then it routes just fine.

In the same sense that SMB, DNS, or any other specific
protocol OVER IP is routable.

That is why a single site that
traverses subnets across a router runs into problems.

Not due to RPC it doesn't.

RPC (over IP) routes just fine.

And the only RPC we are talking about in
replication is RPC/IP no matter what the MMC
calls it.

RPC over NetBEIU is not routable but that is due
to NetBEIU and isn't the issue in modern systems.

The solution is to
designate sites and encapsulate RPC in IP. This allows Intersite
replication.

And intrasite replication too -- even with routers.

When using SMTP to replicate this can replicate the major objects, but not
all of the attributes.

It has nothing directly to do with "attributs" but
rather that SMPT (AD) replication only replicates
BETWEEN DIFFERENT domains.

It replicates only Forest wide (not domain specific)
info -- which may be any attribute so marked.

this is useful in specific circumstances where you
need the objects but have access to the main site for the full attribute
set.

What you have problaby confused her is that GC replication
is forest wide (among the GC set in the forest).

This is why this is almost never used. Why replicate, when you'll
have to go tot the core to authenticate anyway.

Having to have separate domains is likely the main
reason it isn't used much, and the fact that most people
who try to use it don't understand the need and setup of
the Certificates it requires.

 

[Guest]

Hi,

Firstly thank you all for your responses. They have helped me tremendously.
After reading a few articles I now understand the technoligies. Thank you for
verifying that for me!! Now my AD is not spitting out any errors and its
working
Thanks Again..
Elvis

 

[Herb Martin]

Hi,

Firstly thank you all for your responses. They have helped me tremendously.
After reading a few articles I now understand the technologies. Thank you for
verifying that for me!! Now my AD is not spitting out any errors and its
working

You are welcome. Glad to hear it's working for
you.