none
DCDiag, There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. failed DFSREvent

    Question

  • There are warning or error events within the last 24 hours after the SYSVOL has been shared.  Failing SYSVOL replication problems may cause Group Policy problems. failed DFSREvent.  This is a new build and I can ping the other DC by ip address, name and fqdn.  What am i missing?
    Thursday, May 30, 2013 3:40 PM

Answers

All replies

  • Hello, maybe your sysvol have not completed the initialization phase. I will give it some more time. Also, can you post he complete dcdiag /v log to the forum? If you do, remember to remove all references to your network.

    Isaac Oben MCITP:EA, MCSE,MCC View my MCP Certifications

    Thursday, May 30, 2013 4:09 PM
  • Hi,

    What events are you seeing in your event log?

    Have you gone through this article for troubleshooting missing sysvol/netlogon  

    http://support.microsoft.com/kb/257338

    Please also check the similar thread:

    SYSVOL and NETLOGON folders not shared

    http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/d1813eb8-e784-4fae-a448-5e4415ca406b

    If you have any feedback on our support, please click here

    Regards.


    Vivian Wang
    TechNet Community Support

    Friday, May 31, 2013 7:51 AM
    Moderator
  • Hi,

    Just checking in to see if there is any update about the issue. Please let us know if you would like further assistance.

    Regards.

    If you have any feedback on our support, please click here


    Vivian Wang
    TechNet Community Support

    Tuesday, June 04, 2013 9:30 AM
    Moderator
  • Agree with other experts, run net share from elevated command prompt to know whether Netlogon and SYSVOL are shared or not. Also check FRS logs for event IDs 13568.

    Before you proceed any furhter I would suggest you to tell us how many DCs are there in the domain, is SYSVOL migrated to DFSR ? 

    Let us know more about your domain, so that we can assist you better.

    Tuesday, June 04, 2013 9:52 AM
  • Run diagnostics and post results per the Blog below.
    http://blogs.dirteam.com/blogs/paulbergson/archive/2009/01/26/troubleshooting-active-directory-issues.aspx

    --
     Paul Bergson
     MVP - Directory Services
     MCITP: Enterprise Administrator
     MCTS, MCT, MCSE, MCSA, Security+, BS CSci
     2008, Vista, 2003, 2000 (Early Achiever), NT4
     http://www.pbbergs.com    Twitter @pbbergs
     http://blogs.dirteam.com/blogs/paulbergson

     Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, June 04, 2013 12:00 PM
    Moderator
  • hi,

    Can be fixed by making the following changes in the registry:

    1. Open the Windows registry editor “regedit”.
    2. Navigate to “HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesDfs”.
    3. Add NTDS to the list of “DependOnService”.
    4. Create a DWORD with the name “DelayedAutostart” and give it a value of 1.

    This forces the DFS Namespace service wait until Active Directory has been initialized.

    Thanks & Regards,

    Pradeep

    Thursday, October 16, 2014 10:12 AM