locked
DCDIAG test error after upgrade AD server 2008 R2 RRS feed

  • Question

  • Dear All,

    I have upgdare AD to Server 2008, but when i run dcdiag on server dc 2008, i got error information.

    Result dcdiag:

    Directory Server Diagnosis


    Performing initial setup:

       Trying to find home server...

       Home Server = id-dc-001

       * Identified AD Forest.
       Ldap search capabality attribute search failed on server id-dc-002, return

       value = 81
       Got error while checking if the DC is using FRS or DFSR. Error:

       Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail

       because of this error.


    if i run dcdaig on server dc 2003, there's no problem.
    Why this error happen?

    i crosscheck using repadmin, and the replication successfull.

    Thank you

    Regards,

    Endrik

    Tuesday, February 2, 2010 8:48 AM

Answers

  • Endrik,
    verify whether the condition described in http://blogs.technet.com/askds/archive/2010/01/27/dcdiag-advertising-test-with-error-81.aspx does not apply in your case (i.e. you have a stale NTDS Settings object with a duplicate dNSHostName attribute). The blog provides a method for identifying whether this is the case and explains how to resolve the issue...

    hth
    Marcin
    • Marked as answer by Tim Quan Friday, February 26, 2010 3:52 AM
    Wednesday, February 3, 2010 12:39 PM
  • Hello,

    I have two DCs. A 2008 R2 and a 2003. I just upgraded the 2003 server to 2008 R2. I'm getting the same results with dcdiag. I use teaming on my NICs.

    I breaked team and disabled TCP Offload and recreated team.

    After that i has resloved my problem....

    So i sagestted the above...

    Not sure in your case...

    Thanks

    Rajesh J S
    • Marked as answer by Tim Quan Friday, February 26, 2010 3:52 AM
    Wednesday, February 3, 2010 1:09 PM

All replies

  • Hello,

    Do you have teamed network cards.....

    If you have please break the team and re-create it...

    And check the DC diag....

    Regards
    Rajesh J S
    Tuesday, February 2, 2010 9:08 AM
  • Dear Rajesh,

    I dont know, we are using blade server IBM.

    i think i dont have team NIC.

    Thank you

    Regards,

    Endrik 
    Tuesday, February 2, 2010 9:16 AM
  • Hello,

    Can you check by Disable TCP Offload


    http://www.alacritech.com/Support/FAQs/DisableOffload.aspx

    Regards
    Rajesh J S
    Wednesday, February 3, 2010 11:21 AM
  • Dear  Rajesh, 

    it is easy to disabled TCP Offload, but for what?
    why corellation with Dcdiag?

    could explain to me please..?


    Regards.

    Endrik
    Wednesday, February 3, 2010 11:33 AM
  • Endrik,
    verify whether the condition described in http://blogs.technet.com/askds/archive/2010/01/27/dcdiag-advertising-test-with-error-81.aspx does not apply in your case (i.e. you have a stale NTDS Settings object with a duplicate dNSHostName attribute). The blog provides a method for identifying whether this is the case and explains how to resolve the issue...

    hth
    Marcin
    • Marked as answer by Tim Quan Friday, February 26, 2010 3:52 AM
    Wednesday, February 3, 2010 12:39 PM
  • Hello,

    I have two DCs. A 2008 R2 and a 2003. I just upgraded the 2003 server to 2008 R2. I'm getting the same results with dcdiag. I use teaming on my NICs.

    I breaked team and disabled TCP Offload and recreated team.

    After that i has resloved my problem....

    So i sagestted the above...

    Not sure in your case...

    Thanks

    Rajesh J S
    • Marked as answer by Tim Quan Friday, February 26, 2010 3:52 AM
    Wednesday, February 3, 2010 1:09 PM