Root Domain Controler not working

Home Forums Microsoft Networking and Management Services Active Directory Root Domain Controler not working

Viewing 1 post (of 1 total)
  • Author
  • #164606

    We have faced an issue during downtime maintenance in Data Center.
    After downtime, we restarted all production servers and root domain controller.
    In our data center, we have 2 node windows clusters for DB and IIS Applications.

    After we restarted rot domain controller, DNS console not opening and active directory related consoles are also not opened.
    And also by using domain user account, not able to login to servers also.
    Also cluster resources was also not worked.
    After long time, and rebooted several time DNS and AD started working.
    In this root domain controller had all 5 FSMO roles.
    And we have additional DC in remote controller also.
    Domain Controller OS: Windows Server 2008 R2 Enterprise.

    We faced 2 times same issue during downtime
    Why this issue will come. Can anybody help me .

    I found event logs in DNS.
    Event ID: 4013
    The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed.The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller.
    And Event ID: 14550
    The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data.
    Event ID: 1129
    The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
    Event ID: 1014
    Name resolution for the name timed out after none of the configured DNS servers responded.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.