Announcement

Collapse
No announcement yet.

dcdiag error

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • dcdiag error

    Ive just installed the 2nd DC in a child domain, set DNS up and then a day or so later the DNS started playing up a bit.

    I decided to do a dcdiag & got the following results:

    Directory Server Diagnosis
    Performing initial setup:
    Trying to find home server...
    Home Server = BU-DC01
    * Identified AD Forest.
    Done gathering initial info.
    Doing initial required tests
    Testing server: BU-SH\BU-DC01
    Starting test: Connectivity
    ......................... BU-DC01 passed test Connectivity
    Doing primary tests
    Testing server: BU-SH\BU-DC01
    Starting test: Advertising
    ......................... BU-DC01 passed test Advertising
    Starting test: FrsEvent
    ......................... BU-DC01 passed test FrsEvent
    Starting test: DFSREvent
    ......................... BU-DC01 passed test DFSREvent
    Starting test: SysVolCheck
    ......................... BU-DC01 passed test SysVolCheck
    Starting test: KccEvent
    ......................... BU-DC01 passed test KccEvent
    Starting test: KnowsOfRoleHolders
    ......................... BU-DC01 passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    ......................... BU-DC01 passed test MachineAccount
    Starting test: NCSecDesc
    ......................... BU-DC01 passed test NCSecDesc
    Starting test: NetLogons
    ......................... BU-DC01 passed test NetLogons
    Starting test: ObjectsReplicated
    ......................... BU-DC01 passed test ObjectsReplicated
    Starting test: Replications
    ......................... BU-DC01 passed test Replications
    Starting test: RidManager
    ......................... BU-DC01 passed test RidManager
    Starting test: Services
    ......................... BU-DC01 passed test Services
    Starting test: SystemLog
    A warning event occurred. EventID: 0x80050004
    Time Generated: 10/26/2012 12:46:37
    Event String: HP NC382i #48: The network link is down. Check to make sure the network cable is properly connected.
    A warning event occurred. EventID: 0x80050004
    Time Generated: 10/26/2012 12:46:37
    Event String: HP NC382i #5: The network link is down. Check to make sure the network cable is properly connected.
    A warning event occurred. EventID: 0x80050004
    Time Generated: 10/26/2012 12:46:37
    Event String: HP NC382i #50: The network link is down. Check to make sure the network cable is properly connected.
    A warning event occurred. EventID: 0x80050004
    Time Generated: 10/26/2012 12:46:37
    Event String: HP NC382i #49: The network link is down. Check to make sure the network cable is properly connected.
    A warning event occurred. EventID: 0x000003F6
    Time Generated: 10/26/2012 12:47:23
    Event String:
    Name resolution for the name dns.msftncsi.com timed out after none of the configured DNS servers responded.
    An error event occurred. EventID: 0x00000406
    Time Generated: 10/26/2012 12:50:01
    Event String:
    The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or comput
    er. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cy
    cle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery
    of new Group Policy objects and settings. An event will be logged when Group Policy is successful.
    ......................... BU-DC01 failed test SystemLog
    Starting test: VerifyReferences
    ......................... BU-DC01 passed test VerifyReferences

    Running partition tests on : DomainDnsZones
    Starting test: CheckSDRefDom
    ......................... DomainDnsZones passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... DomainDnsZones passed test CrossRefValidation
    Running partition tests on : bu
    Starting test: CheckSDRefDom
    ......................... bu passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... bu passed test CrossRefValidation
    Running partition tests on : ForestDnsZones
    Starting test: CheckSDRefDom
    ......................... ForestDnsZones passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... ForestDnsZones 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 enterprise tests on : bluestone.net
    Starting test: LocatorCheck
    ......................... bluestone.net passed test LocatorCheck
    Starting test: Intersite
    ......................... bluestone.net passed test Intersite


    Ive done the old google search but am struggling to find anything helpful about the GPO error.

    Can anyone help?

  • #2
    Re: dcdiag error

    How many DC do you have?
    Are they set just to point to internal DNS servers?
    cheers
    Andy

    Please read this before you post:


    Quis custodiet ipsos custodes?

    Comment


    • #3
      Re: dcdiag error

      I have x2 DC's on the sub domain. My DC points to DC02 as the primary DNS & then 127.0.0.1 as the secondary DNS, then I have also pointed it at DC01 on the parent domain to keep things in sync.

      Comment


      • #4
        Re: dcdiag error

        Was the GPO error a one-off? Does it still occur?
        What can you see in the event logs about the error?
        cheers
        Andy

        Please read this before you post:


        Quis custodiet ipsos custodes?

        Comment


        • #5
          Re: dcdiag error

          Point your DC to itself, using the actual IP, for the primary then use DC01 as the secondary.

          Comment

          Working...
          X