locked
SharePoint vs Domain Controller RRS feed

  • Question

  • Hi,

    In our company we have multiple domain controllers (like dc-01, dc-02, and dc-03), and large SharePoint FARM. Our system engineers bring down one of the domain controller (ex: dc-03) to do some maintenance task. After that, in SharePoint FARM, we are getting database connectivity errors in eventviewer from one of the WFE. When we bring back the domain controller, WFE starts working. How do we resolve this? How do we identify, is there any services depends on that particular domain controller?

    Regards,
    Prakash


    www.aristonsoft.com - .net 3.5 hosting provider in India
    Monday, June 28, 2010 10:09 AM

Answers

  • It depends on the roles the Domain Controller contains and the DNS settings of your SharePoint Farm. The most likely cause If DC3 hosted DNS and your SharePoint servers were not configured for a second DNS server or unable to resolve the SQL Server Address from the secondary server.. Check to ensure that your DNS servers are configured and available. Then use NSLookup to see if they can resolve your SQL Server Name, use NSLookup Server Name YourDNSServer to set which DNS Server is used for name resolution..

    NSLookup http://support.microsoft.com/kb/200525

     

    -Ivan


    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.
    Monday, June 28, 2010 11:52 AM
  • As Ivan said, sounds like a DNS issue. I would check the IP Configuration on that WFE (look at primary and secondary DNS) to see if it matches the other, healthy servers.

     

    Troy Lanphier

    http://blog.sharepointcookbook.com

    Monday, June 28, 2010 6:18 PM

All replies

  • It depends on the roles the Domain Controller contains and the DNS settings of your SharePoint Farm. The most likely cause If DC3 hosted DNS and your SharePoint servers were not configured for a second DNS server or unable to resolve the SQL Server Address from the secondary server.. Check to ensure that your DNS servers are configured and available. Then use NSLookup to see if they can resolve your SQL Server Name, use NSLookup Server Name YourDNSServer to set which DNS Server is used for name resolution..

    NSLookup http://support.microsoft.com/kb/200525

     

    -Ivan


    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.
    Monday, June 28, 2010 11:52 AM
  • As Ivan said, sounds like a DNS issue. I would check the IP Configuration on that WFE (look at primary and secondary DNS) to see if it matches the other, healthy servers.

     

    Troy Lanphier

    http://blog.sharepointcookbook.com

    Monday, June 28, 2010 6:18 PM
  • Hi Ivan/Troy,

    You are right. It is a DNS issue. Once we updated the correct IP on DNS configuration on particular WFE, everything is fine. Thanks for your help.

    Regards,
    Prakash


    www.aristonsoft.com - .net 3.5 hosting provider in India
    Wednesday, June 30, 2010 9:26 AM