• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1969
  • Last Modified:

Netdiag error...all passed except DC List Test

I have 1 domain controller running AD, DNS, WINS. I am adding another server to run exchange. In the DNS Event viewer, i am getting Error code 4004 and 40015

Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      4004
Date:            10/20/2007
Time:            4:53:35 PM
User:            N/A
Computer:      AFSCME57SVR1
Description:
The DNS server was unable to complete directory service enumeration of zone AFSCME57.  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 extended error debug information (which may be empty) is "". The event data contains the error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00               *#..    

Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      4015
Date:            10/20/2007
Time:            4:53:35 PM
User:            N/A
Computer:      AFSCME57SVR1
Description:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 51 00 00 00               Q...    

I ran Netdiag.exe and everything passes except DC List Test. I am at a loss right now. Any help would be appreciated.
0
neves7
Asked:
neves7
1 Solution
 
Mansoor NathaniCommented:
Try opening DNS manager and checking if the zones load ok. The onces with msdcs for Active Directory SRV records.

Make sure your DNS client service is running, if not start the DNS client service.

Quick search showed up some possible 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
0
 
neves7Author Commented:
Thanks, i think that the DNS was loading before the AD or the 4004 and 4015 error. But the netdiag.exe still shows the DC List Test - still shows failed to enumerate the dcs by using browser [error no browser servers found]
0
 
ChiefITCommented:
Errors 4015 and 4004 can usually be ignored.

It means DNS was started before AD service. They will go away if this was upon loadup. I just helped someone with these errors.

http://www.experts-exchange.com/Networking/Protocols/DNS/Q_22901131.html

If the problem goes unresolved, you may wish to look in your reverse lookup zone.

http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_21213433.html
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now