I am encountering a problem with RDC that began when I replaced Windows XP
with Windows Vista. The best way to describe the problem is "stalling".
Whenever I connect to my Vista machine using RDC, the client will
sporadically just pause (or stall) for a while, and then "come back". Each
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 my remote session
window, but I cannot do anything else. It's like the computer at the other
end just freezes for a while and then comes back like nothing had ever
happened. Has anyone else experienced this? Is there a solution? Thanks.

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
wrote:
I am encountering a problem with RDC that began when I replaced Windows XP
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". Each
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 other
end justfreezesfor a while and then comes back like nothing had ever
happened. Has anyone else experienced this? Is there a solution? Thanks.

Ok; I'm guessing this is happening even when your on the same network
because if this is only happening over the internet the word is "Lag"
and anything over the internet is subject to it. First thing I'd try is
lower the Experence Settings on the RDP client, Hard coding the NIC and
the switch port to 100 Full or whatever then are. Might want to run
Perfmon just to check if RAM is maxing out.


--
oxnyx

I see no difference connecting from a Xp or Vista machine.
I believe the problem is in Vista RDC, because if I connect to my work
machine (with XP and Vista in dual boot) when in Vista I just can't work on
it, otherwhise if it's in XP it works just fine.
FYI: I'm connecting to work via Open VPN and have no problem connectng with
other machines (XP or Server 2003) only to my Vista Business machines.

I've tried from 2 machines at home through the same internet connection, 1
in Vista Biz and the other in XP tablet SP2, and there is no difference -
just can't work.

Is it possible that no one but only 3 or 4 people have this problem ??

" wrote:

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
wrote:
I am encountering a problem with RDC that began when I replaced Windows XP
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". Each
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 other
end justfreezesfor a while and then comes back like nothing had ever
happened. Has anyone else experienced this? Is there a solution? Thanks.

Can you try to follow the instructions listed in the article he
http://blog.tmcnet.com/blog/tom-keat...lem-solved.asp,
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,
etc. Thanks.

--
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
at http://www.microsoft.com/info/cpyright.htm"
wrote in message
ups.com...
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
wrote:
I am encountering a problem with RDC that began when I replaced Windows
XP
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".
Each
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
other
end justfreezesfor a while and then comes back like nothing had ever
happened. Has anyone else experienced this? Is there a solution?
Thanks.