Solved

Servers Crashing

Posted on 2007-11-28
3
181 Views
Last Modified: 2010-04-18
We have three Win 2003 Servers that are domain controllers.  All three installed critical updates from Microsoft last week and this week on rebooting none of them will come up.  Multiple services fail to start and when we open Network Properties there are no Network connections.  Rebooting in Safe Mode will bring them up so they can access the network and others on the network can access them.  In Normal Mode the will not access the network and nothing can access them.  We have tried uninstalling the two updates that installed last week but that didn't help.  We have 2003 servers that are not DCs that are working fine.  We have 2000 servers that are DCs and they are working fine.  So it has to be the 2003 server with DC and critical updates.  Any ideas?
0
Comment
Question by:TechNuts
  • 2
3 Comments
 
LVL 29

Expert Comment

by:becraig
ID: 20367552
why not restore the servers to their system state prior to the critical updates there may be driver issues with the nic's installed and the critical updates put out by microsoft.  Did you test these update before approval for installation (Do you have a staging environment for updates ? this would be well suggested so as to minimize downtime) I would suggest replicating the machines in a virtual environment and in the future applying updates to the virtual servers before distributing for install.

You can do a p2v of the machine and operate it in a vmware environment to better troubleshoot the issue (Acronis true image is a good tool for this)
0
 

Author Comment

by:TechNuts
ID: 20374686
I have an update to this problem.
It isn't the critical updates causing the problem.  I think the problem may be our Active Directory.  Any 2003 server that I bring up, doesn't matter about hardware, service packs, updates, etc.  I make it a DC, reboot and everything is working fine.  I wait about a half hour and reboot again and the server will not come up.  My 2000 DCs seem to be doing fine.  I am testing one of those now.
0
 
LVL 29

Accepted Solution

by:
becraig earned 500 total points
ID: 20377890
keep me posted  you might want to check your GPO's as well as your schema infrastructure since the time period you mention sounds like the time it takes for a policy update to run there may be something "wonky" in your AD set up indeed isolate it on a server by server basis if you can afford to
taking boxes off the network until you can identify where the error might be
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
I've always wanted to allow a user to have a printer no matter where they login. The steps below will show you how to achieve just that. In this Article I'll show how to deploy printers automatically with group policy and then using security fil…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

831 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question