Sites and Services NTDS Settings Transport

  • Thread starter Thread starter Christopher Owens
  • Start date Start date
C

Christopher Owens

I'm just wondering what the difference in between IP and RPC transports
in Active Directory Sites and Services, under the site->Servers->server
name->NTDS Settings->properties on another server. Under the General
tab, the Transport has 3 options - IP, RPC, and SMTP. Most of what I
can find on the 'net tells the difference between RPC and SMTP, but I
have not found anything that tells the difference between RPC and IP.
Anyone here know?

Thanks.
 
if i'm not mistaken RPC is shown when the CO is for intra-site replication
and IP is shown when the CO is for inter-site replication. As joe says, they
are both the same under water.

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
 
RPC protocol is NOT as same as SMTP & IP protocol.

RPC is used for intra-site replication protocol and it is widely used
in MAPI clients like MS outlook.
SMTP & IP is used as inter-site replication protocol.

Since SMTP is somewhat different from IP and RPC, the data for
replication will be converted as mail format and it is replicated to
its remote bridgehead server, one advantage is there for SMTP is that
OFFLINE replication is also done in SMTP as the source server is not
there and SMTP datas are in queue for replication.


By default RPC protocol is enabled for replication in intra-site
replication. You have to dedicate any one of protocols like SMTP or IP
for inter-site replication and have to set its time frequency for
replication as per your WAN bandwidth.

You can assingh these inter-site transport protocol to a bridgehead
server within in your site for replication.

Hope this information is usefull for you!!

Cheers
 
Wow, you have almost no clue what you are talking about yet are trying
to speak like you have the answers.

First, we aren't talking about protocols. We are talking about the
labels in a GUI tool.

Second, intersite replication is done through RPC over IP. How you could
mess that up I have no clue because it has been documented that way for
over 6 years. Even if you got all of your training through a "make an
MCSE today" program you should have learned about it. The difference
between RPC replication within a site and between sites is three primary
items. The first is the replication topology switches from a ring
(intersite) to a spanning tree (intrasite); this is not configurable.
The second is that change notification is not used by default in
intersite replication; this is configurable. The third is that
compression is used by default in intersite replication; this is
configurable.

Third, SMTP replication is generally not used nor recommended. MSFT only
allows the two forest NCs and R-O NCs to replicate through SMTP, all
other replication MUST occur over RPC connections.

The rest of your post is just so far out there I am not even going to
respond to other than I recommend people NOT listen to what you have to
say.



--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm
 
Fine...

At first instance i like to confirm you that whatever you had
posted is not related to this thread.

We are accepting that you are a genius.

Cheers
 
Thanks for the info - I'm still not sure why MS would give us three
options for the transport setting when two do the same thing. I knew
the transport settings could be RPC over TCP/IP or by SMTP, but when
there were two seperate settings for RPC and IP, it was just a little
confusing. Thanks!
 
I am not sure I understand what you are saying.

You only have a choice for transport protocols for intersite
replication, you have the choice of SMTP or IP (which uses RPC over IP).
Intrasite replication uses IP (aka RPC over IP) and you don't have a
choice there.


--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm
 
When I follow the path that I stated in the first post, under the
Transport option (these are for intersite transports), I have 3 options
- IP, RPC, or SMTP. If it makes any difference, all of my DC's are
running Windows 2003 R2.
 
if you are:
* creating a CO using the RPC over TCP/IP protocol for intersite replication
choose IP
* creating a CO using the RPC over TCP/IP protocol for intrasite replication
choose RPC
* creating a CO using the SMTP protocol choose SMTP

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
Christopher Owens said:
When I follow the path that I stated in the first post, under the
Transport option (these are for intersite transports), I have 3 options
- IP, RPC, or SMTP. If it makes any difference, all of my DC's are
running Windows 2003 R2.
Click to expand...
 
Ah sorry, I hadn't looked at the original post in a while.

Honestly, this isn't something that you need to worry about. Certainly
with automatic connections the values will be autoset and overwrite
anything you do when the system figures out you changed anything.

If you are manually setting up connections (which usually indicates a
bad topology so the KCC can't be used or it isn't making logical
connections[1]) then I would stick with the default which the GUI should
work out for you based on the site links in place. Actually, I am not
even sure if those settings actually end up being used. I would need to
test it and look at the source to verify as the site links are where
most configuration is done to control replication between sites.

Overall, I do not recommend SMTP site links unless you have really
really bad connectivity and obviously the domain is entirely contained
in the foreign site because Domain NCs can not be replicated over SMTP.

joe



[1] Yes yes I know that MSFT recommends you set up manual connections
once you get to X size with 2K but I have very successfully ignored that
advice in several very very large installations in Fortune 5 companies
because the topology was set up logically and site link bridging was
disabled.


--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm



Christopher said:
When I follow the path that I stated in the first post, under the
Transport option (these are for intersite transports), I have 3 options
- IP, RPC, or SMTP. If it makes any difference, all of my DC's are
running Windows 2003 R2.
Click to expand...
 
Back
Top