Results 1 to 2 of 2

Thread: Sysvol/netlogon shares never created new dc2008

  1. #1
    Join Date
    Nov 2011
    Posts
    1

    Sysvol/netlogon shares never created new dc2008

    This is the third 2008 dc with in two weeks, these are the first 2008 dcs on the domain. 10 sites around the US with a VPN between. All three 2008 dcs are in different sites.

    The problem is we sent a tech to the site to add the dc, after the promo he waited thirty minutes or so for sysvol and netlogon to appear which didn't. He then demoted it and promoted it using the same name, which still didn't work.

    From here I took over and demoted it, removed from domain and renamed it. After promoting it again I still do not have the shares.

    I ran a dcdiag which is as follows(changed domain for obvious reasons):


    Directory Server Diagnosis


    Performing initial setup:

    Trying to find home server...

    Home Server = NC-DC02

    * Identified AD Forest.
    Done gathering initial info.


    Doing initial required tests


    Testing server: NC\NC-DC02

    Starting test: Connectivity

    ......................... NC-DC02 passed test Connectivity



    Doing primary tests


    Testing server: NC\NC-DC02

    Starting test: Advertising

    Warning: DsGetDcName returned information for \\ga-dc01.xxxx.com,

    when we were trying to reach NC-DC02.

    SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.

    ......................... NC-DC02 failed test Advertising

    Starting test: FrsEvent

    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.
    ......................... NC-DC02 passed test FrsEvent

    Starting test: DFSREvent

    ......................... NC-DC02 passed test DFSREvent

    Starting test: SysVolCheck

    ......................... NC-DC02 passed test SysVolCheck

    Starting test: KccEvent

    ......................... NC-DC02 passed test KccEvent

    Starting test: KnowsOfRoleHolders

    ......................... NC-DC02 passed test KnowsOfRoleHolders

    Starting test: MachineAccount

    ......................... NC-DC02 passed test MachineAccount

    Starting test: NCSecDesc

    ......................... NC-DC02 passed test NCSecDesc

    Starting test: NetLogons

    Unable to connect to the NETLOGON share! (\\NC-DC02\netlogon)

    [NC-DC02] An net use or LsaPolicy operation failed with error 67,

    The network name cannot be found..

    ......................... NC-DC02 failed test NetLogons

    Starting test: ObjectsReplicated

    ......................... NC-DC02 passed test ObjectsReplicated

    Starting test: Replications

    ......................... NC-DC02 passed test Replications

    Starting test: RidManager

    ......................... NC-DC02 passed test RidManager

    Starting test: Services

    ......................... NC-DC02 passed test Services

    Starting test: SystemLog

    ......................... NC-DC02 passed test SystemLog

    Starting test: VerifyReferences

    Some objects relating to the DC NC-DC02 have problems:
    [1] Problem: Conflict Mangled Value
    Base Object:

    CN=NTDS Settings,CN=NC-DC02,CN=Servers,CN=NC,CN=Sites,CN=Configuration,DC=core-eng,DC=com

    Base Object Description: "DSA Object"

    Value Object Attribute: serverReferenceBL

    Value Object Description: "SYSVOL FRS Member Object"

    Mangled Value:

    CN=NC-DC02\0ACNF:4231ffb8-cd81-45fe-86be-b96cbf6c7d30,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=core-eng,DC=com

    Recommended Action: Check that there is not more than one SYSVOL

    FRS Member Object for this DC, and if so clean up the older

    duplicates.


    [1] Problem: Conflict Mangled Value
    Base Object: CN=NC-DC02,OU=Domain Controllers,DC=core-eng,DC=com

    Base Object Description: "DC Account Object"

    Value Object Attribute: frsComputerReferenceBL

    Value Object Description: "SYSVOL FRS Member Object"

    Mangled Value:

    CN=NC-DC02\0ACNF:4231ffb8-cd81-45fe-86be-b96cbf6c7d30,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=core-eng,DC=com

    Recommended Action: Check that there is not more than one SYSVOL

    FRS Member Object for this DC, and if so clean up the older

    duplicates.


    ......................... NC-DC02 failed test VerifyReferences



    Running partition tests on : ForestDnsZones

    Starting test: CheckSDRefDom

    ......................... ForestDnsZones passed test CheckSDRefDom

    Starting test: CrossRefValidation

    ......................... ForestDnsZones passed test

    CrossRefValidation


    Running partition tests on : DomainDnsZones

    Starting test: CheckSDRefDom

    ......................... DomainDnsZones passed test CheckSDRefDom

    Starting test: CrossRefValidation

    ......................... DomainDnsZones passed test

    CrossRefValidation


    Running partition tests on : Schema

    Starting test: CheckSDRefDom

    ......................... Schema passed test CheckSDRefDom

    Starting test: CrossRefValidation

    ......................... Schema passed test CrossRefValidation


    Running partition tests on : Configuration

    Starting test: CheckSDRefDom

    ......................... Configuration passed test CheckSDRefDom

    Starting test: CrossRefValidation

    ......................... Configuration passed test CrossRefValidation


    Running partition tests on : core-eng

    Starting test: CheckSDRefDom

    ......................... core-eng passed test CheckSDRefDom

    Starting test: CrossRefValidation

    ......................... core-eng passed test CrossRefValidation


    Running enterprise tests on : xxxx.com

    Starting test: LocatorCheck

    ......................... xxxx.com passed test LocatorCheck

    Starting test: Intersite

    Doing intersite inbound replication test on site NC:
    ......................... xxxx.com passed test Intersite

  2. #2
    Join Date
    Jul 2011
    Posts
    334

    Re: Sysvol/netlogon shares never created new dc2008

    You can perform D4 (Auth) restore on healthy DC for this problem where SYSVOl and NETLOGON shares are accessible. After this you will have to perform D2 (Non-auth) on problem DC.

    NOTE: You must take SYSVOL folder backup.

Similar Threads

  1. Sysvol and Netlogon Security Permissions
    By Peach in forum Active Directory
    Replies: 2
    Last Post: 15-12-2009, 01:47 AM
  2. Missing SYSVOL and NETLOGON
    By Terry in forum Windows Server Help
    Replies: 3
    Last Post: 06-11-2009, 02:16 PM
  3. netlogon and sysvol shares missing
    By NGV BalaKrishna in forum Active Directory
    Replies: 3
    Last Post: 21-10-2009, 08:01 AM
  4. Sysvol contents missing and no NetLogon share
    By Mauricio Botero in forum Active Directory
    Replies: 5
    Last Post: 12-11-2007, 10:58 AM
  5. missing sysvol and netlogon
    By Dan in Kalamazoo in forum Windows Server Help
    Replies: 1
    Last Post: 13-02-2007, 07:22 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,703,150.81110 seconds with 16 queries