No announcement yet.

ntFRS issues with new DC

  • Filter
  • Time
  • Show
Clear All
new posts

  • ntFRS issues with new DC


    Windows 2003 R2

    3 DC's one domain


    Just depricated and removed a DC due to failing hardware, replaced with new DC, the new DC cannot replicate with the other DCs, and vise versa, (at least not fully).

    Just added a new workstation to the domain, and the DC with the replication issues is the only one showing the new computer object, the other DCs never see it.

    I have went through tons of articles from microsoft, some of which uncovered some issues which were resolved, (locking down RPC ports, confirming firewall rules, etc). But the new DC still will not replicate.

    We have many 13508 NtFRS errors in the event log, but no 13509s, and the other DCs never see newly added computer objects when they appear on the DC with the issue.

    Has anyone else encountered this and been sucsessful in fixing it?

  • #2
    Re: ntFRS issues with new DC

    Update and a little more background:

    Our DCs do not run DNS or DHCP, we use an appliance for both of these services, and the appliances do not allow dynamic registration.

    I found this when restarting the testing

    dcdiag output on problematic DC:

    Domain Controller Diagnosis
    Performing initial setup:
    Done gathering initial info.
    Doing initial required tests

    Testing server: Default-First-Site-Name\PROBLEM_DC
    Starting test: Connectivity
    The host could not be resolved to an
    IP address. Check the DNS server, DHCP, server name, etc
    Although the Guid DNS name
    couldn't be resolved, the server name (
    resolved to the IP address (x.x.x.x) and was pingable. Check
    that the IP address is registered correctly with the DNS server.
    ......................... PROBLEM_DC failed test Connectivity

    Added a host alias in DNS to that resolves to PROBLEM_DC IP address, and viola! replication works.
    Last edited by georgeeye; 5th August 2011, 17:55. Reason: fixed typos