DNS error 4000,9999 (1 ,2 days after restart)

[kokaina]

HI,
I have 2 DC, connected trough VPN.
From a while I have a strange issue with 1 DC, DNS is stop working and I have DNS log, full with ID 4000, 9999.
After I restart the server, everything is OK for 1 or 2 days, and then DNS problems are starting again.
Could be a problem of insufficient resources?
The server is IBM 2x Xeon 3,7 GHZ, 3 GB RAM, RAID-1 SAS 143 GB and running MS SQL.
If I run dcdiag , the following error appear :
LDAP search failed with error 58,
The specified server cannot perform the requested operation..
***Error: The machine, server_name could not be contacted, because of a bad
net response. Check to make sure that this machine is a Domain Controller.
I run a Perf MOn, but I don't see something strange:
Available MB: average 158MB
PAge /sec: 14
disk time : 15
disk queue length : 0.150

Some ideas?

 

[technome]

Start looking for a memory leak, very common to have DNS affected once memory resources are consummed by a buggy program or service.

........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[ITPangaeaArchitect]

So #1, SQL needs to go. A DC should be only a DC and nothing else (give or take the occasional ADMT server)...

If you go to the properties of the DNS server on the monitoring tab, enable all logging (errors and warnings)..that should give more information.

the 9999 events are just the standard "numerous run time errors have been encountered" error correct?

check this for event 4000:

http://support.microsoft.com/kb/316685

What OS and service pack are you running?

-Brandon Wilson
MCSE00/03, MCSA:Messaging00, MCSA03, A+
Manager - Global AD Operations
ACS, Inc.

 

[kokaina]

HI,
I don't have for the moment another choice, so SQL must run on DC.
I already check for that KB on MS site, but that was not a solution.
Yes, the 9999 event is there in DNS event viewer.
I will try to log all DNS events.

 

[ITPangaeaArchitect]

Ok so CrashOnAuditFail is NOT enabled then correct? Thats all I wanted you to make sure of with the article

You may try hotfix 909249 IF you are running windows 2003 SP1...that hotfix ONLY applies to 2003 SP1...but it may fix your issue if you are at that OS/SP level.

As far as SQL on the DC...be advised it can, and likely will, lead to various resource type issues on your DC, as SQL will try to take priority...this leaves your DC in a very precarious state.

-Brandon Wilson
MCSE00/03, MCSA:Messaging00, MCSA03, A+
Manager - Global AD Operations
ACS, Inc.

 

[kokaina]

I forgot to tell you, the server is W2k3 SP2.
So that hot fix, is not apply to this version.
I try also, couple days ago, the /3GB switch, but that was worse than now. When the switch was activated I need to restart the server 1 or 2 times/day. Sometimes I can't log in , I receive some error about " cannot loading profile...".
So I remove the /3GB switch.
I don't know for the moment what else to try.