Re: Terminal Server 2000 pausing

From: Guy Leech (_at_))
Date: 08/26/04 

Date: Thu, 26 Aug 2004 09:35:14 +0100

Is the server itself pausing or is it actually the network side of things?
Have you run perfmon gathering everything over a period and then analysing
the data/looking for patterns? This should also tell you if memory is
actually a bottle neck (look at the memory and paging statistics) - I don't
believe in throwing more hardware resource at an issue without doing
analysis/justification first even if memory is dirt cheap these days.
I'd also bang a kernel debugger on there and interrupt it when it froze to
see where it was at.
Even just putting SysInternal's great dbgview on there to see if there are
any relevant/worrying debug messages coming out might give you something.
Obviously check all drivers, firmware, HP/Compaq Support Pack, etc, etc are
up to date.
I've also seen disk fragmentation kill performance very badly so get all
those pesky users off and do some cleanup (profiles, temp files, etc) and
defrag the thing a few times. Probably wouldn't hurt to do a surface scan of
the disks too.
I guess you've looked in the event log ....

I had a similar problem last year, got hold of the afore mentioned MS patch
and it made no difference - turned out to be a firewall throughput issue.

Regards,

Guy

"Patrick Rouse [MVP]" <PatrickRouseMVP@discussions.microsoft.com> wrote in
message news:55E4292A-FB51-4C0F-8C70-79714D6C13EA@microsoft.com...
> Check this:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;324446
>
> You caould also suspect improperly installed Office 2000 install or faulty
> drivers/BIOS for the SCSI Drives, RAID Controller, Motherboard, NIC...
>
> You absolutely MUST add more RAM (4GB total is good) to this machine, if
you
> plan on running these kind of apps with more than 25 or so concurrent
users,
> as only 1/2 of the installed RAM is available to user processes.
>
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.workthin.com
>
>
>
> "Ed Talbot" wrote:
>
> > It doesn't seem to matter how many are on. For example, right now there
are
> > only 10 concurrent "office" users logged on, and yet the system still
> > hesitates just as much. They are running the SAP GUI client, Solumina,
> > Office 2000 (mostly Excel and Outlook). I have a few users using
Autocad LT
> > 2000.
> >
> > I've had approx. 75 "users" for about a year now. They are generic id's
for
> > shop floor operators to walk up and clock time and view pdf files in an
IE
> > browser window. Along with those I've had about 15 "office" users
during
> > that time. No issues with hesitation all of that time. Only since I
started
> > with the large number of "office" users last weekend.
> >
> > Server specs are HP DL380 G3 2 GB RAM, 2 x 2.8 GHz processors, hard
drives
> > are 10K RPM drives.
> >
> > Ed
> >
> >
> > "Cláudio Rodrigues" wrote:
> >
> > > How many concurrent users do you have now?
> > > What are the specs of your server?
> > > Which apps are the users running?
> > >
> > > --
> > > Cláudio Rodrigues
> > >
> > > Microsoft MVP
> > > Windows Technologies - Terminal Services
> > > http://www.terminal-services.net
> > > "Ed Talbot" <EdTalbot@discussions.microsoft.com> wrote in message
> > > news:83D727CC-3704-4BB0-BEE0-72474F4EA2EF@microsoft.com...
> > > > I'm having an issue with my terminal server pausing. I've recently
added
> > > > about 50 users to my system (was running about 75 before). These
are
> > > > pretty
> > > > heavy duty users. Since then the system will pause periodically for
10-15
> > > > seconds and then continue. No users are disconnected during this
time.
> > > > Any
> > > > ideas?
> > > > --
> > > > Ed Talbot
> > >
> > >
> > >

Relevant Pages