Windows 2003 R2 extremely slow responses
Hi, This is the 3rd Windows 2003 R2 server to do this in the last 3 months. The other 2 we just upgraded to 2008 but that's not an option here. Server boots normally, when you log in at the console it takes 5 solid minutes to bring up the desktop. Then trying to anything is futile. Opening Windows Explorer take 5 minutes. Opening a command prompt the same. The processes look fine, nothing is spiking in CPU or Memory. The hardware is fine, no errors in Device Manager. This has happened on 2 Dells and now an HP Blade so I don't think it's hardware related. Ther are n't any errors worth mentioning in Event Viewer either. I'm at a loss to try and fix this. Does anybody or has anybody had a similair situation? Network shares and file access are fine though those shares. Thanks
June 22nd, 2011 12:43pm

Hi, Is this a fresh install? What services are running on it? What is the type of RAID? Check if it has enogh RAM to handle the job. If yes check possible disk failure, I ve seen this alot of a failing disk is attached (even a USB one). Let me know how it goes. AleksandarMCITP
Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2011 1:02pm

Hi, no this server has been in production for 3 years. All it runs is Terminal Services with a couple of local apps. Plenty of RAM and disk. This happened right out of the blue.. just like it did on 2 other servers (Windows 2003R2 storage servers). There's no rhyme or reason for it. Right now I'm selectively uninstalling things in Safe Mode and rebooting to see if I can find a corrupt program or service.
June 22nd, 2011 2:32pm

Hello, are this machines domain member and do you use only the domain DNS servers on the NIC?Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
June 23rd, 2011 3:01am

I would definetly run hard drive benchmarking software on the drives before concluding that its not an issue. I have seen that behavior many times and it usually points to hdd when it happens right out of the blue. ThanksMCITP
June 23rd, 2011 2:25pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics