|
Home | Site Map | How To | Windows Vista | Case Studies | Articles | Forums | Services | Donations | Careers | About Us | Contact Us| |
|
Event ID 4000 - The DNS server was unable to open Active Directory. Event ID 4004 - The DNS server was unable to complete directory service enumeration of zone %1 Event ID 4015 - The DNS server has encountered a critical error from the Active Directory Symptoms: 1. You have a Windows server running as DNS server. The Event Viewer displays Event ID 4000 - The DNS server was unable to open Active Directory. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code. 2. You have a Windows server running as DNS server. The Event Viewer displays Event ID 4004 - The DNS server was unable to complete directory service enumeration of zone %1. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The event data contains the error. 3. Or Event ID 4015 - The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The event data contains the error. 4. When you run Netdiag.exe, you may receive the following error message: DNS test . . . . . .
. . . . . . . : Passed Note Error 9003 RCODE_NAME_ERROR means that the host name a.b.c.d. does not exist in the DNS servers that are listed in the error message. Causes: 1. If DNS server starts and Active Directory has not started yet and is down, DNS cannot load the zone from AD until AD has started. 2. You have two DCs and they are running DNS. Primary DNS and 2nd DNS servers point to each other as primary and themselves as secondary. One of them has been removed or down. 3. Your internal DNS settings points to your ISP or a router DNS. 4. The behavior will occur if the DNS server IP address is incorrect. 5. The DC either is not configured to use a correct DNS server, or the zone does not have the needed SRV records. 6. The DNS or DC is multihomed computer or RRAS server that register multiple A records.. That may cause a name solution issue. 7. After upgrading Windows 2000 DNS servers to Windows 2003, the DNS address points to 127.0.0.1. 8. ICS is enable on the DNS server that is not recommended. 9. DNS server A record is missing from the DNS server Suggestion: Running dcdiag and netdiag.exe to troubleshoot these issues. Related Topics
|
|
|
This web is provided "AS IS" with no warranties.
Copyright © 2002-2007
ChicagoTech.net,
All rights reserved. Unauthorized reproduction forbidden.