[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 328
  • Last Modified:

windows 2003 SBS becomes unresponsive

I'm running a Windows 2003 SBS for a network of about 50 XP SP3 machines.  Every couple of weeks the server becomes unresponsive early in the morning typically on the weekend.   Most recent was around 12:30am , previous was 2 weeks ago @ 5:15am.

Currently, I've got an anti-virus scan setup to run @ 10pm, (AVG anti-virus SBS Edition v8.5 - Quick Scan, full scan is weekly).  NovaNet 10 runs differential backups @ 1AM over the weekend.   I'm running Exhcange 2003 on this box as well.  

When the hang happens, I either see nothing out of the ordinary in the system logs or (as was the case last night) I see a few 2012 or 2013 errors about the SMTP service not being able to connect to the DNS server, although there were no reports of connectivity issues before the hang and my fuze was able to sync w/ Active sync after those errors had occurred and before the server hung.  There were no errors in the system log before the previous hang.

I am relatively new to SBS administration and am a bit lost as to where to go next in terms of debugging or troubleshooting - I ran the SBS Best Practices analyze and it gave me 2 critical : Task Offloading was enabled and TCP Offloading was enabled.

Where should I go next in terms of troubleshooting this problem?  

Thanks,
Patrick
0
Paddy_Boy_Floyd
Asked:
Paddy_Boy_Floyd
  • 2
  • 2
1 Solution
 
freerCommented:
Is this a complete crash - ie. you have to restart the server - or does it come back?

Tim
0
 
Paddy_Boy_FloydAuthor Commented:
It's a complete crash - the machine freezes / wont come back from the screen saver - everything becomes unresponsive - the only thing that works is to hard reset it w/ the switch on the case.
0
 
freerCommented:
If the machine crashes/freezes with no clues in the event log I'd suspect a hardware fault. Finding these intermittent faults is tricky though. Candidates include RAM, power supply, motherboard, maybe hard drive (drive faults usually raise disk errors in the event log though).

Testing the RAM is easy and worth doing. I'd also Google for the exact hardware to see if anyone has had similar problems.

Tim
0
 
Paddy_Boy_FloydAuthor Commented:
Turns out it was a RAM chip that since went completely dead.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now