Question Locked

Active Directory problem

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi everybody,

I am having a problem with my active directory. There was a sudden power outage and my two domain controllers are not responding. I have run dcdiag and gives me the following errors.
I could not be able to see or addd any DNS ZONES and shows me the 4000 4013 DNS event errors. I would appreciate any help.

Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... xxx.COM failed test FsmoCheck

3 replies

by Former member

Event ID 4013 ? DNS Server Active Directory Integration

You can configure the DNS Server service to use Active Directory Domain Services (AD DS) to store zone data. This makes it possible for the DNS server to rely on directory replication, which enhances security, reliability, and ease of administration.
Event Details

Product: Windows Operating System

ID: 4013

Source: Microsoft-Windows-DNS-Server-Service

Version: 6.0

Symbolic Name: DNS_EVENT_DS_OPEN_WAIT

Message:
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. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
Resolve
Troubleshoot AD DS and restart the DNS Server service

The DNS Server service relies on Active Directory Domain Services (AD DS) to store and retrieve information for AD DS-integrated zones. This error indicates that AD DS is not responding to requests from the DNS Server service. Ensure that AD DS is functioning properly, troubleshoot any problems, and then restart the DNS Server service.

For information about troubleshooting AD DS, see Active Directory Troubleshooting Topics (http://go.microsoft.com/fwlink/?LinkId=95789).

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To restart the DNS Server service:

1.

On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager.

2.

In the console tree, expand Roles, expand DNS Server, and then expand DNS.

3.

Right-click the DNS server, click All Tasks, and then click Restart.

If the problem continues, restart the computer and then use Server Manager to confirm that the DNS Server service has started.

To restart the computer:
?

Click Start, click the arrow next to the Lock button, and then click Restart.

To confirm that the DNS Server service has started:

1.
On the DNS server, start Server Manager.

2.
In the console tree, expand Roles, and then click DNS Server.

The System Services list shows the state of the DNS Server service.
Verify

Ensure that Event IDs 4523 and 4524 are being logged and that no events in the range 4000 to 4019 appear in the Domain Name System (DNS) event log.

Please post back if you have any more problems or questions.

This discussion is closed to new replies.