I hope this is the right Exchange to ask this:
On Saturday, our client’s dedicated Windows 2003 Web Server suddenly shut down and was down for around ten hours while the hosting company restarted the machine several times, then replaced the power supply and finally put the drives into a new server.
Looking through the event logs, it’s obvious that someone/thing was trying to RDC into the server, with no luck, but could that actually take down a server?
I ask because this isn’t the first time this machine has shut down suddenly and with no apparent reason so I thought I’d ask.
I don’t see anything in the logs that looks odd aside from the constant RDC attempts, which get forcibly closed by the server, and you have to be at a certain IP address in order to have access in the first place, so it’s really dumb for them to try.
The server wouldn’t turn back on without swapping out the mobo, processor, RAM, power supplies, and controller (basically everything but the drives)?
I’d say this was a hardware issue, not software.
- How to shut down Windows Server 2003 without using RDP?
- Setting the order in which services are stopped on a system shut-down in windows server 2003
- Is Windows 2003 Firewall appropriate for a web server?
- Windows Server 2003 Terminal server easiest way to view all mapped drives for all users and the drive status
- How do I setup a Windows Web Server 2008 R2 in a 2003 AD?
Leave a comment
- What is the easiest way to upgrade my existing Perl 5.14 to Perl 5.16 on FreeBSD 9 using the ports system?
- Know if mysql has done its job
- Redirect https .com to https .co.uk without a valid SSL cert on .com without DNS change
- Why is it a bad idea to use customer email as from address
- 100% packets dropped on first RX queue on 3/5 raid6 iSCSI NAS devices using intel igb (resolved)