Server Stops Responding

[steelcoyot]

I have an interesting issue, my Windows 2003 server stops responding about the same time every day which requires a hard boot. I've disabled all client virus scanning of network drives, broke the HP Teaming, and verify that the system is up to date. Has anyone run into this problem? If so what did you do to resolve it?

Thanks

 

[porkchopexpress]

Do you have any scheduled tasks that run about that time?





When you are the IT director, it's your job to make sure the IT works. If it does work they know already and if it doesn't, they don't want to hear your pathetic excuses.

 

[steelcoyot]

This is a new file server that has Shadow coping running at 7am, and Norton Antivirus Client. I've seen reports about Terminal Services causing an issue of the server not responding but that is disabled and we were using remote desktop access.

 

[porkchopexpress]

RDP uses the terminal service. Do you see any errors in the event log?

Does the server stop at the time the shadow copy runs?






When you are the IT director, it's your job to make sure the IT works. If it does work they know already and if it doesn't, they don't want to hear your pathetic excuses.

 

[steelcoyot]

The server stops at or around 2:30 every afternoon, there are no errors and monitoring the Task Manager shows that the server is barely being utilized. In all since and purposes the server should not be over loaded. It's a quad processors with 4 gigs of ram.

 

[kbing]

Have you performed hardware diagnostics to be sure that all hardware and disk components are running without faults?

 

[steelcoyot]

Yes I have, I've also set up SMNP Traps to monitor the server from an outside source. I've even gone as far as physically sit infront of the machine when it happens. Usually we loose the connections to the shared drives then the server becomes unresponsive with in 5 minutes of that.

 

[kbing]

Do you have any 3rd party software installed on the system? Is it running when this occurs? If so, shut is down to see if it reoccurs. If it still does, then turn off any other non-standard services to see if it re-occurs. Do this one-at-a-time so you know which one it is.

Is the system running the latest service packs? Updates?

 

[cmeagan656]

When this happens are any of the LEDs on your system board lit?

We had a similar problem with a new HP Proliant ML350 G4 running terminal services. In our case the the server was dropping its network connection at random times. As in your case there were no entries in the event logs.

Because the network connection was dropped you couldn't log on to the domain from the console and logging on locally took forever because the server couldn's see the DNS server.

The NIC LED on the front of the server and the light where the cable plugged into the server both showed network connectivity. However, the LEDs on the mobo indicated a problem with the onboard NIC. Two mobos later the issue was still not resolved. Since the server was under warranty HP provided us with an external NIC and we haven't had any problems since (over 17 months now).

HP couldn't provide an answer as to why the connection was dropping but tried to suggest it could be because of our software configuration. We're an accounting office and use a LOT of third party software.

Cheers.