Two Windows Server 2003 Domain Controllers hang every day

Hello,

We have two domain controllers running Windows Server 2003 that freeze up every day, and have to be powered off completely to bring them back up.  Sometimes one of them freezes multiple times.  We have been checking the event logs for clues, but haven't found anything helpful.  We thought that the time service was the cause, and have set that to NoSync in the registry for now on one of the servers.  We are currently in the middle of migrating from Novell to windows, so we have some buildings running Novell and Windows parallel.  I'm not quite sure what other info you may need to better assist us with this.

Thanks,
Miket71
miket71Asked:
Who is Participating?
 
trippleO7Commented:
This is going to be a tough one to troubleshoot...Do the servers have sufficient cooling so they aren't overheating?  Are there any patterns of when they lock up, certain time of day maybe?   Are there known electrical problems in your area?  Protected by UPS or other battery backup?  If so, is it overloaded?

Something to start with...
0
 
miket71Author Commented:
I think we can rule out any harware related issues because both DCs are going down together and they are in different physical locations (100 miles apart).
0
 
miket71Author Commented:
I looked in the event log this morning, even though I discovered that the two servers did not freeze up this morning for the first time in the last 5 days or so, I noticed these events (1053 and 1054 respectively) in the Event Viewer Application Log for both servers:

Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1053
Date:            10/20/2006
Time:            1:52:00 PM
User:            NT AUTHORITY\SYSTEM
Computer:      SKLDC
Description:
Windows cannot determine the user or computer name. (The specified component could not be found in the configuration information. ). Group Policy processing aborted.

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


Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1054
Date:            10/20/2006
Time:            1:40:19 PM
User:            NT AUTHORITY\SYSTEM
Computer:      SKLDC
Description:
Windows cannot obtain the domain controller name for your computer network. (The specified component could not be found in the configuration information. ). Group Policy processing aborted.

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

Thanks,
Mike
0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

 
miket71Author Commented:
The two events that I just added above for both servers would continuously post themselves quite a few times which was determined to be the the entire time that the servers would be froze.  One server would usually start the problem during the evening hours, and continue posting the specific events as posted above during the nighttime hours until someone would reset the server in the morning.  The other server would start acting up anytime day or night.
0
 
miket71Author Commented:
I have found that the two servers that are freezing are currently using the generic microsoft driver for the Intel Pro/1000 MT nics in them, so I will apply the newest driver from Intel's site tonight to see if that will at least stop the servers from freezing.  We do have other DCs on the network with Broadcom Nics in them, and they don't freeze at all even though they still get those Application Log errors concerning Group Policy as noted above.  I also noticed that my PC is getting the Group Policy errors.  I'm not sure if fixing the drivers on the two affected DCs will clear up those errors everywhere else.  I'll keep you posted.
0
 
trippleO7Commented:
What did you find out?  Were the Intel drivers the problem?  If so, you can ask a Moderator for point refund.  Please post your solution in case someone else runs into this problem.

Thanks.

0007
0
 
miket71Author Commented:
It appears to have been the NIC drivers for the two servers.  They were originally using the microsoft driver, but we have since upgraded them to the most recent Intel driver.  We will have to wait a few more days to see what happens.  The Application log errors for the Userenv Group Policy errors have also cleared up.  We'll keep you posted if anything changes.
0
 
trippleO7Commented:
Thanks for the update.  Because I didn't answer your questions, you can ask a moderator to refund points.  Good to see you solved your problem!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.