none
ntfrs 13508

    Question

  • This is a newly joined Windows 2012 [dcserver-01]DC (as of the 18 Jan) with  a DC [jjoserver] Windows 2008 R2 as the PDC

    DCDiag /Q shows

        Warning: DsGetDcName returned information for
        \\jjoserver.company.domain, when we were trying to reach DCSERVER-01.
        SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
        ......................... DCSERVER-01 failed test Advertising
        Unable to connect to the NETLOGON share! (\\DCSERVER-01\netlogon)
        [DCSERVER-01] An net use or LsaPolicy operation failed with error 67,
        The network name cannot be found..
        ......................... DCSERVER-01 failed test NetLogons

    can ping jjoserver.company.domain

    repadmin /showreps looks ok

    local dns settings of adpatrr configure correctly i.e. private ip dns1 loopback dns2 also tried ip address of jjoserver


    www.software-kinetics.co.uk Dependable Software

    Tuesday, January 22, 2013 11:20 AM

Answers

  • The error seem to stem from the operations master the Win 2003 server R3 it was showed the infamous  JRNL_WRAP_ERROR.

    To fix:

    1.    Stop File Replication Service on all machines

    2.    On the Operations Master I set the BurFlag to 0xD4.

    3.    Started File Replication Service on the Operations Master.

    4.    On the Windows 2012 Server set the BruFlag to 0xD2.

    5.    Started File Replication Service Windows 2012 Server.

    SYSVOL and NETLOGON are now present on the Service Windows 2012 Server and the NTFrs errors/warning have stopped - Yay!.


    www.software-kinetics.co.uk Dependable Software

    Wednesday, January 23, 2013 7:42 AM
  • Check to see if the sysvol and netlogon shares are available. It seems this is a similar issue:

    http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/6713c55f-0bc5-4d74-a18b-b867ccc9d059/

    And the solution seems to be a non-authoritative or authoritative restore.

    http://support.microsoft.com/kb/290762 (FRS)

    http://support.microsoft.com/kb/2218556 (DFSR)

    "If setting the authoritative flag on one DC, you must non-authoritatively synchronize all other DCs in the domain. Otherwise you will see conflicts on DCs, originating from any DCs where you did not set auth/non-auth and restarted the DFSR service. For example, if all logon scripts were accidentally deleted and a manual copy of them was placed back on the PDC Emulator role holder, making that server authoritative and all other servers non-authoritative would guarantee success and prevent conflicts.

    If making any DC authoritative, the PDC Emulator as authoritative is preferable, since its SYSVOL contents are usually most up to date.

    The use of the authoritative flag is only necessary if you need to force synchronization of all DCs. If only repairing one DC, simply make it non-authoritative and do not touch other servers."


    http://mariusene.wordpress.com/





    • Edited by Marius Ionut Ene Wednesday, January 23, 2013 12:06 AM
    • Marked as answer by Normski Wednesday, January 23, 2013 7:42 AM
    Tuesday, January 22, 2013 11:39 PM

All replies

  • Check to see if the sysvol and netlogon shares are available. It seems this is a similar issue:

    http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/6713c55f-0bc5-4d74-a18b-b867ccc9d059/

    And the solution seems to be a non-authoritative or authoritative restore.

    http://support.microsoft.com/kb/290762 (FRS)

    http://support.microsoft.com/kb/2218556 (DFSR)

    "If setting the authoritative flag on one DC, you must non-authoritatively synchronize all other DCs in the domain. Otherwise you will see conflicts on DCs, originating from any DCs where you did not set auth/non-auth and restarted the DFSR service. For example, if all logon scripts were accidentally deleted and a manual copy of them was placed back on the PDC Emulator role holder, making that server authoritative and all other servers non-authoritative would guarantee success and prevent conflicts.

    If making any DC authoritative, the PDC Emulator as authoritative is preferable, since its SYSVOL contents are usually most up to date.

    The use of the authoritative flag is only necessary if you need to force synchronization of all DCs. If only repairing one DC, simply make it non-authoritative and do not touch other servers."


    http://mariusene.wordpress.com/





    • Edited by Marius Ionut Ene Wednesday, January 23, 2013 12:06 AM
    • Marked as answer by Normski Wednesday, January 23, 2013 7:42 AM
    Tuesday, January 22, 2013 11:39 PM
  • The error seem to stem from the operations master the Win 2003 server R3 it was showed the infamous  JRNL_WRAP_ERROR.

    To fix:

    1.    Stop File Replication Service on all machines

    2.    On the Operations Master I set the BurFlag to 0xD4.

    3.    Started File Replication Service on the Operations Master.

    4.    On the Windows 2012 Server set the BruFlag to 0xD2.

    5.    Started File Replication Service Windows 2012 Server.

    SYSVOL and NETLOGON are now present on the Service Windows 2012 Server and the NTFrs errors/warning have stopped - Yay!.


    www.software-kinetics.co.uk Dependable Software

    Wednesday, January 23, 2013 7:42 AM