Comments on: Microsoft releases Terminal Services Client 6.0 for Windows XP and Windows Server 2003

by: Szikra Istvan

Tue, 11 Mar 2008 09:19:58 +0000

Do any or all of you have ATI video card and a little ati icon on the tray?
Disable it!
Display Properties > Settings > Advanced > Options > “Show ATI icon on taskbar”
Solved the problem here.
I had similar problems back in the day with Terminal Services Client, ATI tray icon caused some freaky keyboard problems. After a month troubleshooting i found the solution. It seems to work in this case too.
Hope it helps.

by: Greg_PL

Wed, 24 Oct 2007 10:25:33 +0000

have one quesion. What is effective response time for RDP in mseconds? Iam trying to find the perfect bandwidth for RDP

by: Moni

Fri, 27 Jul 2007 04:49:51 +0000

Regarding Generation of Terminal service gateway(TSGU) traffice over netmon :

Hi, i have a setup where-in i need to connect to remotely from a client(longhorn)to a target server(longhorn)through a Gateway server(longhorn).

I am able to connect using mstsc,but i am not gettng the TSGU packets over netmon 3.1.Can anyone help in this regard?

by: Bryan

Wed, 06 Jun 2007 13:13:22 +0000

exact same issue but found that if I hit the L key a fair few times, then locked the TS session then hit windows+L (and locked my local machine) and then ctrl+alt+del and unlocked my machine it all seemed to go away..!

No doubt it’ll surface again some other time though…

Bry

by: Kim

Fri, 13 Apr 2007 16:03:36 +0000

Just to pitch, I experience the same problem and I just want to add to the discussion, that rebooting a remote server is not an option in any live environments. I sincerely hope Microsoft resolves this issue and deploys a new release of Remote Desktop.

On a side note to Remote Desktop.
It should be able to handle two concurrent connections and one /console connection.
Its our experience that this does not work well. We keep bouncing each other off if a user tries to connect to a server that already has a user connected.
Have you guys experienced the same problem?

by: Andy

Fri, 12 Jan 2007 12:46:50 +0000

Matt,

We have the same problem. Since we have installed the MSTSC 6.0 some Windows 2003 servers are working like the windows key is pressed instantly. But there is no windows-key on the keyboard. I’ve found no way to disable that “feature”. Disconnect or Logoff are no work-arounds. A server-restart solves the problem

The windows-key-tapping-action is not working. I’ve installed Windows XP Professional + SP2

by: Joel Wasinger

Mon, 18 Dec 2006 21:50:02 +0000

Matt,

I’ve encountered the same problem (the system thinks the Windows key is pressed). There’s no problem outside of RDP. Good to see that there is at least a temporary work-around.

by: Matt

Fri, 08 Dec 2006 18:21:30 +0000

Ever since going to the 6.0 RDP client, I’ve had issues with windows thinking the Windows key on my keyboard is being pressed, even though it’s not. I hit L, the terminal locks, I hit E, I get explorer, I hit U and I get accessibility controls. Anybody else got this? I’ve had it, and one of my fellow admins has also experienced the same on his desktop. Keys are DEFINITELY not stuck.

Fix is to tap the windows key a few times, then it goes away for a while.

by: Mark

Tue, 05 Dec 2006 03:23:45 +0000

Be aware that on Windows XP SP2 machines Alt+Tab may not switch windows on the remote machine even when you set the option for it. As I frequently use Alt+Tab to switch between programs I have been forced to revert to a previous version of Terminal Services Client. The bug has not been fixed as of 5/12/2006.