Recommended Inter-Site Transport for AD

Discussion in 'Active Directory' started by Robert Gordon, Aug 12, 2005.

  1. 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?
    Robert Gordon, Aug 12, 2005
    1. Advertisements

  2. 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 :eek:)

    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], Aug 12, 2005
    1. Advertisements

  3. Robert Gordon

    Al Mulnick Guest

    To add to that, you should really troubleshoot your replication issue (to
    either verify that there is one and what the root cause is, else that there
    is no "problem" with replication) before making changes. It'll save you
    loads of trouble later.


    Al Mulnick, Aug 12, 2005
    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.