FRS Sysvol Domain Controller sync

Discussion in 'Windows Server' started by Adrian Marsh (NNTP), Jul 31, 2009.

  1. Hi All,

    I'm trying to master our DCs here. I'm replacing a DC in one site, and
    adding a new site.

    Setup: 3 DCs in "Stella" (serv 1,8 and 9), and 1 DC in "Wales" (serv10)

    I'm testing replication, but putting a small .txt file into
    sysvol\<domain> and watching as it replicates around.

    Everything in the "Stella" site seems to be working OK. I put the file
    in place, and everything replicates.

    However, the DC in Wales, only seems to replicate if I restart the FRS
    service (between sites).

    DNS seems ok, and this is a newly added DC. Its not a "bridgehead".
    I get the below error log on serv10.

    I can resolve ubiq-serv1 with no problems on ubiq-serv10.
    DNS is held by serv1 and serv9, bother entered as the DNS servers for

    dcdiag on serv10 passes everything except the FRS event log (frsevent)
    where it lists this event.

    netdiag passes all the tests on serv10
    (theres a warning from WINS about Workstation service 03 messenger service)

    I've been looking at NTDS Settings for inter-site transport, and have
    added 2 links between serv1 and serv10. But not sure if thats right.


    Event Type: Warning
    Event Source: NtFrs
    Event Category: None
    Event ID: 13508
    Date: 31/07/2009
    Time: 14:01:46
    User: N/A
    Computer: UBIQ-SERV10
    The File Replication Service is having trouble enabling replication from
    UBIQ-SERV1 to UBIQ-SERV10 for c:\windows\sysvol\domain using the DNS
    name UBIQ-SERV1.ubiquisys.local. FRS will keep retrying.
    Following are some of the reasons you would see this warning.

    [1] FRS can not correctly resolve the DNS name
    UBIQ-SERV1.ubiquisys.local from this computer.
    [2] FRS is not running on UBIQ-SERV1.ubiquisys.local.
    [3] The topology information in the Active Directory for this replica
    has not yet replicated to all the Domain Controllers.

    This event log message will appear once per connection, After the
    problem is fixed you will see another event log message indicating that
    the connection has been established.

    For more information, see Help and Support Center at
    0000: 0d 00 00 00 ....
    Adrian Marsh (NNTP), Jul 31, 2009
    1. Advertisements

  2. That all said, I have another FRS/DFS share between serv1 and serv10
    (ClientApps) where replication works fine.
    Adrian Marsh (NNTP), Jul 31, 2009
    1. Advertisements

  3. Hello Adrian,

    If no external DNS servers are used i think we can exclude DNS.

    Did you check on the new DC that sysvol and netlogon folders exist and you
    can access them?

    Which OS version and SP/patch level do you use?

    If you add a new site and you configure AD sites and services with the new
    site and subnet and move the DC to it, replication connections will be built

    Did you add serv10 in the new site to the domain or prepared it ion the main
    site and then shipped it to it's own? During promotion you should always
    use only one DC/DNS on the NIC to replicate from and if all is replicated
    and checked with dcdiag /v and repadmin /showrepl then change DNS for your

    Best regards

    Meinolf Weber

    Meinolf Weber [MVP-DS], Aug 2, 2009
    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.