Re: Thin Clients vs Win XP / PE

Well lets, for the moment, forget about my one user...and lets discuss this
from a general perspective. Say the KB article is not the issue...but we are
experiencing on all our clients a keyboard lag (buffering) to some degree or
another. What would cause that? Forgot about all the other symptoms and
just think of this from the user perspective that the keyboard input seems
slow, say once or twice an hour and sometimes the slowness is short in
duration (couple of secs) to almost a full minute.

What would your thoughts on that be? The Term Servers themselves are pretty
darn beefy (the slowest one has a quad processor with 8GBs of RAM) so I can't
imagine it is a hardware issue. Switch logs are clean so it doesn't look
like a network issue.

"Josh Rosenberg [MSFT]" wrote:

Only one user has the big problems? And I'm guessing he is always using the
same client machine? You might want to run diagnostics on his machine,
rather than the intermediate switches; any number of things could be causing
him problems, from a bad Ethernet/wireless card, to malware infestation, to
just running so many apps locally that his computer is performance choked.
Connecting a different computer to the same Ethernet cable might help you
rule out a networking problem unique to his machine.

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"Marcus Cotey" <MarcusCotey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5879DFA0-12D3-4C21-B85E-0D2FE3CB8F4F@xxxxxxxxxxxxxxxx
Well all users experience some lag occasionally but for one user it is
particularly painfull. As for what I mean by delay it is pretty much all
of
the above...keystrokes seem to buffer and take a second to display on the
screen, dropped key strokes, cursor sometimes jumps fields and about once
or
twice a day the delay becomes longer than a few seconds (we timed one up
to
45 seconds) and the user becomes completely frustrated.

So far we only have 15 users on our TermServ farm and the intention was to
roll this out to a couple of 100 users but unless we can improve upon the
experience the project may stall out. Thanks for the responses.

PS
I got with out Network Engineering group and we checked the ports on the
switch and their were no errors, no dropped packets and no collisions.
Everything from the switch to the wire to the port was five by five.

"Josh Rosenberg [MSFT]" wrote:

Do you mean that the keyboard responsiveness lags for all users when one
of
the affected clients connects (per the KB article you mentioned), or that
there is a lag for the affected client only?

Can you describe exactly what you mean by "keyboard delay"? Slow
response,
dropped keystrokes, something else?

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"Marcus Cotey" <MarcusCotey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E535A079-0A8E-4479-9397-762F17E23753@xxxxxxxxxxxxxxxx
We have several users using thin clients to connect to Win 2003
Terminal
Services.
We also have several users using WinXP and MSTSC to connect.
We even have a few that use Win PE2.0 and MSTSC to connect to the
TermServ
farm.

The WinXP and the WinPE clients have keyboard delays when connecting.
The
thin clients do not. What would cause this delay?

Before someone suggests this article:
http://support.microsoft.com/kb/324446
I have already read it. We cannot enable those advance features on our
RAID
array (Thanks Dell) and so that is not an option. How would I even
test
for
that anyway? I mean, if that really is the issue I could probably
lobby
to
get the Term Servers on different hardware but until I can prove
unequivocally it won't happen.

Any suggestions would be appreciated. Thank you.

MC



.

Relevant Pages

  • Re: Thin Clients vs Win XP / PE
    ... SDE - Terminal Services ... twice a day the delay becomes longer than a few seconds (we timed one up to ... Everything from the switch to the wire to the port was five by five. ... > We have several users using thin clients to connect to Win 2003> Terminal ...
    (microsoft.public.windows.terminal_services)
  • Linux console keyboard delay trouble
    ... For my current application I need to switch off the keyboard delay. ... the manpage claims this is hardware dependent. ...
    (comp.os.linux.development.apps)
  • Re: Slow response when opening files from Win2K3 Server
    ... however with this installation, there is a 20-30 second delay when opening ... Check if the clients pointing to the correct internal DNS server, ...
    (microsoft.public.windows.server.active_directory)
  • Network hanging - event id 1058, 1000 client side
    ... newly installed network cabling, new hardware, 3com 16 port ... a few clients get hung up when ... but that seems hard to fix without being able to replace the switch. ... Visit Topic URL to contact author (reg. ...
    (microsoft.public.win2000.general)
  • SUMMARY: Sol8 / netraX1 / packet loss
    ... network autonegotiation between the netras and the cisco switch. ... The netras decided they had 100MHz full duplex, the switch decided 10MHz ... > All the clients were installed using jumpstart and a common OS image. ...
    (SunManagers)