Win34 being super slow -rebooted and still

We are checking Win34, it is just crawling slow, we thought it was the brute force scans initially but that passed and win34 remained slow. We tried a reboot and now it is still very slow even to login to it on the local machines.

We are researching it now to find and solve the issue and will report back.

The issue is now resolved, after rebooting it a few times and seeing how it was hanging I felt it had to be some issue in the hard drives RAID array. I opened the top of the case and felt the temps on the drives and sure enough one was much hotter than the other. I turned the server off and booted up with the hot one unplugged, that resulted in the same super slowness, so I plugged in the hot one and unplugged the other, and all is working properly now. The RAID is currently degraded and we will plan a maintenance on this server within 24-36 hours to resolve the degraded raid.

Seems like we are having a occurrence of this slowness issue now and checking it out.

One of the base services is not stating so it is not allowing IIs to start, we are checking into this now, starting by doing a filesystem check.

Server has been up for about 15 minutes now. We didn't see anything actually found or corrected in any of the scans but it came up and working properly now where before services would not completely start just hang.

This is a pre R2 Windows 2008 Server and we are now going to prep a 2008 R2 server to move it across to this will help uprade to the latest MVC and ASP.NET 4.5 as well, so it will benefit all around with less trouble in the shift than 2003 server.