Can you try to follow the instructions listed in the article here:
specifically, these instructions from that article may help:
Here is what you need to do if you have the same issue:
- Run a command prompt (cmd.exe) as an Administrator
- Type: netsh interface tcp set global autotuninglevel=disabled
If you want to to re-enable it:
- Type: netsh interface tcp set global autotuninglevel=normal
In some cases you may need to use this command in addition to the above,
but I didn't have to:
- Type: netsh interface tcp set global rss=disabled
Please write back to let us know if it works or not.
If this works, can you please send me an offline email at "sfeng at
microsoft dot com" as we are
interested in knowing more detail about this issue, like the configuration,
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples (if any) are subject to the terms specified
<email@example.com> wrote in message
>I have the exact same problem on multiple machines. It seems to
> mostly happen when connecting to a Vista machine from a Vista
> machine. When connecting to a Vista machine from an XP machine, it
> seems to work better. FYI, the XP machine is using RDP 6 as well.
> On Mar 5, 7:31 pm, VistaRDC_Sucks
> <VistaRDCSu...@discussions.microsoft.com> wrote:
>> I am encountering a problem with RDC that began when I replaced Windows
>> with WindowsVista. The best way to describe the problem is "stalling".
>> Whenever I connect to myVistamachine using RDC, the client will
>> sporadically just pause (or stall) for a while, and then "come back".
>> time the delay varies anywhere from a few seconds to up to a minute.
>> When it
>> is stalled like this, the mouse works and I can minimize myremotesession
>> window, but I cannot do anything else. It's like the computer at the
>> end justfreezesfor a while and then comes back like nothing had ever
>> happened. Has anyone else experienced this? Is there a solution?