Announcement

Collapse
No announcement yet.

dcdiag errors

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

  • dcdiag errors

    Hello All!, I am experiencing some issues with AD and thought I would drop my dcdiag results to see if anyone had any quick input for me..
    ______________________________

    Domain Controller Diagnosis

    Performing initial setup:
    Done gathering initial info.

    Doing initial required tests

    Testing server: Okoboji\NF-OKOBOJIDC
    Starting test: Connectivity
    ......................... NF-OKOBOJIDC passed test Connectivity

    Doing primary tests

    Testing server: Okoboji\NF-OKOBOJIDC
    Starting test: Replications
    [Replications Check,NF-OKOBOJIDC] No replication recently attempted:
    From CR-EXCHDC2 to NF-OKOBOJIDC
    Naming Context: DC=DomainDnsZones,DC=fnb_domain,DC=local
    The last attempt occurred at 2007-09-04 04:46:46 (about 4 hours ago)
    .
    [Replications Check,NF-OKOBOJIDC] No replication recently attempted:
    From CR-EXCHDC2 to NF-OKOBOJIDC
    Naming Context: DC=ForestDnsZones,DC=fnb_domain,DC=local
    The last attempt occurred at 2007-09-04 04:46:46 (about 4 hours ago)
    .
    [Replications Check,NF-OKOBOJIDC] No replication recently attempted:
    From CR-EXCHDC2 to NF-OKOBOJIDC
    Naming Context: CN=Schema,CN=Configuration,DC=fnb_domain,DC=local
    The last attempt occurred at 2007-09-04 04:46:46 (about 4 hours ago)
    .
    [Replications Check,NF-OKOBOJIDC] No replication recently attempted:
    From CR-EXCHDC2 to NF-OKOBOJIDC
    Naming Context: DC=fnb_domain,DC=local
    The last attempt occurred at 2007-09-04 04:46:46 (about 4 hours ago)
    .
    REPLICATION-RECEIVED LATENCY WARNING
    NF-OKOBOJIDC: Current time is 2007-09-04 09:35:51.
    DC=DomainDnsZones,DC=fnb_domain,DC=local
    Last replication recieved from OE-DC at 2007-07-16 04:57:08.
    DC=ForestDnsZones,DC=fnb_domain,DC=local
    Last replication recieved from OE-DC at 2007-07-16 04:57:09.
    CN=Schema,CN=Configuration,DC=fnb_domain,DC=local
    Last replication recieved from OE-DC at 2007-07-16 04:57:06.
    CN=Configuration,DC=fnb_domain,DC=local
    Last replication recieved from OE-DC at 2007-07-16 04:57:05.
    DC=fnb_domain,DC=local
    Last replication recieved from OE-DC at 2007-07-16 04:57:07.
    ......................... NF-OKOBOJIDC passed test Replications
    Starting test: NCSecDesc
    ......................... NF-OKOBOJIDC passed test NCSecDesc
    Starting test: NetLogons
    ......................... NF-OKOBOJIDC passed test NetLogons
    Starting test: Advertising
    ......................... NF-OKOBOJIDC passed test Advertising
    Starting test: KnowsOfRoleHolders
    ......................... NF-OKOBOJIDC passed test KnowsOfRoleHolders
    Starting test: RidManager
    ......................... NF-OKOBOJIDC passed test RidManager
    Starting test: MachineAccount
    ......................... NF-OKOBOJIDC passed test MachineAccount
    Starting test: Services
    ......................... NF-OKOBOJIDC passed test Services
    Starting test: ObjectsReplicated
    ......................... NF-OKOBOJIDC passed test ObjectsReplicated
    Starting test: frssysvol
    ......................... NF-OKOBOJIDC passed test frssysvol
    Starting test: frsevent
    ......................... NF-OKOBOJIDC passed test frsevent
    Starting test: kccevent
    ......................... NF-OKOBOJIDC passed test kccevent
    Starting test: systemlog
    An Error Event occured. EventID: 0xC0002715
    Time Generated: 09/04/2007 09:04:55
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0xC0001B72
    Time Generated: 09/04/2007 09:11:05
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0xC0002715
    Time Generated: 09/04/2007 09:11:10
    (Event String could not be retrieved)
    ......................... NF-OKOBOJIDC failed test systemlog
    Starting test: VerifyReferences
    ......................... NF-OKOBOJIDC passed test VerifyReferences

    Running partition tests on : DomainDnsZones
    Starting test: CrossRefValidation
    ......................... DomainDnsZones passed test CrossRefValidation

    Starting test: CheckSDRefDom
    ......................... DomainDnsZones passed test CheckSDRefDom

    Running partition tests on : ForestDnsZones
    Starting test: CrossRefValidation
    ......................... ForestDnsZones passed test CrossRefValidation

    Starting test: CheckSDRefDom
    ......................... ForestDnsZones passed test CheckSDRefDom

    Running partition tests on : Schema
    Starting test: CrossRefValidation
    ......................... Schema passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Schema passed test CheckSDRefDom

    Running partition tests on : Configuration
    Starting test: CrossRefValidation
    ......................... Configuration passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Configuration passed test CheckSDRefDom

    Running partition tests on : fnb_domain
    Starting test: CrossRefValidation
    ......................... fnb_domain passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... fnb_domain passed test CheckSDRefDom

    Running enterprise tests on : fnb_domain.local
    Starting test: Intersite
    ......................... fnb_domain.local passed test Intersite
    Starting test: FsmoCheck
    ......................... fnb_domain.local passed test FsmoCheck
    ____________

    Thanks,
    Jason

  • #2
    Re: dcdiag errors

    ummm, looks ok besides the latency.

    do you have two DCs on a WAN link or something? looks like they are having intermittent connectivity issues, but im not a dcdiag master.

    what did you want to know about it?
    its easier to beg forgiveness than ask permission.
    Give karma where karma is due...

    Comment


    • #3
      Re: dcdiag errors

      Hi,

      explain your issues with AD,

      I don't see any "fails" in a log.

      you can run
      Code:
      netdiag /v
      to validate network configuration
      With best regards, Victor

      Comment


      • #4
        Re: dcdiag errors

        You are pretty close to tombstone lifetime period (60 days unless your forest was created on W2K3 SP1 with results in 180 days).
        You really need to sort out the replication issues.

        Please post the output of "netdiag /v" and "dcdiag /v"
        Guy Teverovsky
        "Smith & Wesson - the original point and click interface"

        Comment

        Working...
        X