http://blog.tmcnet.com/blog/tom-keat...lem-solved.asp

In the above-mentioned article, Tom Keating describes how he has found the
issue in Windows Vista which causes Remote Desktop Connection (RDC) to either
fail to connect, or operate extremely slow.

In my experiences, I was trying to connect to Windows 2003 Server and
Windows XP based systems from my Windows Vista (Home Premium) operating
system using RDC. Each time I would try, the connection would stop
completely after opening the window and drawing a small portion of my remote
system's desktop.

After searching the internet for over an hour, I found Mr. Keating's article
and executed the following instructions:

1) Open Command Prompt (START - PROGRAMS - ACCESSORIES - COMMAND PROMPT) as
an Administrator by right-clicking on Command Prompt.

2) Type: netsh interface tcp set global autotuninglevel=disabled

This command disables TCP Auto Tuning which is the cause of this particular
problem. To re-enable it, execute the following:

1) Open Command Prompt (START - PROGRAMS - ACCESSORIES - COMMAND PROMPT) as
an Administrator by right-clicking on Command Prompt.

2) Type: netsh interface tcp set global autotuninglevel=normal

If you're technically savvy, there's much more to this issue (fine tuning
the problem, etc), so I recommend reading this article in Mr. Keating's blog.
But for the layman, this quick fix will solve the problem of not being able
to connect to Vista Operating Systems.

And to Microsoft - recognize this problem and PUT A SOLUTION IN THE
KNOWLEDGEBASE!

Enjoy and good luck!

And to Microsoft - recognize this problem and PUT A SOLUTION IN THE
KNOWLEDGEBASE!


A quick search of Microsoft turned up these articles.


http://support.microsoft.com/kb/934430

http://www.microsoft.com/technet/tec...y/default.aspx

http://blogs.msdn.com/wndp/archive/2...-on-vista.aspx

--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca

p0wertech;390696 Wrote:
'Remote Desktop slow problem solved'
(http://blog.tmcnet.com/blog/tom-keat...lem-solved.asp)

In the above-mentioned article, Tom Keating describes how he has found
the
issue in Windows Vista which causes Remote Desktop Connection (RDC) to
either
fail to connect, or operate extremely slow.

In my experiences, I was trying to connect to Windows 2003 Server and
Windows XP based systems from my Windows Vista (Home Premium)
operating
system using RDC. Each time I would try, the connection would stop
completely after opening the window and drawing a small portion of my
remote
system's desktop.

After searching the internet for over an hour, I found Mr. Keating's
article
and executed the following instructions:

1) Open Command Prompt (START - PROGRAMS - ACCESSORIES - COMMAND
PROMPT) as
an Administrator by right-clicking on Command Prompt.

2) Type: netsh interface tcp set global autotuninglevel=disabled

This command disables TCP Auto Tuning which is the cause of this
particular
problem. To re-enable it, execute the following:

1) Open Command Prompt (START - PROGRAMS - ACCESSORIES - COMMAND
PROMPT) as
an Administrator by right-clicking on Command Prompt.

2) Type: netsh interface tcp set global autotuninglevel=normal

If you're technically savvy, there's much more to this issue (fine
tuning
the problem, etc), so I recommend reading this article in Mr. Keating's
blog.
But for the layman, this quick fix will solve the problem of not being
able
to connect to Vista Operating Systems.

And to Microsoft - recognize this problem and PUT A SOLUTION IN THE
KNOWLEDGEBASE!

Enjoy and good luck!
when i try to disable the autotuninglevel, it said:
set global command failed on IPv4 The requested operation requires
elevation.

i am running as administator.

anyone knows how to solve this problem? i read microsoft's article. i
am using Cisco 800 series router (supplied by my cable provider). my RDP
session has this problem: when i RDP to my office pc from home,
everything is fine; however, when my remote RDP is on (from home) and i
come back to office and log into my pc, i get the problem you guys
mentioned. The pc only shows small portion of screen. It takes 10
minutes to return the normal state.

I use Vista Ultimate. 32bits Dell PC.

thanks,
Dan


--
duanyang

Logon administrator is not good enough. You need to run elevation command
prompt. This link may help.

netsh commandSet command failed requested operation requires elevation.
Netsh is a command-line scripting utility that allows you to, either locally
or remotely, ...
www.chicagotech.net/netsh.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"duanyang" wrote in message
...

p0wertech;390696 Wrote:
'Remote Desktop slow problem solved'
(http://blog.tmcnet.com/blog/tom-keat...lem-solved.asp)

In the above-mentioned article, Tom Keating describes how he has found
the
issue in Windows Vista which causes Remote Desktop Connection (RDC) to
either
fail to connect, or operate extremely slow.

In my experiences, I was trying to connect to Windows 2003 Server and
Windows XP based systems from my Windows Vista (Home Premium)
operating
system using RDC. Each time I would try, the connection would stop
completely after opening the window and drawing a small portion of my
remote
system's desktop.

After searching the internet for over an hour, I found Mr. Keating's
article
and executed the following instructions:

1) Open Command Prompt (START - PROGRAMS - ACCESSORIES - COMMAND
PROMPT) as
an Administrator by right-clicking on Command Prompt.

2) Type: netsh interface tcp set global autotuninglevel=disabled

This command disables TCP Auto Tuning which is the cause of this
particular
problem. To re-enable it, execute the following:

1) Open Command Prompt (START - PROGRAMS - ACCESSORIES - COMMAND
PROMPT) as
an Administrator by right-clicking on Command Prompt.

2) Type: netsh interface tcp set global autotuninglevel=normal

If you're technically savvy, there's much more to this issue (fine
tuning
the problem, etc), so I recommend reading this article in Mr. Keating's
blog.
But for the layman, this quick fix will solve the problem of not being
able
to connect to Vista Operating Systems.

And to Microsoft - recognize this problem and PUT A SOLUTION IN THE
KNOWLEDGEBASE!

Enjoy and good luck!
when i try to disable the autotuninglevel, it said:
set global command failed on IPv4 The requested operation requires
elevation.

i am running as administator.

anyone knows how to solve this problem? i read microsoft's article. i
am using Cisco 800 series router (supplied by my cable provider). my RDP
session has this problem: when i RDP to my office pc from home,
everything is fine; however, when my remote RDP is on (from home) and i
come back to office and log into my pc, i get the problem you guys
mentioned. The pc only shows small portion of screen. It takes 10
minutes to return the normal state.

I use Vista Ultimate. 32bits Dell PC.

thanks,
Dan


--
duanyang

Hi,

I am similar slowness with RDP. Unfortunately even after implementing
below changes, it is still very slow.

I am trying to connect from home m/c(vista) to windows terminal server
work m/c (windows xp).

Any other ideas?

Thanks


p0wertech;390696 Wrote:
'Remote Desktop slow problem solved'
(http://blog.tmcnet.com/blog/tom-keat...lem-solved.asp)

In the above-mentioned article, Tom Keating describes how he has found
the
issue in Windows Vista which causes Remote Desktop Connection (RDC) to
either
fail to connect, or operate extremely slow.

In my experiences, I was trying to connect to Windows 2003 Server and
Windows XP based systems from my Windows Vista (Home Premium)
operating
system using RDC. Each time I would try, the connection would stop
completely after opening the window and drawing a small portion of my
remote
system's desktop.

After searching the internet for over an hour, I found Mr. Keating's
article
and executed the following instructions:

1) Open Command Prompt (START - PROGRAMS - ACCESSORIES - COMMAND
PROMPT) as
an Administrator by right-clicking on Command Prompt.

2) Type: netsh interface tcp set global autotuninglevel=disabled

This command disables TCP Auto Tuning which is the cause of this
particular
problem. To re-enable it, execute the following:

1) Open Command Prompt (START - PROGRAMS - ACCESSORIES - COMMAND
PROMPT) as
an Administrator by right-clicking on Command Prompt.

2) Type: netsh interface tcp set global autotuninglevel=normal

If you're technically savvy, there's much more to this issue (fine
tuning
the problem, etc), so I recommend reading this article in Mr. Keating's
blog.
But for the layman, this quick fix will solve the problem of not being
able
to connect to Vista Operating Systems.

And to Microsoft - recognize this problem and PUT A SOLUTION IN THE
KNOWLEDGEBASE!

Enjoy and good luck!


--
esk

are you issueing this command on the machine you are using to connect
too or the one you want to connect too?
thanks


--
dww
Posted via http://www.vistaheads.com