Re: Thin Clients vs Win XP / PE

Usually, I would suspect CPU or network load spikes, particularly when the lag is only a few seconds. For example, if even a few users have IE7 open with Flash enabled, that will *kill* a connection. Blocking Flash via GP or a reg key, or making it opt-in with a third party plug-in would help a great deal. Another example would be playing back movie files, transferring an enormous file via drive redirection, or running "dir /s" from the root of a drive in the command prompt.

While TS makes some effort to balance session resource allocation, it doesn't operate well at full capacity.

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"Marcus Cotey" <MarcusCotey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B3D72E64-1AE9-499A-BFC7-C21E5AEDB777@xxxxxxxxxxxxxxxx
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: IP address assignment problem
    ... I have a little problem and seek for ur thoughts, let's assume I'm in a very open environment where everyone can very easily try to get his/her laptop on the network and IP addresses are assigned by a DHCP server and we are in a domain environment, how do I prevent machines that are not part of our domain to be assigned an IP address? ... This approach doesn't stop your rogue clients from connecting to other clients, but merely doesn't give them the information they normally need to do so. ... Using 802.1x, your workstations authenticate through the switch to a radius server before they are allowed any connectivity. ... This authentication can use X.509 certificates, computer account credentials from AD, or whatever else you'd normally configure radius to authenticate with. ...
    (Focus-Microsoft)
  • RE: Dropped Client Connections
    ... I understand that the SBS clients will lose ... Do all clients lose network connection at same time? ... Do you have single or double NICs on SBS? ... Modify the registry to disable Receive Side Scaling ...
    (microsoft.public.windows.server.sbs)
  • Re: Please help me "sell" the idea of a more secure network
    ... changes first should bring the network up a notch or two. ... Do the same thing using a wireless notebook from you company. ... show him a PO or invoice for a customer who had an AV ... products, releases, life cycles, etc, all on the individual clients. ...
    (microsoft.public.win2000.active_directory)
  • Re: Please help me "sell" the idea of a more secure network
    ... changes first should bring the network up a notch or two. ... Do the same thing using a wireless notebook from you company. ... show him a PO or invoice for a customer who had an AV ... products, releases, life cycles, etc, all on the individual clients. ...
    (microsoft.public.win2000.active_directory)
  • Multiple Consistent Security Event Logs
    ... to capture Audits for both the Clients n the Servers. ... enabled certain other policies relating to secure Network Communication. ... Object Access, Logon/Logoff, Account Logon, Privilege Use with 'User' varying ...
    (microsoft.public.win2000.security)
Loading