Server rebooting between 2-4pm every other day.

Posted on 2007-10-11
Last Modified: 2008-05-31
I have a Win2k3 corporate server which resides behind a firewall and is a part of Active Directory.  Its acting as an app server in some ways and a print server in others.  It has standard corporate products installed such as Symantec AV Corporate Edition, with real-time monitoring disabled so as not to interfere with the files the application requires to be opened at the same time - else, the app comes to a grind.  However, since this issue begin we've randomly run scans on the server but the AV client log indicates nothing detrimental in terms of viruses picked up.

Windows Firewall is disabled, all hardware and software firmware patches and updates are current.  We've run Dell OMSA and everything hardware/software related on the server is upto date or shows no errors.

MS-SMS client is enable, and NT backup exec client is installed but backups are set to run nightly.  The Windows Event Log doesn't show anything that stands out (but I'd be more than happy to try various approaches, and supply the Event Log information within the forum if that helps).

The problem I have is that the server reboots itself every other day between 2-4pm.

Any help/thoughts/ideas would be greatly appreciated.
Question by:birdn
    LVL 11

    Accepted Solution

    It's strange the number of Windows 2003 servers that are rebooting randomly these days, we've had numerous brand new servers doing this over the last 12 months.  It has been caused by one case of a dodgy processor, one of HP drivers being out of date and about 8 of the windows storport driver conflicting with the system.

    Is there a UPS to rule out power failure?  The chances are the server is blue screening, it's just not making it into the Event Logs and the server reboots.  Have a look at this article, it's a great guide to getting some info on blue screens -  I've used it a few times now and it's always pointed me to the right thing causing the problem.
    LVL 3

    Assisted Solution

    You first need to determine if the server OS is crashing (blue screen) or if you are having a hardware reset of some sort. Crashing leaves evidence in the System Event Log (Windows rebooted due to a bugcheck), or in the form of a crash dump file (memory.dmp or %systemroot%\minidump). Hardware resets can be caused by malfunctioning hardware or by automatic server restart functionality of some systems which automatically reboots the system when hard lock-up is detected.

    Also, exactly what type of hardware are we talking about here?

    Author Comment

    Sorry for the delay in getting back.  I'll take a look at the article Zenith submitted, thanks very much.

    Here's a snapshot of the hardware profile:

    Dell PE 2850
    Xeon multi-processor (dual core, not single core)
    Total physical memory 4 GB
    Available physical memory 3.39 GB
    C: = 42MB of available free space
    D: = 31GB of available free space
    SCSI drives are PERC 4e/Di RAID Controller

    Is there something specific you'd like submitted?  We're currently working on increasing the HD capacity for the C: drive.

    Thanks for all the help.

    LVL 3

    Expert Comment

    "It has standard corporate products installed such as Symantec AV Corporate Edition, with real-time monitoring disabled"

    why don't you just set not to scan the apps folder rather than disable real-time monitoring function?

    I think your server got virus, try to install a anti-virus software on another server/workstation and then map the infected server drives, and scan it
    LVL 11

    Expert Comment

    Just curious what the problem turned out to be if it's sorted?  Seeing so many of these these days it's good to know all the possible causes!

    Author Comment

    I'm working on gathering more information.  My symptoms are kind of all over the board right now.
    Thanks for the input.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    This is my first article in EE and english is not my mother tongue so any comments you have or any corrections you would like to make, please feel free to speak up :) For those of you working with AD, you already are very familiar with the classi…
    As network administrators; we know how hard it is to track user’s login/logout using security event log (BTW it is harder now in windows 2008 because user name is always “N/A” in the grid), and most of us either get 3rd party tools, or just make our…
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

    759 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

    Need Help in Real-Time?

    Connect with top rated Experts

    13 Experts available now in Live!

    Get 1:1 Help Now