Re: Recommended Inter-Site Transport for AD
- From: "Dean Wells [MVP]" <dwells@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 11 Aug 2005 20:04:28 -0400
This is a common misnomer, AD supports only 3 replication transports -
1. encrypted RPC
2. compressed RPC (comes in 2 flavors, 3 assuming you include off)
3. SMTP
Both 1 and 2 support replication of any kind of AD partition, 3 does not
support domain partitions.
The interface represents replication-transport-option #1 as it should be
(RPC), #2 as IP (let's not bother asking why) and #3 once again as it
should be (assuming anyone has ever used SMTP :o)
Changing connection objects in the manner you reference is of no
benefit, I'm afraid either the advice you received is incorrect or your
memory is ;o)
--
Dean Wells [MVP / Directory Services]
MSEtechnology
[[ Please respond to the Newsgroup only regarding posts ]]
R e m o v e t h e m a s k t o s e n d e m a i l
Robert Gordon wrote:
> Current, a number of my internal AD servers are using RPC for their
> default transport, in their NTDS settings. I recall at a conference
> that changing these from RPC to IP for transport is the recommended
> option. Is this still true?
>
> I ask because I am experiencing some replication slowness within my AD
> domain, (Exchange Server SA not being able to start occassionally with
> the error that replication throughout the domain hasn't completed),
> and I'm wondering if changing the transport to IP would help?
.
- Follow-Ups:
- Re: Recommended Inter-Site Transport for AD
- From: Al Mulnick
- Re: Recommended Inter-Site Transport for AD
- References:
- Recommended Inter-Site Transport for AD
- From: Robert Gordon
- Recommended Inter-Site Transport for AD
- Prev by Date: Re: Global catalog question
- Next by Date: GPO Deletion
- Previous by thread: Recommended Inter-Site Transport for AD
- Next by thread: Re: Recommended Inter-Site Transport for AD
- Index(es):
Relevant Pages
|