• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win2003 Terminal Server... Wicked slow downs

K

Kenazo

Lifer
We have a Terminal Server 2003 based system. Maybe 20 users on a 2xXeon 2.4ghz, 4 gigs ram, some RAID 5 scsi setup etc... all in all a pretty decent system...

Any ideas what migh cause extreme slowdowns? There are times when the system bogs down so bad that it is unusable. Users can't even log themselves off. If I log into the system directly it is even unusable (so it's not a network issue). It seems to almost alwas start around 4, though not every day... There's no scheduled virus scan at that time, no backup is running, nothing besides normal user use.... Go to task manager and the CPU usage looks normal (around 25% CPU usage average).

Is it possible to get some sort of spyware/malware that's running beneath the O/S? I've looked at all the services running and all are traceable to programs we run. I'm at a bit of a loss here.

Other system info:

Windows 2003 Term Server (no sp1 yet)
Office XP
Outlook 2003 connecting to a seperate exchange 2003 server
Mcaffe 8.0.0 enterprise running engine 4400
no scheduled scan for around that time... Onaccess scan is set to scan on write only.


 
I remember once I had a similar problem with a program, it was a memory leak. The memory would get full after 5 hours of usage that day, and then windows would just restart the service and then it again restarted to work well. The slowdown was when the memory + page file were full.
 
Originally posted by: Missing Ghost
I remember once I had a similar problem with a program, it was a memory leak. The memory would get full after 5 hours of usage that day, and then windows would just restart the service and then it again restarted to work well. The slowdown was when the memory + page file were full.
Click to expand...

Let's say this is the problem, how would you determine which program or service was causing the issue?


ivwshane, there's not enough other network traffic that could be causing the problem. The termserv needs very little bandwidth to interact with the terminals anyway.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top