Answer for:

windows server 2003 remote desktop

Message 17 of 16

View entire thread
0 Votes

Have you logged in from the console and examined CPU and running tasks? Any new software, or changes recently ? I'd look at getting it off the network entirely for the same amount of time it would take to have issues normally, then access it from a laptop and a crossover cable. Like Rob mentioned above, you can at least isolate the problem. A good scan might turn up some goodies too! Anyone leaving term sessions up and running? This can chew up CPU. Also, when you boot the server, do you see any errors reported in post like CPU or memory? Maybe a fan failure?