kytjwrangler
asked on
How Fix Event ID 4004 DNS Error?
I have a Windows Small Business Server 2003 R2 that's generating the following error:
DNS Error Event 4004:
The DNS server was unable to complete directory service enumeration of zone DOMAINNAME.local. [The actual domain name is appearing within the zone.DOMAINNAME.local text]. 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.
How do I eliminate this error?
***Edited by TechSoEasy***
Please also see http:Q_23024027.html for a related error message, but post all comments in this question only.
DNS Error Event 4004:
The DNS server was unable to complete directory service enumeration of zone DOMAINNAME.local. [The actual domain name is appearing within the zone.DOMAINNAME.local text]. 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.
How do I eliminate this error?
***Edited by TechSoEasy***
Please also see http:Q_23024027.html for a related error message, but post all comments in this question only.
Please post a COMPLETE ipconfig /all from your SBS.
Jeff
TechSoEasy
Jeff
TechSoEasy
ChiefIT... thanks for posting here instead... but I should point out that article is for NT 4.0 domains, and really isn't applicable here.
Jeff
TechSoEasy
Jeff
TechSoEasy
ASKER
ChiefIT, the solutions found at your link are for Windows NT 4; this is an SBS 2003 R2 box.
kvtjwrangler,
How about posting the IPCONFIG?
How about posting the IPCONFIG?
ASKER
Here's the ipconfig /all result:
Windows IP Configuration
Host Name . . . . . . . . . . . . : SERVER1
Primary Dns Suffix . . . . . . . : DOMAINNAME.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : DOMAINNAME.local
PPP adapter RAS Server (Dial In) Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.105
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-1A-A0-2B-C8-BD
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.11
Primary WINS Server . . . . . . . : 192.168.0.11
Windows IP Configuration
Host Name . . . . . . . . . . . . : SERVER1
Primary Dns Suffix . . . . . . . : DOMAINNAME.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : DOMAINNAME.local
PPP adapter RAS Server (Dial In) Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.105
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-1A-A0-2B-C8-BD
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.11
Primary WINS Server . . . . . . . : 192.168.0.11
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, the server provides DHCP service.
Yes, the CEICW was run, but not recently.
I don't believe Limewire is installed on this network, but I'll check when I visit the client site Thursday. Thanks for the tip.
Yes, the CEICW was run, but not recently.
I don't believe Limewire is installed on this network, but I'll check when I visit the client site Thursday. Thanks for the tip.
ASKER
Limewire was found on a client workstation. I subsequently removed it.
In a separate post for DNS Event ID 7062 you stated these events were obviously related. That wasn't obvious to me, nor to numerous other IT professionals I consulted.
How do you determine two separate DNS Event IDs are related to the same event?
No word yet on whether the DNS error is recurring following the Limewire removal. Sometimes it would occur every ten days. So, it'll be a few weeks before we determine whether that was the cause.
In a separate post for DNS Event ID 7062 you stated these events were obviously related. That wasn't obvious to me, nor to numerous other IT professionals I consulted.
How do you determine two separate DNS Event IDs are related to the same event?
No word yet on whether the DNS error is recurring following the Limewire removal. Sometimes it would occur every ten days. So, it'll be a few weeks before we determine whether that was the cause.
I had suspected Limewire to be the culprit. Removing it should resolve the problem.
Jeff
TechSoEasy
Jeff
TechSoEasy
ASKER
Thanks for that tip. I appreciate it.
Again, I'm not sure how I was supposed to know the two separate Event IDs were related, but I appreciate your recommendation.
Again, I'm not sure how I was supposed to know the two separate Event IDs were related, but I appreciate your recommendation.
ASKER
DNS issues are notoriously difficult to diagnose. Thank you for the recommendation to check for/remove Limewire.
I'm very sorry to sound like an ignorant jerk, but how on earth would Limewire cause DNS to get these errors? Especially if ran on a workstation?
Sometimes a DNS error will appear on an AD integrated DNS server upon bootup. If these errors appear upon bootup, it could be caused by DNS loading up before Active Directory. AD integrated DNS needs Active directory. Once Active Directory is started, you will see the errors disappear.
If this is the case, you can ignore the errors because it will not effect your domain.
If you have problems replicating, you may need to register your server's DNS info in that server's DNS and replicate that to other servers. Usually this comes from bringing a new server on line.
I hope this helps