Hi.
Does anyone have any idea why our DC keeps crashing/locking up, and as a result, slowly bringing everything to a halt?
We've reconfigured our IIS to act as a second DC/DNS to try and help but it hasnt worked..
Ideas?

Any messages in Event Viewer? Anything eating CPU in Task manager?
Theres occasional DNS->AD errors/warnings in the DNS log, but otherwise its fine.
CPU wise, nothing seems to be eating it up.
Tbh, im convinced the DNS on the DC is borked. Anyone know how to rebuild it? Im not 100% familier with rebuilding a DNS. I know how to set one up, (just about.).
Last edited by boomam; 26th June 2008 at 03:33 PM.

Does it also act as a print server, we have issues with rubbish brother printer drivers using up all of the non-paged memory pool on a server at one of my sites. The server slows right down and the services start to fail like you described but there is no error regarding the actual cause logged.
You might try using a scheduled task to restart the print spooler service every 4 hours which reloads the faulty bit of the driver freeing the memory.
Ive wrote a batch with this is:
And set the scheduler to run it every two hours.Code:net stop spooler net stop PCPrintProvider net start spooler net start PCPrintProvider
The PCPrintProvider (papercut) asks for a Y/N answer when i run it manually.
Anyway to get it to do that automatically?

It should stop without asking questions unless there are services that depend on it that must also be killed. You can see which are dependent by stoping the task in the services manager as this will bring up a list.
You need to stop all dependent services before killing the spooler:
Code:net stop PCPrintProvider net stop "TCP/IP printing" (not exact syntax) net stop spooler net start PCPrintProvider net start "TCP/IP printing" net start spooler
Fair enough. Will put those into the script then.
It crashed again this morning..
Update.
First it wouldnt boot, 'no OS'.
Then it'd hang on the 'preparing network connections' part.
If i boot into directory restore mode, then because our IIS was just made a secondary DNS/AD then it functions fine.
Rebuilt the AD using ntdsutil and it appears to be working correctly now.
Touch wood..
Down again..
This time theres no logical reason for it..
There are currently 1 users browsing this thread. (0 members and 1 guests)