locked
Exchange fails to communicate with Active Directory RRS feed

  • Question

  • Hi,

    I have Active Directory running on Windows 2008 R2 and Exchange 2007.  I usually get an error " active directory operation failed on dc. This error could have been caused by user input or by the Active Directory being unavailable. Please retry at a later time. Additional information : Active Directory response: The operation was aborted because the client side timeout limit was exceeded. It was running command "get-recipient -Result '500' -SortBy 'DisplayName' -RecipientType 'DynamicDistributionGroup' , 'UserMailbox' ,'MailContact' , 'MailUniversalDistributionGroup' , MailUniversalSecurityGroup' , 'MailNonUniversalGroup'. 

    Now only if I reboot the DC the exchange starts to work. Has anyone come across this error. 

    Any suggestions please


    Sujit
    Monday, May 9, 2011 8:48 AM

Answers

  • Fix what's wrong with the DC.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    • Marked as answer by Terence Yu Thursday, May 19, 2011 8:34 AM
    Monday, May 9, 2011 5:14 PM
  • Hi
       According to your saying, you’d better to run Dcdiag to check your AD.
       This article is about dcdiag
       http://technet.microsoft.com/en-us/library/cc731968(WS.10).aspx
       If you see any error , you can post it to
      
     http://social.technet.microsoft.com/Forums/en-us/category/windowsserver
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Terence Yu Thursday, May 19, 2011 8:34 AM
    Tuesday, May 10, 2011 5:20 AM
  • Is your DC your Exchange server?  Where does it register in DNS?  Does it point to itself for DNS?

    Check your DNS registrations, something is amiss.  Next time, try restarting the netlogon service on the DC (will force it to reregister).  Check your DNS configuration. 

    J

    • Marked as answer by Terence Yu Thursday, May 19, 2011 8:34 AM
    Tuesday, May 10, 2011 8:35 PM

All replies

  • Fix what's wrong with the DC.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    • Marked as answer by Terence Yu Thursday, May 19, 2011 8:34 AM
    Monday, May 9, 2011 5:14 PM
  • Hi
       According to your saying, you’d better to run Dcdiag to check your AD.
       This article is about dcdiag
       http://technet.microsoft.com/en-us/library/cc731968(WS.10).aspx
       If you see any error , you can post it to
      
     http://social.technet.microsoft.com/Forums/en-us/category/windowsserver
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Terence Yu Thursday, May 19, 2011 8:34 AM
    Tuesday, May 10, 2011 5:20 AM
  • Thank you!! 

    When login to the DC i see the things works fine. Able to pull user informations too.

    Is there any thing to do with network performance


    Sujit
    Tuesday, May 10, 2011 6:14 PM
  • Is your DC your Exchange server?  Where does it register in DNS?  Does it point to itself for DNS?

    Check your DNS registrations, something is amiss.  Next time, try restarting the netlogon service on the DC (will force it to reregister).  Check your DNS configuration. 

    J

    • Marked as answer by Terence Yu Thursday, May 19, 2011 8:34 AM
    Tuesday, May 10, 2011 8:35 PM