Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Robert MacLean — Wed, 29 Nov 2006 08:14:44 GMT

Excellant. More Vista goodness for those stuck on XP.

Your links however point to the Microsoft webmail and not to the actual files.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

jeutix — Wed, 29 Nov 2006 11:34:25 GMT

Hello!

I want so setup a TS Gateway but don't find any help or "How-to"s. Could someone help me, please?

Greetings

Udo

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Tim Tytso — Wed, 29 Nov 2006 16:43:56 GMT

Will any of these new features be available when using the new client to connect to the old version of the RDP server running on XP Pro/Windows 2000?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

termserv — Wed, 29 Nov 2006 19:06:19 GMT

Thanks for the heads-up. The URLs are fixed.

Rob Leitman

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

termserv — Wed, 29 Nov 2006 19:07:48 GMT

Udo:

TS Gateway is part of Longhorn Server. If you have access to the beta, you should be able to find documents on the Microsoft Connect site on how to set up TSG.

Rob Leitman

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick Rouse — Wed, 29 Nov 2006 19:18:15 GMT

http://www.msterminalservices.org/articles/Overview-Longhorn-Servers-Terminal-Service-Gateway-Part1.html

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Joshua Erquiaga — Wed, 29 Nov 2006 21:34:58 GMT

Will Terminal Services Gateway be released for Server 2003, or will it only be available on Longhorn Server?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick Rouse — Wed, 29 Nov 2006 21:57:34 GMT

It's a component of Longhorn Server. You can do the equivalent w/ 2000 or 2003 w/ 3rd party tools, i.e. an of the SSL VPN products listed here:

http://www.sessioncomputing.com/add-on.htm#security

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Roger French — Fri, 01 Dec 2006 14:19:16 GMT

Since updating to Terminal Services Client 6.0, I cannot connect to one of my servers using Remote Desktop from any of my XP SP2 workstations although I can connect from a server running Windows 2003. I get the following message when I access from a workstation even though there are no sessions running on the server.-

The client could not connect. You are already connected to the console of this computer. A new console session cannot be established.

I have two servers running 2003 standard edition SP1, both domain controllers. One I can still access OK, the other I cannot although I can access both servers from each other.

I have proved this to be caused by the update by trying from a workstation before Terminal Services Client was updated and that worked OK but It failed after updating. I have also tried several workstations and different user names but they all fail.

Is this a known problem?

One other point when I can log in the credentials box prompts me with a user name prefixed with the server name rather than the domain name although this still works it is not what I expected. I would prefer the user name to be blank unless I have asked for it to be remembered.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Gaurav Daga — Fri, 01 Dec 2006 23:00:03 GMT

Will any of these new features be available when using the new client to connect to the old version of the RDP server running on XP Pro/Windows 2000?

No - the remote computer must be Windows Vista or Windows Server codename "Longhorn".

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

dennis@7summitsict — Sat, 02 Dec 2006 17:06:24 GMT

Will there be a Single Sign On for not-vista clients? As in the Citrix CSG?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Anders Frederiksen — Sun, 03 Dec 2006 21:25:24 GMT

Installed the new client, and I must say: Smooooth! Really nice work.

But it keeps saying: "Network Level Authentication not supported" in the about window. How can I enable this feature. My Vista machine has it enabled. Am I doing something wrong?

Kind regards

Anders

Copenhagen, Denmark.

Remote Desktop Connection 6.0英語版(マルチモニタ対応)

米田 Blog ( SQL Server MEMO ) — Tue, 05 Dec 2006 15:21:11 GMT

Remote Desktop Connection 6.0英語版(マルチモニタ対応)

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Curtis — Tue, 05 Dec 2006 22:40:13 GMT

great release but... all my TS users are now getting a mstc.exe application error when every they close the app. has this been reported by anyone?

cpetrey@mahoningcountyoh.gov

RDP 6.0 Client BREAKS msrdp.ocx registration

JPlavocos — Wed, 06 Dec 2006 21:41:43 GMT

The msrdp.ocx (3790) was registered and working on all of our machines. We understand that msrdp.ocx is not being updated by RDP 6.0.

However,installing the RDP 6.0 client results in a "Component 'msrdp.ocx' or one of it's dependencies not correctly registered."

As Admin, manually registering the file fixed the problem.

However, we have hundreds clients with user rights that cannot re-register the ocx manually.

Please advise to a possible upcoming fix.

Sincerely,

John Plavocos

john@michaelsutter.com

(435) 654-2800

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

shubs — Wed, 06 Dec 2006 21:43:32 GMT

Installing RDC 6.0 on Windows 2003/XP machines stops printer redirection. Uninstalling it resolves the issue as the version is rolled back. Any known issues with printer redirection?

How do I rollback Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Peter — Wed, 06 Dec 2006 22:20:01 GMT

Authentication via SmartCard no longer works for me - is there a way to uninstall the update?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Thu, 07 Dec 2006 00:46:52 GMT

Shubs, I dont think there are any known issues with printer redirection. After you install RDC 6.0, have you checked if printing redirection is enabled? To do so, click on options, and then click on the "Local Resources" tab, and see of "Printers" is checked. If for some reason, after installation, this checkbox gets unchecked, that would be nice to know :)

-Z

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Gaurav Daga — Thu, 07 Dec 2006 00:51:24 GMT

Peter, can you please describe the scenario? Do you get prompted again for user name and password after you give your smart card credentials? What is the OS you are connecting to?

Thank you

Gaurav

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Gaurav Daga — Thu, 07 Dec 2006 01:03:15 GMT

Anders, the TS client 6.0's "About" section says "Network Level Authentication not supported" because the client computer (either XP or Windows Server 2003) that you are running does not support Network Level Authentication. It does not matter what is the remote computer you are connecting to (e.g. in your case, Vista).

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Gaurav Daga — Thu, 07 Dec 2006 04:41:07 GMT

Hi John

TS Client 6.0 explicitly removes msrdp.ocx registration. The new version of mstscax.dll replaces msrdp.ocx functionality.

Can you please describe the specific problem you are running into?

Thank you

Gaurav

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Gaurav Daga — Thu, 07 Dec 2006 04:42:25 GMT

Hi Curtis

What is the mstsc.exe application error that your users are hitting? Please help with details.

Thank you

Gaurav

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

JPlavocos — Thu, 07 Dec 2006 17:07:32 GMT

Guarav,

Thank for your response. The issue is that our VB6 application which has the msrdp.ocx compiled into it, is crashing with a VB error of "Component 'msrdp.ocx' or one of it's dependencies not correctly registered."

So, we are stuck without being able to reference all the existing deployments of the VB6 app with msrdp.ocx. They are now broken.

John Plavocos

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

AuraDave — Fri, 08 Dec 2006 02:27:02 GMT

HOW do I get rid of that first 'Enter Network Credentials' prompt - the TS prompts me anyways even if I fill in the fields, and click remember me -- and then, it really *doesn't* remember what I typed in. HelP!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick Rouse — Fri, 08 Dec 2006 06:51:28 GMT

Uncheck "Always prompt for password" in the Terminal Services Configuration -> Connections -> RDP-tcp -> Logon Settings

Patrick Rouse

Microsoft MVP - Terminal Server

Citrix Technology Professional

Provision Networks VIP

(949) 433-9422

http://www.sessioncomputing.com

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Anders Frederiksen — Fri, 08 Dec 2006 17:53:52 GMT

Hi Guarav,

Thanks for the reply. So, if I understand you correctly, the problem is with Windows XP itself?

Will a version of Network Level Authentication be available for Windows XP?

Thank you very much for the help.

Rgds.

Anders

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Roger French — Fri, 08 Dec 2006 22:18:09 GMT

As per my message of the 1st. Still getting the error :-

The client could not connect. You are already connected to the console of this computer. A new console session cannot be established.

when trying to connect to one of my servers. I have had to roll TS client back to 5.1 to be able to connect.

Anybody got any ideas?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Teck — Sat, 09 Dec 2006 21:45:20 GMT

HI,

There used to be a workaround in previous version for the error "he client could not connect. You are already connected to the console of this computer. A new console session cannot be established."

By changing in properties of the RDP shortcut > Compatibility tab>Compatibility mode - to Windows 98/ME. But now with version 6, this ability to change compatibility is disabled. Don't know why. So you are stuck.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Nathaniel — Mon, 11 Dec 2006 08:00:40 GMT

Patrick I am having a similar problem. My users are trying to connect to a windows 2000 server that is already configured the way you suggest. Also the RDP connections no longer remember the username or the domain that the user should be using this is a major problem for some users!

Anyone know any work arounds

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick Rouse — Mon, 11 Dec 2006 08:05:12 GMT

You could look at an add-on product w/ Single-Sign On capability, i.e. Provision Management Framework Enterprise, Citrix Presentation Server, Ericom PowerTerm Webconnect or 2X ApplicationServer.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Nathaniel — Mon, 11 Dec 2006 08:17:20 GMT

Until this update RDP worked fine for us. Would really suck if because of an update we had to go to something else. Hopefully stopped the roll out soon enough to minimize the number of users affected.

Smartcard authentication prompts for username and password

Tim B — Mon, 11 Dec 2006 11:37:25 GMT

After upgrading to the TS 6.0 Client on Windows XP-SP2 the smartcard authentication is not working properly anymore.

After I select my Smartcard certificate and enter the PIN for my SafeNet Rainbow 2032 token, the server (Windows 2003SP1 with SSL Security layer and SafeNet Auth solution 4.7 -MU20) prompts me for my username and password again.

The Logon Settings on the server are set to "Use client-provided logon information".

The "Alternative Name" on my cert is correct and with the Windows XP Sp2 TS client I can connect without the username/password prompt.

With the TS 5.2 client from Windows 2003 Sp1 I get the best usuability on Windows XP Sp2, since smartcard logon detects the right cert automatically and SSL security works without any problems.

Is there something I can tweak on the TS 6.0 client to make the smartcard authentication working again?

Thanks for any help in advance.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

curtis — Mon, 11 Dec 2006 19:48:04 GMT

Gaurav,

Thanks for the response on this.

The error message is:

mstc.exe - application error

the instruction at 0x00c8fd50 referenced memory at 0x0000008. the memory could not be read.

all of our users get this when they exit an rdp session.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Gaurav Daga — Tue, 12 Dec 2006 05:55:21 GMT

Tim

Can you please reconfirm that the Smart cards checkbox in mstsc -> Options -> Local Resources -> More... section is checked? If not, please check it and try again.

Thank you

Gaurav

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Roger French — Tue, 12 Dec 2006 22:58:50 GMT

Hi Teck

Thanks for your response. Don't think you could change the compatibility settings on 5.1 but that worked OK without any configuration so don't know why 6.0 doesn't. Looks like I will have to roll back to 5.1 on all my workstations - still there's only 50 to do!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Steve Pilkington — Wed, 13 Dec 2006 14:22:49 GMT

Upgraded to the latest TS client and we are now having problems with Citrix logons. I traced this down to using the new TS client to logon to the Citrix Server consoles. When a qualified user id is entered in the logon dialog (domain or machine name) then the DefaultDomainName entry is changed in the WinLogon key. Users don't notice that the domain name box is now defaulting the the local machine name and so fail to logon.

Had to manually change the WinLogon keys back and NOT pass credentials to the TS client.

Is this working as designed???

Thanks

Steve.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Gerard — Wed, 13 Dec 2006 16:39:21 GMT

I am also receiving the error:"The client cannot connect. You are already connected to the console of this compu........."

I only receive it when trying to connect to the DC, I have two member servers that I can connect to with no problem.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

John Reighard — Wed, 13 Dec 2006 18:14:13 GMT

I updated to TSC 6 on this laptop i am currently on only, every other computer on the network still runs 5.1. When I attempt to connect to any other workstation I get the error "this computer can't connect to the remote computer. try connecting again." if i try to connect via IP. If I try to connect via DNS name says "rdp cannot find remote computer. contact blah blah blah" Is it because the only client that is this laptop and the older versions arent compatible? or am I missing something entirely.

Username/password prompt happens before connecting now.

Reed Arvin — Wed, 13 Dec 2006 19:54:19 GMT

So this version of mstsc wants the username/password first before even connecting to the remote server. Is there anyway to configure it to behave the old way (i.e. connect first, then logon with username/password/domain)?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Richard — Thu, 14 Dec 2006 12:29:15 GMT

Hi,

initial connect is now extremely slow - approx. 10 seconds. Can I speed it up?

Thanks

Richard

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Richard — Thu, 14 Dec 2006 15:24:30 GMT

Hi,

I discovered, that after launcing RDC 6.0, netbios queries start for "LOCALMACHINE <00>".

Disabling netbios helps to dismiss startup delay, but these netbios queries happen only since installing RDC 6.0.

Richard

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick — Fri, 15 Dec 2006 23:45:06 GMT

Put us down for the mstsc.exe - Application Error

The Instruction at "0x00d0fd50" reference memory at "0x00000008". The memory could not be "read".

Click on OK to terminate the program

About 90% of our users get this message anytime they disconnect at Terminal server session - from any server. Graceful Logoff, or just closing the window. Those who get the error - get it every time.

Anyone have a fix for this? Please?

Same old Microsoft, can't let me piss without telling me how...

Scott — Sat, 16 Dec 2006 00:11:34 GMT

How do I stop it from asking for Server Authentication credentials entirely?

We only use this stupid program in our office where there is exactly zero chance that anyone is going to connect to the wrong server, so the added step of entering credentials *before* logging into anything has been very poorly received by our confused staff. Since I'm the one fielding all the calls on this, I am not at all happy that this was enabled by default with no obvious mechanism to disable it.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick Rouse — Sat, 16 Dec 2006 01:00:33 GMT

You can always roll back to the 5.1 or 5.2 versions of mstsc.exe.

Newer means newer, and often different, and almost never pleasing to everyone. I understand you are frustrated, but as an IT Professional it is your responsibility to test new software before deploying it. I've been testing the 6.x RDP Client for some time and it has new features that would make some want to use it, i.e. screen size > 1600x1200, 32 bit color, saved credentials... but I've yet to tell any of my clients to update their computers.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Scott — Sat, 16 Dec 2006 07:32:17 GMT

I don't accept the response 'use the old version'. The problem with that tactic is that it assumes that I can use it forever. It is never possible to simply 'go back' and use an older version, especially where MS is concerned. Having played with the beta, I happen to know for a certainty that the TSC built into Vista has this same anti-feature. Am I to assume that you expect me to use WinXP forever too? Are you telling me I can rely on MS to support WinXP from now to eternity?

How hard can it be for MS to figure out that security means giving control to people who know how to use it, not simply taking control away? I swear, MS is worse than BigBrother.

Does anyone have a *real* answer to my problem?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

hgk — Mon, 18 Dec 2006 09:17:03 GMT

I installed it on a notebook & initially it seemed fine but then there were could not connect...virtual memory.. failures when connecting to XP systems while connection to Win2K systems still worked. How does one regress? It is not listed in Add/Remove programs. Can't see how to uninstall or overinstal...

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

GOM — Mon, 18 Dec 2006 20:08:13 GMT

I also have the failures noted by hgk. I installed this on my XP Pro notebook and I get the error message "Cannot Connect. The Problem might be due to low virtual memory..." If I logon to my notebook as the local machine Administrator I can connect to some but not all servers. As a domain user I cannot connect to anything.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Gaurav Daga — Tue, 19 Dec 2006 01:10:43 GMT

Patrick, are you using ThinPrint? This application crash may have originated in the ThinPrint Client (http://www.thinprint.com/)

You may want to follow up with their technical support, by giving the crash-dump as a starting point.

Or, you can try some of their hotfixes

http://www.thinprint.com/index.php?s=4319&lc=61

Also, if you have not already done so, when you hit the error during normal operation, please report the error to Microsoft (you should get a dialog).

Thank you

Gaurav

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Server Tech — Tue, 19 Dec 2006 23:04:43 GMT

I'm also recieving the mstc.exe - application error:

the instruction at 0x10006c40 referenced memory at 0x10006c40. the memory could not be read.

I get this error when I launch mstsc. if I ignore the error I can connect without a problem. I just have to leave the error on screen. What is the process to rollback?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Sankar — Wed, 20 Dec 2006 07:19:52 GMT

I am also getting the same above error.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Server Tech — Wed, 20 Dec 2006 18:10:41 GMT

In case someone is wondering how to perform a rollback. I was able to rollback the install by installing WinUpdatesList then finding the TSC 6.0 update. Then I found the unistall command line for it. I uninstalled rebooted and an now back to my older 5.1 client.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick — Wed, 20 Dec 2006 22:45:17 GMT

Yes - it was indeed the thin print cleint. Using the new 7.0 (RDP) version of the Client fixes the issue. No server update required.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Al — Thu, 21 Dec 2006 21:01:55 GMT

Getting "can't connect, low virtual memory" errors when trying to connect from a WinXP laptop to either a XP or Win2003 Server box.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

John Doe — Fri, 22 Dec 2006 00:59:27 GMT

is there any good way to make RDP6.0 work with windows 2000? I have a fair ammount of 2000 servers in my domain still. The "pre-auth" NTLM is not used currently in 2000 so i must enter my cridentials 2x can i turn that off in RDP client or can i fix that in 2000?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

sankarp — Fri, 22 Dec 2006 10:31:22 GMT

Is there any property available to change the text on Connection Bar in fullscreen mode. It default shows the server name. I tried using property FullscreenTitle but its changing only the title text on taskbar when the fullscreen window is minimized.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Michael — Fri, 22 Dec 2006 18:07:47 GMT

I have been testing the new RDP client prior to pushcing this update out via WSUS to all of my clients. I have noticed a few problems that I may have when I push this out to my clients and would like to see if anyone has some ideas.

We are a mixed Novell/Microsoft netowrk. All of our users have there home directories on our Novell Server. We use Microsoft for just about everything else. So I have a login script that runs via group policy when the users log into the terminal server that takes there username/password using Native File Access it maps there home directory on the terminal server session to the Netware box. This has worked great. However with the new client it seems that when I start a remote session it prompts me for a username and password (as expected). Lets say I enter useranme 'user' and password 'password. It will login and work. However the next time I connect to that box it tries to put the hostname or ip address of the server in front of the username. The first problem with this is that there is no local account so I can manully change it back to just 'user' instead of '192.168.0.1\user'. Being that we use Active Directory I was like ok, I can just enter either domain\user or user@domain. This works however the problem with this is that my homedirectory does not get mapped because there is no user on our novell box called test\user or user@test.net. I do like a some of the features of the new client but need to find a way around this prior to rolling it out. If not I will get many calls and that is something I don't want. One last side note -- This is why you test software prior to rolling it out.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Ioannis — Tue, 26 Dec 2006 20:43:09 GMT

I have the same problem that Anders talked about. I downloaded the new 6.0 client, but it still says that NLA is not supported. This is on a Windows XP Home with SP2, which the download webpage says is supported. Is there any setting I can change? I tried to connect to a windows vista machine and I can't because I get an error that my computer does not support NLA. Anything I can try? Thanks!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Jon — Wed, 27 Dec 2006 08:40:28 GMT

Uninstall RDC 6.0 on Windows XP from Control Panel | Add / Remove Programs. Check the box "Show Updates". Locate update "KB 925876" and uninstall.

Haven't had any problems since uninstalling.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Jamie — Wed, 27 Dec 2006 12:27:04 GMT

In my opinion, the new Remote Desktop client is seriously broken.

Firstly, there should be an option (other than a hidden RDP file setting) to disable prompting for credentials before connecting. If the server is prompting for credentials anyway, it means I have to enter things twice.

Secondly, I can no longer remote desktop to a XP Pro SP2 machine in my workgroup. Looking at a network trace, the "server" machine is resetting the connection. There's obviously something in the data that's being rejected.

How on Earth was this software allowed to be released when there are so many bugs in it?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

DJonathan — Thu, 28 Dec 2006 02:40:13 GMT

Easy to install. Added confusion along with new desired features. No compatability mode by default (assumes I am in the new Longhorn environment), even though it is pushed out via Windows Updates as an update.

Hard to figure out how to uninstall. Leaves new Icon after uninstall, just to continue the confusion I guess. I will try again next year(2008).

RDC 6.0 Cannot connect to existing XP machines

J. Garcia — Sun, 31 Dec 2006 01:17:35 GMT

I installed this on an XP SP2 machine and i am trying to connect to another XP SP2 machine.

I keep getting "This computer cant connect to the remote computer. Try connection again...".

Therefore uninstalling.

Should have know it would not work...

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

John Doe2 — Tue, 02 Jan 2007 15:31:32 GMT

To echo a comments above, this RDP6.0 client is extremely slow in connecting and any Windows 2000 server clients require 2x logins (well the first can be garbage entry as it's not used, but you still must enter it!)

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Trevor — Tue, 02 Jan 2007 21:05:05 GMT

Just had this update pushed to my machine, no real problems when connecting to 2003 server.

BUT connecting to a 2000 server ( admin mode ) requires that I first enter the credentials into the client app and then when it fails to pass them to the server you have to enter them again.

We have lots of 2000 servers and it will be some time before we migrate to 2003

How can I stop it requesting the credentials twice.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Louis — Wed, 03 Jan 2007 19:09:36 GMT

I can see how the network authentication might be handy. But, I connect to several computers in several domains, and I really won't be able to get by without the dropdown box for picking a domain. I hope the network authentication option will be disabled (hopefully by default) in a future release.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Steve — Wed, 03 Jan 2007 20:01:48 GMT

Thanks for the uninstall info it helped greatly. I have been testing the new version to see if it is a good update or not. My vote is not, I hate having to log in twice to get to my 2000 servers and will not allow any of my users to install this update. If this is what we have to look forward to in Lonhorn I think it can wait a few years.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Dan — Wed, 03 Jan 2007 21:18:24 GMT

I tried the 6.0 update, and subsequently wasn't able to connect to the server I'd been using. Uninstalled it, and all was pretty much well again, although my icon is still changed. While the higher graphics resolutions are nice, they're not necessary. I'm connecting to servers for administrative purposes, not something that needs the higher resolution. I'll try again with the next version, maybe. Meanwhile, we'll be declining this one through WSUS.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

sankarp — Thu, 04 Jan 2007 14:41:33 GMT

Whats are the names of ActiveX properties to disable/enable sound redirection and Windows key combination?

re: Remote Desktop NLA Not Supported

Andre — Thu, 04 Jan 2007 18:49:15 GMT

I have installed RDC 6.0 in order to have a more secure connection to my Vista computer by using NLA. After installing the client on my Win XP Pro SP2 the "About" dialog of the RDC indicates Network Level Authentication (NLA) Not Supported. I have verified and the NLA service is active and running on my XP PC. Why is NLA showing as not supported and how do I fix this?

Thank you,

Andre

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

PJK — Fri, 05 Jan 2007 16:52:06 GMT

I find that when using .rdp files to connect, the user's username is always prefixed by the machine name and a backslash. This is stupid. I have a domain, and the proper form would be to prefix the username with the domain name and a backslash, or use no prefix at all.

Worse is when I'm connecting over the Internet. Now my username is prefixed by the DNS name of the server and a backslash.

Yet another example of a programmer trying to make my life easier, but not anticipating all the possible situations that might actually make it harder.

And I echo those who are using a purely internal TS, and don't appreciate the inability to use a .rdp file with a saved username and password.

Microsoft, please let us determine for ourselves the level of security we need. Secure by default? Sure - thanks. But no option to disable inconvenient, redundant checks? Don't be my nanny. I can decide when it's necessary.

Thanks,

PJK

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Joel — Fri, 05 Jan 2007 16:59:07 GMT

Is there any way to remove the machine address from the login? I am using RDC to administer servers and usually use an IP address or a URL (such as mail.domain.com) to connect. RDC 6 adds the IP address or the URL onto my user name (x.x.x.x\username or remote.domain.com\username). Of course, the servers are behind firewalls and have no idea about that IP/domain so they reject the login and I have to re-enter it.

Joel

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Fri, 05 Jan 2007 20:45:00 GMT

To those that dont like the populated domain provided: is there any reason why you do not correct the domain one time, and then in subsequent connections to the same machine, you should have the right domain

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

PJK — Fri, 05 Jan 2007 22:07:06 GMT

Nope, it doesn't work that way in my experience. The username is always prefixed by some version of the machine name, which is generally a useless rendition of the lgoin name. My users always have to remove the machine name and the backslash every time they log in.

PJK

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Ryan — Sat, 06 Jan 2007 14:41:58 GMT

Yes, I agree it would be great to be able to remove the server name that is now added.

Previously, I would see a login screen where all I had to do was type in a password. Now I have to remove the superfluous severname and enter a password.

I am not fussed that the login is before connection (because I only see one login so the work is the same), but the fact that I have an extra step is a pain.

I concur with PJK that you can remove the servername and login and it still comes back next time...

Remove the machine address from the login

DT — Sat, 06 Jan 2007 17:44:55 GMT

Please, please, please reinstate the ability to enter the Domain in RDC. I have 3 remote server to administer and all require that I must re-enter the password to logon. Our password are randomly generated 30 character strings -- and I can't cut-and paste! This is independant of clipboard settings in RDC; logins can't be pasted.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

PJK — Sun, 07 Jan 2007 06:51:17 GMT

For those annoyed by the new authentication scheme, see this posting:

http://help.lockergnome.com/windows/Terminal-Services-Client-Authentication-ftopict536599.html

I haven't tried any of this yet, but I thought it might be helpful.

pjk

re: Automatically detect GW server settings

Jeff Bryant — Mon, 08 Jan 2007 22:48:25 GMT

Does the "automatically detect GW server setting" option work? If so, what needs to be configured. I suspected it looks at the domain name portion of the FQDN, but a netmon trace shows no SRV DNS query or anything of the sort.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

termserv — Mon, 08 Jan 2007 23:12:39 GMT

This is controlled by a Group Policy setting.

Rob

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Barry — Tue, 09 Jan 2007 21:26:08 GMT

I have installed Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP. Now I can no longer connect to the machines that I could connect to before. Can someone please tell me how I can revert back to the previous (5.1?) version? Is it possible to "Uninstall" Remote Desktop Connection?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick Rouse — Tue, 09 Jan 2007 21:34:45 GMT

Search this page for the word "uninstall" and you'll find the answer.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Henry — Wed, 10 Jan 2007 23:59:17 GMT

hi i've seen that some people had already some problems connecting to a server with smartcard. today i was at one of my customers who installed Terminal Services Client 6.0 and after selecting the certificate for login i receive the prompt for username/password. i tried the same procedure with a windows vista machine, where it worked perfectly (at least i get the enter pin screen). i already checked, that smartcard is selected under local devices. has anyone a solution to this issue?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Nelly Porter [MS] — Thu, 11 Jan 2007 03:17:42 GMT

Hey,

I am investigating all concerns that people posted here with RDP Client 6.0 authentication issue when they connected to WS2000/WS2003. To reproduce the problem I need some additional info: when smart card auth did not work for you, you were connecting from WinXP with RDP6.0 client to what server OS? You also enabled smart card redirection (it is good and required). In your post you also mentioned Vista worked for you, Vista as a client or a server?

Thanks,

Nelly

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Henry — Thu, 11 Jan 2007 09:38:20 GMT

Hi Nelly

I installed RDP 6.0 on an WinXP with SP2 (fully patched). At my customer I tried to connect to a Win 2003 Server (SP1 & fully patched) and also to a WinXP computer. Both computer don't have RDP 6.0 installed and on both computers I couldn't connect via smartcard. Then I installed RDP 6.0 on the WinXP computer, but the problem was still the same. With my Vista (Business Edition) computer I tried to connect as a client. When I connect to the same computers I receive the PIN prompt and as soon I type in my PIN I can successfully login to both computers. Could it be a CSP-related problem?

Regards,

Henry

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Ken — Thu, 11 Jan 2007 19:13:31 GMT

Add me to the list of people that want a way to turn off the double sign-in. I work internally with a mix of 1500 different servers and the double login is a major pain - as is the fact that this is being pushed by automatic updates.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Venkat — Fri, 12 Jan 2007 03:03:54 GMT

mstsc.exe - Application Error

The Instruction at "0x00d0fd50" reference memory at "0x00000008". The memory could not be "read".

Click on OK to terminate the program

All of our users get this message anytime they disconnect at Terminal server session - from any server. Graceful Logoff, or just closing the window.

Anyone have a fix for this? Please?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Nelly Porter [MS] — Fri, 12 Jan 2007 03:41:42 GMT

Henry,

Thank you very much for your follow up comments and clarifications, it helped me to understand your scenario much better.

I have some theory around the issue you described and if you would be able to validate it, I would really appreciate it.

Here we go:

1) Smart card authentication from RDP6.0 client installed on Windows XP would not work when you connecting to WinXP. It is a known problem. We are planning to come up with KB to explain the current situation. Also we will consolidate all feedback that coming right now from all of our customers to understand if we need to proceed with WinXP patch/updates.

2) Smart card authentication from RDP6.0 client installed on Windows XP should work when you are connecting to WS2003 SP1. However, what I believe the root cause of all confusions around TS client authentication with smart cards is related to Credential UI( CredUI) for WinXP. This version of CredUI does not recognize your smart card automatically and always prompt for User name and Password, instead of PIN (what you would see on Vista and expect. This is a major difference between WinXP and Vista CredUIs). Despite our confusing UI, if you would click on the arrow of the “User” combo box to open drop down list of the credentials, you would be able to find one of the smart card certs ( if you have more than one on your smart card). Select it and provide your pin. It should connect you to the Windows 2K3 server with no problem.

Henry, I would like to ask you to validate this theory, if you would have the opportunity.

Answering your question is it CredSSP related? The answer is no, it is mostly CredUI related.

Thanks very much for your feedback and help,

Nelly

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

juan — Fri, 12 Jan 2007 05:51:11 GMT

I successfully downloaded and installed Remote Desktop Client 6.0 for Windows 2003 Server x64 today. Unfortunately, when I try to connect to a Windows Vista machine with NLA enabled, I get a dialog stating, "The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support."

Is this supposed to work, or does it only support Vista clients? If the latter is the answer, then why would they even mention NLA on the RDP 6.0 client for 2003?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Nelly Porter [MS] — Fri, 12 Jan 2007 06:04:58 GMT

Juan,

Thanks for your feedback.

Currently, only Vista supports Network Layer Authentication (NLA) natively.

To make your configuration work, you need to modify your remote host (Vista) to allow connections from any clients. ( System Property/Remote).

Nelly

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

David Neil Smith — Fri, 12 Jan 2007 12:35:21 GMT

I too can confirm the issues with the server name replacing the domain name prefix in the logon username box; just when I had got all my staff used to entering their usernames too. Why oh why is this happening?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

David Neil Smith — Fri, 12 Jan 2007 13:03:00 GMT

I am re-posting perhaps as an apology but maybe this might help those people who are finding the issue with logon credentials of servername\username rather than domainname\username.

I changed my logon to username@domainname and the rdp client remembered this for future use.

Perhaps it might be worth trying.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Fri, 12 Jan 2007 18:25:21 GMT

if you enter proper domainname as domainname\username, then RDP client should remember domainname\username. It is only when you provide NO domain, and just submit username, when it will remember servername\username.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Andre — Fri, 12 Jan 2007 23:13:49 GMT

There are a few people in this page who have indiacted that they can't connect to a Vista machine when it requires NLA on the client side. The client side has RDC 6.0, there are XP Pro and 2003 machines, none show support for NLA as posted a few times by various people above (including me).

Nelly has indicated that NLA is only in Vista, but has not answered any of us as to why the feature would be in RDC 6 if no other OS supports it, nor have we been told if and when it will be implemented.

It would be nice to get a straight answer on this once and for all so that we may stop asking this question over and over.

Please let us know when and if NLA will be available as a patch for OS' other than Vista!

Thank you.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Gaurav Daga — Sat, 13 Jan 2007 00:53:35 GMT

Venkat - reposting the comment that I posted earlier for the same error:

Are you using ThinPrint? This application crash may have originated in the ThinPrint Client (http://www.thinprint.com/)

You may want to follow up with their technical support, by giving the crash-dump as a starting point.

Or, you can try some of their hotfixes

http://www.thinprint.com/index.php?s=4319&lc=61

Also, if you have not already done so, when you hit the error during normal operation, please report the error to Microsoft (you should get a dialog).

Thank you

Gaurav

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Gaurav Daga — Sat, 13 Jan 2007 00:56:13 GMT

Venkat - adding to my last comment: another user confirmed the following:

Yes - it was indeed the thin print cleint. Using the new 7.0 (RDP) version of the Client fixes the issue. No server update required.

TS Client 6.0 Feedback

Terminal Services Team Blog — Sat, 13 Jan 2007 02:28:20 GMT

Since we released the client on the Windows Update site, we received a lot of feedback in our blog, in

TS Client 6.0 Feedback

Terminal Services Team Blog — Sat, 13 Jan 2007 02:33:39 GMT

Since we released the client on the Windows Update site, we received a lot of feedback in our blog, in

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Nelly Porter [MS] — Sat, 13 Jan 2007 04:45:46 GMT

Andre,

Andre, Thanks for your comment.

You asked “..when would NLA will be available on downlevel OS?”

I would not be able to provide you concrete answer. MS does see the value of providing NLA support for downlevel Oss and is investigating if the practicality of delivering this, but at this point no decision has been made.

Nelly

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

sanjay — Sun, 14 Jan 2007 04:27:37 GMT

while RDP is working smoothly, however, it is connecting to the remote machine after repeated attempts ...4-5 times at least...I have Zonealarm Pro on the remote machine (server-Xp Pro SP2)...pinging the remote machine with -t option sometimes helps in speeding up the connection (less tries)...any idea why I cannot connect on the first attempt.

Remote machine is configured as Always On in the power settings.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Alexander Liffers — Mon, 15 Jan 2007 06:09:51 GMT

Someone mentioned adding a configuration setting to the rdp files saved for server connections to stop the new client from doing that annoying duplicate login request In our case all servers do this because we do not allow remote login without credentials typed at the time, and disabling the request from the server gives users a way in should they happen to stumble across a machine with saved credentials.

We have publically accessible servers and users work from home, and we can't control home computers, some of which are Win95/XP.

Personally, I see this new feature and having to lower server security as a security flaw rather than a feature.

To make a global change to the behaviour, you can add the setting to the hidden Default.rdp file that's in the logged in user's "my documents" folder and that'll also shut up the client once and for all.

I've had the local client save back default settings to the rdp file, and so far without it over writing this setting. Hopefully this will work for other frustrated users.

If it does come back and become difficult to control, I'll have to find a way to shoehorn RDP 5.2 back onto Windows Vista and get rid of this new one.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Nelly Porter [MS] — Mon, 15 Jan 2007 08:12:39 GMT

Thanks for reporting this issue.

This seems that you are having an issue with your Zonealarm Pro firewall. Please disable it and attempt to connect

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Ian Banyard — Mon, 15 Jan 2007 14:20:05 GMT

We've been testing server authentication (and network traffic enc) with Server 2003 Sp1. In previous versions of the clients, if you the server authentication fails you cannot connect. With the Vista RTM client, it allows you to still connect even though authentication fails. I understand that this isnt "user" authentication, but this feature could have been used a another security layer (if the machine connecting doesnt have the required certificates it wouldn't have been able to connect. Now with the Vista client this can be easily bypassed.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Philips — Tue, 16 Jan 2007 01:06:29 GMT

We also experience the problem of double login. We maintain different servers which has their own FQDN. We used to let RDP to connect to the domain and then enter the login credentials by hand.

Now we have to enter them in the reference window. Because the FQDN is not the same as the domain the external computer operates in, this login fails. The next step is entering the credentials for an second time.

Very anoying and undermining the whole 'ease access concept behind the XP/Vista RDP client'.

Hope an solution will follow soon.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Tue, 16 Jan 2007 03:21:25 GMT

Have you tried entering username@FQDN? That should work.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Mark A. Ziesemer — Tue, 16 Jan 2007 06:51:01 GMT

I'm curious to know where the saved credentials are now stored (since they're obviously no longer in the *.rdp files). (I'm using the 6.0 client on WinXP SP2.)

I would have expected them to show under "Manage my network passwords" in control panel, along with the rest of my Windows network passwords. I also made a quick run with Sysinternals' (err, Microsoft's) FileMon and RegMon, but didn't see anything of interest.

My concern is, how can I see a list of credentials that I've ever saved with the client (and remove as desired?)

I can connect to a number of computers, that the earlier computers are no longer in the MRU. Yet, I can type in the name of one of the first computers, and it still recognizes the saved credentials. I'm not comfortable with this - I should be able to view a list, and remove those I no longer want saved.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

George Rose — Tue, 16 Jan 2007 23:21:35 GMT

All I need to make this work as well as it did before the 'patch' is to be able to have the login default to the Domain rather than the local machine.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Yann — Thu, 18 Jan 2007 15:10:47 GMT

I'm dissappointed to see so many comments about not being able to connect & getting the "you're already connected" message, even you you're NOT already connected go unanswered by the blog staff.

For me, it WAS working with the new client (connecting to Windows Server 2003), but now it's not. I can rdp to a vista machine on the same network, but no longer to the server.

Why are so many people, myself included, suddenly having this problem?

Login fails due to username@server.com

mattias w — Sun, 21 Jan 2007 13:53:07 GMT

Was stupid and upgraded to version 6 on my WinXP.

When I click on .rdp file, it tries to login using

username@server.com

instead of

username

which of course fails. So everytime I have to delete the "@server.com" part.

Suggestions on how to solve this? (Except uninstalling v6, can I do that?)

Doesn't help to edit the .rdp file and add

username:s:<username>

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Sun, 21 Jan 2007 19:59:06 GMT

Simply delete the "@server.com" part (I assume in the credentials dialog). If you successfully logon, the next time you try to connect to that server, you will only see "username" You should not have to delete "@server.com" EVERY time. You should have to do it just once

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

mattias w — Mon, 22 Jan 2007 10:13:31 GMT

I have to delete the @server.com part each time. Otherwise I wouldn't complain :-)

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Dennis@7summitsict — Mon, 22 Jan 2007 17:55:16 GMT

A feature request; could you built-in a proxyserver tab?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

termserv — Mon, 22 Jan 2007 20:20:07 GMT

The TS Gateway (if that's what you mean by Proxy Server) is controllable from the Advanced tab. Click Settings...

If you mean something else, could you explain?

-- Rob [MS]

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

buckh — Tue, 23 Jan 2007 07:36:28 GMT

The Terminals application on CodePlex (http://www.codeplex.com/Terminals) provides a tabbed GUI for RDP sessions using the RDC client. It rocks. It would be awesome to get this functionality into the RDC client.

See http://www.epocalipse.com/blog/2006/11/05/windows-terminal-services-client/ for a description and screenshots.

Buck

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

John X — Wed, 24 Jan 2007 22:36:49 GMT

I use a WinXP Pro SP2 Tablet and need connections to a Vista Business machine. I have installed this update and still get a "NLA is not supported" and is "not supported" in the about--version 6.0 window-

is there a way to enable this?

what is the point of having an XP client if it does not support these changes?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Josh [MSFT] — Fri, 26 Jan 2007 00:54:06 GMT

John X:

NLA support for pre-Vista OSes is being looked at.

In the meantime, if you want to use RDP 6.0 on a non-Vista machine to connect to a Vista machine, you need to tell the Vista machine not to require NLA. You can do this by going to Remote Settings (right click Computer, select Properties, then select Remote Settings from the left hand bar) and select Allow Connections from computers running any version of Remote Desktop.

RDP 6.0 has some advantages beyond the previous version unrelated to security (better device redirection for instance) that still make it a good option, but for now, NLA on XP and 2k3 is not available.

Console Root Terminal Services sort

serge — Fri, 26 Jan 2007 02:08:51 GMT

Does anyone know how to sort the list of Terminal Sevices Connections at the Console Root in MMC?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released - Application Error

John Hagan (Hagan@Trilon.com) — Sat, 27 Jan 2007 20:45:04 GMT

I support several small businesses in my area. A few of the workstations I support at more than one site encounter the "mstsc.exe - Application Error" problem. These stations first successfully connect to a remote station, then after logging out, return to the Remote Desktop Connection as usual. However, when they choose Cancel to close the application, they see the Application Error. The instruction address seems to vary, but the referenced memory is always at "0x00000008" and cannot be "read".

I have removed the 6.0 client update using Add/Remote Programs, and the original version of Remote Desktop Connection works correctly. Reinstalling the 6.0 client again causes the Application Error described above.

Is there a fix in the works? Would remote access to one of the problem workstations help diagnose the issue? If so, I could arrange access for a support engineer.

Please direct any response to Hagan@Trilon.com, as I do not routinely check this blog. Thanks for any help you can provide.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released - Application Error

John Hagan (Hagan@Trilon.com) — Sat, 27 Jan 2007 21:27:09 GMT

Wow--isn't it always after posting a problem, I find a fix myself!

First, let me clarify my previous statement:

"However, when they choose Cancel to close the application..."

I meant:

"However, when they choose Close to close the application..."

Sorry for any confusion that may have caused.

Now on to the good news: I removed the ThinPrint client (http://www.thinprint.com/) from a station experiencing the Application Error, and I no longer have any problem closing the RDP 6.0 client.

I hope that helps some other people with their Application Error issues.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

XDvir — Wed, 31 Jan 2007 12:33:50 GMT

Hi,

Recently I installed the RDP 6 Client and I have these problems:

1. I am getting on the about screen Network Level Authentication Not Supported - Does not find a way to activate it.

2. On our server, all the properties of the application is loaded per user by his account name. Some users that needed several properties have several logins on the server.

Now with the new update, it does not let us save few usernames for the same server. Even not with "Always Ask For Credentials" it is still overiding the previous username every time the user tryes to log on with another username.

Is there any way to set it to enable multiple logins credantials for the same server?

Cheers,

Dvir

re: Network Level Authentication is broken on XP

szlevi — Fri, 02 Feb 2007 01:46:36 GMT

Why there's absolutely NO MEANINGFUL ANSWER with regard to this issue???

This lack of clear information is totally annoying and represents a very typical (should I say chaotic) MS-styled mis-communication at best - powerful stupid at worst...

Please, somebody from MS: state it clear when you will fix this 6.0 client because KB925876 is definitively a BROKEN release as it apparently still does not support Network Level Authentication and broke several other things too (see posts above).

Looking forward to your explanation,

Levente Sz.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick Rouse — Fri, 02 Feb 2007 02:35:43 GMT

"NLA on XP and 2k3 is not available." It's a feature of Vista Client to Longhorn Server communication. Just like when you connect with a newer RDP Client to a 2000 TS, you can't get > 8 bit color, even thought the client supports it.

NLA is not a current feature of pre-Vista Clients.

Is that clear?

Patrick Rouse

Microsoft MVP - Terminal Server

Citrix Technology Professional

Provision Networks VIP

President - Session Computing Solutions, LLC

http://www.sessioncomputing.com

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Nelly Porter [MS] — Fri, 02 Feb 2007 11:13:01 GMT

Thanks Patrick for your attempt to clarify issues with Network Layer Authentication and RDP6.0 client on Windows XP.

Network Layer Authentication is a way of establishing secure network connection prior to a session creation on the remote server. This feature would be available only and only with Vista clients connected to the Longhorn Server.

Network Layer Authentication is the layering functionality on top of Vista authentication platform, so RDP6.0 on Windows XP OS would not be able to provide it without underlying OS wiring on Windows XP.

I hope it would clarify the confusion with Network Layer Authentication.

Nelly Porter

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Garlyn Norris — Fri, 02 Feb 2007 18:49:41 GMT

Earlier there where many comments regarding the slowness of the RDP client whenv connecting to various servers. I am running windows vista and have been running windows Xp sp2 with remote desktop client 6 and have been experiencing major issues connecting to various servers due to speed. Is there an update to remote desktp yet? Can an earlier version be run on windows vista?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Nelly Porter [MS] — Fri, 02 Feb 2007 19:15:31 GMT

One correction to my own post: Vista client would be able to authenticate users when connected to Vista Server, however the value of this scenario is lower, compare to connection from Vista client to Longhorn server.

Nelly Porter

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Nelly Porter [MS] — Fri, 02 Feb 2007 19:18:30 GMT

Garlyn,

What are you connecting to? Vista to Vista? Vista to XP or WS2K/WS2K3? Is it nested sessions that you see being noticeably slow?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Mike — Mon, 05 Feb 2007 14:53:49 GMT

I just tested the new client. I think screen flickering with non-ts-friendly apps (e.g. with VisualStudio 2005) got much worse. This also leads to misses while scrolling (scolling continues although the cursor key has been depressed.) Saw this behavior on Win2003 as client to couple of Win2003 hosts (1600x1200 res, 16 or 24bit, with or without bitmap-buffering enabled, connected via LAN). I downgraded to old client and retestet, and it behaving like we are used to it again.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Dale — Tue, 06 Feb 2007 08:08:34 GMT

Remote Desktop was recently updated to version 6 during an automatic update. Now when I attempt to connect to the remote computer, I get a user name/password prompt. When I click on the down arrow for the user name box, I see the message "Incompatible smart card." I attempted to find a way to uninstall the update; however, it does not show up on the add/remove programs page. How do I either back up to the old version or correct the compatibility problem?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Mike T. — Tue, 13 Feb 2007 23:51:55 GMT

Remote Desktop was updated to 6.0 on a host computer with XP SP@ installed on it and now only clients with the 6.0 client software can connect to the host computer. Is this a result of the client update to 6.0 on the host or another Windows Update to the RDP itself? If it is a result of another update, which one is it that needs to be rolled back? I have customers that refuse to upgrade their client software, yet still want to connect to the host machine.

Thanks,

Mike

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Jordan — Wed, 14 Feb 2007 08:14:15 GMT

Any response to Richard's comments about log in lag from the dev team? Why is it slow to respond w/ 'netbios over tcp' on. I'm still confused with Richard's explaination and I don't know why I should have to turn off netbios over tcp to get the login promptly.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Jordan — Wed, 14 Feb 2007 08:15:19 GMT

... and the change does help w/ login speed, btw

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Sam — Tue, 20 Feb 2007 13:43:54 GMT

Does anyone know how I can script the removal of the version 6 client as someone accidentally approved the install via WSUS.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

david gallagher — Fri, 23 Feb 2007 23:32:20 GMT

Cut and paste between client and server is not working. The first cut from local can be pasted into the remote, but subsequent cut/paste just paste the first cut.

Any ideas

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

termserv — Fri, 23 Feb 2007 23:40:49 GMT

David, have you looked at http://blogs.msdn.com/ts/archive/2006/11/16/why-does-my-shared-clipboard-not-work-part-1.aspx and http://blogs.msdn.com/ts/archive/2006/11/20/why-does-my-shared-clipboard-not-work-part-2.aspx ?

Rob

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Chris Oleschu — Sat, 24 Feb 2007 07:30:06 GMT

I get the application error upon session launch. It happens as soon as I hit connect, whie the credentials box is up. Same as oter people are describing. NOI DONT USE THIN PRINT. I have a freshly loaded tablet pc w/sp2 and all updates. What do I do? This is happening on 17 of my other pcs as well!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Selder — Tue, 27 Feb 2007 12:42:38 GMT

Is there any chance that Seamless Windows are possible with a client version 6?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

James B. Wood — Wed, 28 Feb 2007 23:54:15 GMT

Problem solved! Uninstall KB925876! Why did I install it in the first place(?) - I don't use Vista!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Mark Goldey — Thu, 01 Mar 2007 19:41:41 GMT

I have to agree that the 'double login' is a bad feature. The problem isn't really that there are two login screens. The problem is that the RDP client seems to be sending the target machine a username of "ipaddress/username" (or "domain/username") instead of just "username".

Changing to "username@IP" (or "username@domain") does not help because our usernames are just "username".

The client does not remember any changes made, and the drop-down menu never populates with "username" or anything else. It insists upon "IP/username" and nothing will make the default change, or give the user a mouse-selectable choice.

IMHO, it should be possible to turn off the domain/IP part of the username, so the client won't try to populate the username with that information.

The alternative suggested above of just hitting OK (and setting the client to connect even if authentication fails) is the equivalent of putting up a dummy dialog box with an "OK" button on it, between the dialog to select the remote machine, and the dialog to authenticate the user. I do not see the point of this, or how it improves the old client, which at least would remember if you identified youself as domain/user.

If the idea was to allow the user to select the remote machine and the username in a single click, then then first dialog box should have modified to do that. Frankly, I'd be happier from a security perspective knowing that the client will not send the password to the remote machine until the remote machine acknowledges that a user with the provided username exists on the machine, and then have a second dialog open, prompting me for the user's password.

In any case, this new client is not a welcome addition to my desktop.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Sebastien — Thu, 01 Mar 2007 20:20:46 GMT

Any news about the NLA compatibility under non-vista OSs ? Can we expect a firm date ?

I dont mind setting up the Vista server to allow all connections, but if possible, i'd like to enjoy the security features provided by NLA on my XPSP2 gear.

Thanks in advance

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

John McGee — Fri, 02 Mar 2007 17:39:10 GMT

Thank you to Jon for posting the info on removing KB925876 to roll back, it would be nice if this info was found more easily. More importantly though, I can't imagine how any system administrator could possibly use the new client until it is understood how to save the credentials for more than one identity for a given TS. Every admin I know logs into servers as different users, and relys on the securty of their workstations to keep the saved username/pwds saved. I could not figure out how to do this with the new RDP clieint. Is it not possible? it appears to only allow you to save the credentials of a single identitiy per TS. comments from msft on this topic would be appreciated.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Mika Selin — Sun, 04 Mar 2007 21:52:44 GMT

Another problem I found out was, that the new RDP 6 client doesn't really like SSH-tunnels too much. With RDP 5.1 client there was not problem, but the RDP 6.0 cliend doesn't work if you tunnel the connection trough localhost (127.0.0.1) to the server at port 3389.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Niranj — Sun, 04 Mar 2007 22:44:18 GMT

How can I take a Windows server crash dump thru MS RDP session..plase update if anyone knows about it.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

jingram — Thu, 08 Mar 2007 02:15:13 GMT

Well here is our situation. We originally did our TS setup on Windows 2000 and migrated the server over to Windows 2003 several years ago. We have several applications published on the Terminal Server and have the Terminal Server setup to always login with one username and password. This way the user simply clicks on a shortcut and the application launches. This has worked great for years! After RDP 6, this functionality broke. As other mentioned, we have a number of users that have absolutely no idea what a domain is or the concept that the application they are running is actually running on a server under a Terminal Services environment. All they want is to be able to use their application. Things are absolutely in total chaos after this "update" and with no ability to uninstal, well that is ridiculous! At the very least we should have the ability to do that. So, is it impossible to get back to where we were? Simply have the application launch when they click on the an icon or are we SOL?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Carlos — Fri, 09 Mar 2007 06:40:27 GMT

We're having the same crap issue with the Application Errors upon exiting MSTSC. Believe it or not, what fixes it for me is if you disable DEP (Data Execution Prevention) for the app or for the whole O/S. :-( So the app may have a bug in how it calls for memory.

Any thoughts on this?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Carlos — Fri, 09 Mar 2007 18:44:43 GMT

Also, we're able to go back to the old version of the client by copying both mstsc.exe and mstscax.dll from a non-updated machine into your c:\windows\system32 directory....but that one still blows up with the memory error for us too with DEP enabled.

Why isn't this a security problem?

Joel Reinford — Fri, 09 Mar 2007 19:20:24 GMT

Can someone explain to me why this new version isn't a big security hole? The client may be providing a username and password to an unverified location. Suppose I normally connect to a server at xx.xx.xx.32 and I type in xx.xx.xx.31 instead. That IP might belong to someone else and now that someone else could grab my password. Ditto for a server at remote.abc.com, oops, I put in remote.abv.com and now they have my username and password.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick Rouse — Fri, 09 Mar 2007 20:48:40 GMT

There will be an updated 6.x RDP client before Longhorn Server is released that should address the issues that people have addresed.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Vincent Yao — Wed, 14 Mar 2007 12:55:24 GMT

Font smoothing doesn't work when I connect from home (vista) to work (xp pro). It used to work when I was using xp pro at home. Once I upgrade it to vista, it stops working...

Can anyone tell me why?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Nelly Porter [MS] — Wed, 14 Mar 2007 20:26:25 GMT

Font smoothing will work only and only when you connect to Vista/LHS host.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Chris B. — Mon, 26 Mar 2007 21:39:31 GMT

I was hoping that someone could tell me why TSclient6 won't disconnect from my Win2k3 TS at logoff. Apparently users are logging off and it just goes back to the server login instead of disconnecting the client (as with TSclient 5). Is this a problem or by design? Is it possible to get TSClient 6 to disconnect @ logoff?

My email is chris(at)8degrees(dot)org for anyone who might have a response.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

George C — Tue, 27 Mar 2007 04:26:49 GMT

I installed the TCS 6.0 client in November and once again a few minutes back. I am connecting from this laptop to a Win3K server and the Windows Keys are not working in the remote session. The session is configured to apply the keys sequences on the remote machine (as well as in full screen mode). This works flawless on two other WinXP SP2 machines. Something seems to be "stuck" on this machine. I have looked around for some registry setting that may help, but I have not found anything.

TIA.

George.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Martin Gaciarz — Wed, 28 Mar 2007 23:30:45 GMT

I was fairly excited about this update when it came out, but after I used it for a while, I decided that I have to uninstall it. My main gripe about the new client is how it caches the usernames for RD connections. For example, when I connect to my server and log in with domainuser, the next time I go to connect to my server, the cached username is computername\domainuser instead of domain\domainuser. This is even less helpful than no caching at all, since I have to shift-tab to the username field and take out the computername part...

As far as uninstalling, I did a registry search for the KB # (925876), and this led me to find the uninstall command line:

C:\WINDOWS\$NtUninstallKB925876$\spuninst\spuninst.exe

(in my case)

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Redowa — Thu, 29 Mar 2007 05:09:52 GMT

In Dale's message from Feb 6, he mentions an "incompatible smart card" problem. When I run 6.0 on XP, I have the same problem, but when I downgrade to 5.1, no problem. Is this error a part of the other smart card problems that have already been discussed? Is a fix in the works?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Jean Oiler — Thu, 05 Apr 2007 23:33:29 GMT

I really need Terminal Services Client 4. something. Can someone help me?

Jean Oiler

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

isaac — Sun, 15 Apr 2007 18:19:42 GMT

Impractical, complicated and time consuming.

How it was ever expected that normal, non administrative, unpriveleged END-USERS should magically understand that they need to manually remove the username prefix or manually add their UPN suffix (almost all end-users would not know this) is completely beyond me.

Prefixing the username with the FQDN of the server you have chosen to connect to is absurd. I would have thought that providing this wonderful thing called "Remote Access" is a primary feature of TS

Is not the ethos behind SSO that the END-USER need only remember 2 things - their user name and their password? Login behaviour via TS should be identical to that via the users' desktop OS when they login to their domain by simply typing username/ password & selecting the valid domain.

Someone mentioned there should be an option to disable this functionality, and someone said these issues should be resolved before LHS is released.

Anyone have any more info on UsernameHint functionality as per http://help.lockergnome.com/windows/Terminal-Services-Client-Authentication-ftopict536599.html posted above?

/wrists

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick Rouse — Sun, 15 Apr 2007 21:28:26 GMT

Terminal Services Team Blog Entry - Details of Remote Desktop Client 6.1 released to the public (March 28, 2007)

http://blogs.msdn.com/ts/archive/2007/03/28/ts-connection-experience-improvements-based-on-rdp-6-0-client-customer-feedback.aspx

Patrick Rouse

Citrix Technology Professional

Microsoft MVP - Terminal Server

Provision Networks VIP

President - Session Computing Solutions, LLC

(949) 433-9422

http://www.sessioncomputing.com

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

isaac — Mon, 16 Apr 2007 10:05:57 GMT

Thanks Patrick! Good news!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Confused — Thu, 03 May 2007 04:52:22 GMT

Having recently upgraded to RDC 6 I am experiancing dropped connections on my Windows XP SP2 client when connecting to a Windows 2000 SP4 Server. The Server people tell me I am the only one with this problem and point to my ISP as the source of the problem. However the only thing that has recently changed is the RDC client software. When trying to roll it back to a previous version (add/remove KB925876) I am presented with a list what looks like every program on my computer that it warns that it may uninstalltion may impact. So, is there anything in RDC 6 that might be causing the constant disconnections to the Win2K Server that I can adjust, and/or is uninstalling KB925876 going to impact any of my other applications as it warns?

Thank you!

How to rollback Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Bret — Sun, 06 May 2007 02:03:40 GMT

open add/remove programs in your windows control panal then make sure show updates is ticked (top right). Find update (KB925876)in the list and remove, and you are done

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Leo — Sun, 06 May 2007 18:10:46 GMT

The new client is absolutely awesome from a usability standpoint. Its been a snap to use and easy to intuitively configure!

TS team, you guys did a great job!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

paul — Wed, 16 May 2007 01:46:18 GMT

I am trying to connect to my Terminal Server running 2003 from a Vista home machine and am getting a DEP error. Any help would be appreciated.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Rafael — Thu, 24 May 2007 11:30:25 GMT

Hi there

I just tried to use smart card authentication to log in via RDP to a WIN2003 SP1 Server (from a Windows XP SP2 Client with RDP 6.0 installed).

I selected "smart cards" under local resources. When I connect to my Win2003 Server I can choose the certificate from the dropdown list first, enter the pin and get connected: But on the Win2003 Server I get a standard login prompt with userid/password?

I saw that several other people have had that problem before but I didn't find a solution yet.

Rafael

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Joz — Fri, 25 May 2007 23:16:00 GMT

I can't even connect to an XP box using remote desktop on Vista Ultimate. I have to connect to a Win2k3 box, then from there, remote desktop to my XP box. I don't know if anyone else has had this problem; I'm sure it's something strange with Remote Desktop on my Vista box. I had a buddy use Remote Desktop on his Vista box to connect to my XP box and it worked. If anyone has a clue about what could be wrong, please let me know!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Steven Ryerse — Thu, 31 May 2007 08:15:06 GMT

I've read thru this entire blog and I see very very little positive feeback about version 6.0. It looks like Microsoft has Vista'd RDC as well. Microsft seems to want to improve the home users while severely hurting Business Users. Win XP was awesome the day it came out and my expereince so far with Vista related stuff is that other than the improved graphics it is an awful thing to support for businesses. We are a long time Microsoft Partner and we do large installs of dozens of workstation at a time and all this exra setup is going to cost our customers a lot of unnecessry money spent. There is no reason why the new RDC client needs two separate logon setup screens when maybe another tab was all that was needed. We have many end users who can't even understand how to click Start and then All Programs to find the programs they need. If we can't put an Icon on their desktop with everything already preset then they can't figure out how to use it. They don't know or care what a domain is they just want to be able t write down their user ID, Password, and the name that has to go into the third field. Better security and some of the other features would be nice but RDC 6 as it is now is totally unusable. The suggestions here to go back to RDC 5 are not an option if you are running Vista already. What the heck was Microsoft doing the last 5 years while working on Vista, did they not bother to listen to their business customers? Everyone wants simpler installs and not more complex installs! Why does it have to be so hard and why do we have to put up with this level of pain?

I have a folder with about 100 .rdp files for various servers at all of my diferent custmers. It has worked great for years but now is basically useless as I have to fgure out how to fix each one so that I can remote into my customers servers for maintenance. What a mess! Does Microsoft even use their own new software? Obviously not in the real world. They have gone from the ability to set up several servers in the old Microsoft/Citrix client of 4.0 to separate but decent .rdc files of RDC 5.x to the horrible unmanagable 6.0 without remembering where they came from and who their customers are.

I hope Microsoft takes all this negative feedback and goes back to the drawing board to "fix" RDC the right way and to "fix" Vista Business so it is easy to roll out a lot of workstations in a domain. They better do it quick because they are losing a lot of business as I can't in my right mind recommend any business over about 5 computers go to Vista or RDC 6. If this is what we have in store for us with Longhorn then I'm changing careers! At least the Home users are now happy . . . .

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Bart van de Beek — Sat, 09 Jun 2007 13:47:16 GMT

I find many of these remarks pretty much out of place... First of all, RDC 6 is the next gen. client. As such it is meant to connect to VISTA/LongHorn TS, NOT 2003/XP or even less. Secondly, RDC6 is not a critical update. People have to install it themselfs since it's optional. 3rd, advances in technology often break things in backwards-compatibility. I believe microsoft deliberately forsaked on backwards compatibility since it would be impossible to improve it with new features, TS gateway being one of them. Backwards compat. will improve as 2nd thing as it has been MOST of the time with MS this way with most of their products. It's this feature that peopple complain about most. Advice: people connecting to 2000/2003/XP should use RDC5, NOT 6. If you have 6, revert back to 5. There's not much benefit using RDC6 to connect to 2000/2003/XP anyway. Problem is just with people on vista, they cant revert to 5. So connecting Vista to 2003 will give you these problems. To get rid of it once and for all, I've written a batch. Copy/paste this into a textfile, name it rdc.cmd, put it in windows-folder, then create a shortcut having this as commandline:

cmd /c rdc <your domainname, FQDN, IP or NETBIOS DOMAIN>

This batch simply strips whatever it otherwise prepends to the username. I admit, it's just a workaround, but at least it works until microsoft releases the next version which probably will have more logic added to detect better what the client is connecting to, and which also fixes the USernameHint-bug (which really is a bug in the 6.0 client). Hope this will help most people having this issue here.

This batch leaves all other options and features intact, so saving credentials, choosing not to save them, etc. all still works. This batch only strips every time you use it to logon, nothing more. Be advised that in a multi TS environment this batch can lead to other problems, be aware of this!

The batch:

@echo off

if %1x==x goto help

for /f "usebackq tokens=2 delims=: " %%i in ('echo %1') do set a=%%i

for /F "usebackq delims=" %%i IN (`reg query "HKCU\Software\Microsoft\Terminal Server Client\UsernameHint" /v %a%`) do set t=%%i

for %%i in (%t%) do set n=%%i

set name=%n%

if %n%==REG_SZ set name=

if %n%==UsernameHint set name=

if not %name%x==x for /f "usebackq tokens=2 delims=\" %%i in ('echo %name%') do set name=%%i

reg add "HKCU\Software\Microsoft\Terminal Server Client\UsernameHint" /v %a% /d "%name%" /f

start mstsc /f /v:%1

exit

:help

echo RDC FQDN/IP/DOMAIN to connect to

echo RDC replaces the annoying crediantial dialog of Remote Desktop Connection 6.0

echo asking and setting FQDN\Username as default

echo It does this by stripping the FQDN/IP/DOMAIN-part,leaving only the username

pause

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick Rouse — Sat, 09 Jun 2007 18:17:53 GMT

RDP Client 6.1 that's in Server 2008 Beta3 provides the same kind of authentication that version 5.x did when connecting to 2000 & 2003 Terminal Servers. I would imagine that this will be released for XP SP2 and higher clients around the release of Server 2008.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Smarty — Tue, 12 Jun 2007 11:25:03 GMT

Hi there, Is there a way to send virtual functional keys (VK_F1 to VK_F12) to remote application ? By pressing the hard keys on the client, remote application is able to receive the functional keys. I would like to achieve the same by sending virtual functional keys. Any help is greatly appreciated.

-Smarty

re: Network Level Authentication - MS messed us around!

Nick — Thu, 28 Jun 2007 03:20:43 GMT

I share the frustration of Andre, Levente and many others.

Patrick Rouse and Nelly have offered little of any quality.

Patrick - regarding your 'is that clear' negative comment. What is clear to me is that this morning on my Vista Ultimate machine at home I enabled NLA - as it misleadingly states it will work on Vista or other machines with NLA version of RDP and is better becasue it is more secure. KB925876 also misleading states that the 'featires' are only avaiable to remote computers running Vista - which mine is. Now you are saying sorry it wont work and to make my machine less secure, from using one MS Windows product to another!

WE ARE ALL HAVING THIS PROBLEM - THANKS TO IN PART MISLEADING INFO. DOES IT TELL YOU SOMETHING IF WE ARE ALL HAVING THIS PROBLEM. I suggest you refine your customer skills and listen when many experienced customers are having the same issue.

I wopuld appreciate being able to RDP from my Business XP pro sp2 machine to my Home Vista Ultimate machine using NLA security. Is that asking too much when I have invested recently into both these MS operating systems?

Your customers are FRUSTRATED. Any other business will quickly go bust. Soon maybe MS will if they dont learn or listen.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Patrick Rouse — Thu, 28 Jun 2007 04:35:11 GMT

I am NOT a Microsoft Employee, but am a customer. NLA is NOT, and as far as I know will not be added as a feature for downlevel OS. The Terminal Server team, as far as I know, does not have control over NLA, as this is not a Terminal Server, Remote Desktop, or RDP specific feature. A 6.1 Remote Desktop Client is in the works, as has been posted several times by Microsoft.

As for your quote of mine being a negative comment, it was not intended as such, but rather as a question.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

fuzb — Wed, 18 Jul 2007 13:19:54 GMT

Hello,

Before I start some feedback:

NLA - Great

CredSSP - wow, looking forward to not typing my password 100 times a day.

RDP with Aero/Desktop Composition - Fantastic

New Vista logon UI - Fantastic for smartcards, annoying to put in domain name - I only have one domain, why can't it be default?

TSWeb - Hmmm

Using Vista with RDPClient 6.0 the old Win2k3 TSWEb AX errors with "Error in licencing protocol" and will not work.

Using XP with RDPClient 6.0 - works, but annoying "are you sure you want to connect the clipboard, etc?" messages - I NEED A WAY TO TURN THESE OFF, I am the administrator and I don't need to delegate this decision to our users, they don't care, they just want to get on with their job and let someone else look after security. I used to have drives on too but now have to turn off all sharing to give them a good experience and deal with the helpdesk calls when they can't use their USB sticks or clipboard and point them to a special URL with the settings and prompts.

Thanks!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Admin guy — Mon, 13 Aug 2007 22:50:13 GMT

Patrick, I thought you were clear. NLA is not a feature of XP, if you try to connect from XP it wont work. This is why CHARTS are better than paragraphs in some cases, put together a chart or table and everyone will be able to clearly see what works.

Hey, Terminal Services Team, this user humbly requests that you give us a nice link to an article that will show us the recommend ways to make the most secure connection possible to a TS machine. hopefully it will show how to add layers of security and include info on smartcards, certificates, etc.

thanks in advance

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Ramesh Gogineni — Sat, 18 Aug 2007 00:52:25 GMT

I have Windows Vista Business and Office 2007 installed on laptop. I can connect to the first client without any problem. Whenver I try to connect to an additioanl client (different IP) at the same time, Remote desktop crahes with the following signature:

Problem signature:

Problem Event Name: APPCRASH

Application Name: mstsc.exe

Application Version: 6.0.6000.16386

Application Timestamp: 4549b425

Fault Module Name: StackHash_2ba6

Fault Module Version: 6.0.6000.16386

Fault Module Timestamp: 4549bdc9

Exception Code: c0000374

Exception Offset: 000af1c9

OS Version: 6.0.6000.2.0.0.256.6

Locale ID: 1033

Additional Information 1: 2ba6

Additional Information 2: edb81efb925a9e212708c512a1009784

Additional Information 3: c16e

Additional Information 4: d1e5272f31bf042e4e228a6256de90ab

Do you have any suggestions to help me?

Ramesh

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Key to escape out of tsc

ligesh — Wed, 22 Aug 2007 02:35:02 GMT

Hello,

Does anyone know if there is any shortcut to escape out of the fully maximized terminal services client? It seems the tsc grabs all keys, and it would be nice if there was a way to get out of it, other than using the mouse on the small title bar that appears at the top.

Thanks.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

termserv — Wed, 22 Aug 2007 02:53:47 GMT

CTRL-ALT-Break will escape out.

Rob

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Anthon — Mon, 27 Aug 2007 12:14:08 GMT

Hi,

I have trouble with the printer redirection on the XP computers with RDC 6.0 installed.

Is there any known issue about this?

Thanks.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Rich Raffenetti — Mon, 27 Aug 2007 23:25:39 GMT

Since upgrading to RDP 6 I have had some difficulty accessing my office PC remotely. My office PC is an XP/SP2 Tablet Edition.

The difficulty is connecting. The authentication is ok but during the connection process it appears to get so far (almost done) and then the whole session disappears.

This weekend the same problem was happening. I removed the upgrade with add/remove programs and was able to connect with no difficulty with RDP 5.

Will RDP 6.1 fix this?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

rudy truyens — Fri, 31 Aug 2007 12:05:16 GMT

For those having problems with loging in twice, do the following.

Click on the options button. Click save (this creates a default rdp in my documents

Op the default rdp with notepad and add a new line "enablecredsspsupport:i:0" at the bottom.

problem solved....

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Ramesh — Tue, 04 Sep 2007 08:38:35 GMT

Rudy:

Thank You for your suggestion...Unfortunately, adding the new line to the default rdp did NOT solve the problem.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Tim Chamberlain — Wed, 05 Sep 2007 23:35:16 GMT

Here's an odd issue we're experiencing after upgrading to 6.0... On our terminal servers we use an application called Spectrum Messenger made by Telescan. It's an internal IM client and works for our needs. We have two terminal servers, one with 2000 on it (sp4 + up to date) and another with 2003 on it (sp2 + up to date). When a user connects to the 2000 box, there are absolutely no issues. However, if a user connects to the 2003 box AND has Spectrum Messenger running (doesn't matter if they are logged into it or not, as long as it's running) the session becomes slow and very unresponsive. If a user connects with v5.x everything works fine. I've tried turning all of the unnecessary options off (printers, smart cards, lowering the display to 8bit ect.) but the problem still persists. Spectrum Messenger uses port 6767 by the way. If anyone has ANY ideas as to what this could be please let me know.

Thanks,

Tim

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

james — Mon, 10 Sep 2007 17:17:35 GMT

Pls admit this is a useless bit of software. My remote users still use rdp5.2. Ver6 is useless. Why is it asking me to logon twice and why would I want to log on locally to a server?. Why can't it just work?. MS please listen to your customers. Thank you or at least test the software first. Im waiting for an update me thinks.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

John Kittelsrud — Fri, 14 Sep 2007 03:25:53 GMT

Is there any reason that RDC requires CTRL+ALT+DEL to be pressed on the target machine if the Novell Netware client is installed? If I have a user boot a machine up and just leave it I can not login remotely to do any work on it. Now if they press CTRL+ALT+DEL and bring up the Netware log in screen I can get right in no problem. Is this a problem with Netware, RDC, or the OS?

All systems are running XP Pro and the Netware client is 4.91 sp2.

Thank you.

-John K

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Colin LeMahieu — Thu, 04 Oct 2007 23:11:51 GMT

If you have an RDP session within an RDP session, how do you send a CTRL-ALT-DEL to the inner session? CTRL-ALT-DEL is captured by the local machine, CTRL-ALT-END is captured by the first session, how can this be done on the inner session?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Chuck Hallback — Fri, 05 Oct 2007 03:13:03 GMT

The problem with controlling the RDP options via the default.rdp file, e.g. to turn off the double logon prompt, is that after installing the client, you now have to touch the default.rdp file for every user on every PC or server they use, no an elegant solution. Why in the world don't you have global setiings, or use a GPO?

Another problem is that the Windows key now no longer works on the remote desktop, when you press the Windows key, it brings up the start menu, on the local desktop.

Could you please fix these issue ASAP?

Thanks,

Chuck HAllback

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Chuck Hallback — Fri, 05 Oct 2007 03:13:53 GMT

Another problem is that the Windows key now no longer works on the remote desktop, when you press the Windows key, it brings up the start menu, on the local desktop.

Could you please fix these issue ASAP?

Thanks,

Chuck HAllback

P.S. This blog is SO slow, it's almost unusable

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Chuck Hallback — Fri, 05 Oct 2007 03:18:12 GMT

Another problem is that the Windows key now no longer works on the remote desktop, when you press the Windows key, it brings up the start menu, on the local desktop.

Could you please fix these issue ASAP?

Thanks,

Chuck Hallback

P.S>. This web site is SO slow it is almost unusable.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

dazone — Fri, 05 Oct 2007 03:55:18 GMT

Sorry for the triple post, I kept getting server errors about page not found.

The major changes in behavior from remote desktop 5.2 to 6.0: e.g. prompting for credentials before connecting, the Windows key not working on the remote desktop, etc, is analogous to Microsoft coming out with an MP3 player that is not Playforsure compatible, and won't play the DRM protected WMA files that law abiding people have been buying online for years ... Like a Zune. Didn't you beta test remote desktop 6.0?

If Microsoft would get feedback from real people/users, they could avoid these major blunders that make people lose faith in them.

Chuck Hallback

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Sergey Kuzin — Fri, 05 Oct 2007 21:09:13 GMT

remote desktop 6.1 (coming with Vista SP1) will not have double logon problem and will not prompt for credentials before making a connection. So, you won't have to make changes to default.rdp.

Vista SP1 is also going to have reacher GP support for remote desktop client.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

dazone — Fri, 05 Oct 2007 21:15:48 GMT

Will the problem with the Windows key combos, and alt-tab, not working on the remote desktop also be fixed? For us this is the biggest show stopper on deploying the 6.0 client.

I didn't see this mentioned on your list of issues for the 6.0 version.

Thanks,

Chuck Hallback

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Peter — Mon, 08 Oct 2007 10:15:31 GMT

Installed the XP SP2 RDC update but now getting always this error. But if I move away the error dialog I'm able to sign on and get connected to remote system. Is this a known issue?

AppName: mstsc.exe AppVer: 6.0.6000.16386 ModName: unknown

ModVer: 0.0.0.0 Offset: 011a5c50

manual removal

Girc — Wed, 10 Oct 2007 10:14:10 GMT

RDC6 was installed on my computer while making a repair install (yes, _now_ I know I should have unplugged my computer from the net :)) and cannot be uninstalled normally via Add/Remove Programms or WinUpdatesList. Is there a way to remove it manually, like deleting mstsc.exe and all references to it in registry?

Thanks a lot.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

termserv — Wed, 10 Oct 2007 19:30:14 GMT

To Girc:

There should be a checkbox that controls whether to show updates. Check that box, and you should see the RDC update, which will allow you to uninstall.

Rob

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Girc — Wed, 10 Oct 2007 21:35:55 GMT

To Rob:

Thanks a lot for the answer, but I tried it and unfortunately it does not show, that's why I asked for a way to remove it manually :)

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

dazone — Thu, 11 Oct 2007 04:45:13 GMT

Will the problem with the Windows key combos, and alt-tab, not working on the remote desktop also be fixed? For us this is the biggest show stopper on deploying the 6.0 client.

I didn't see this mentioned on your list of issues for the 6.0 version.

I would hate to have to use a premier support call to find out the answer to this

Thanks,

Chuck

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

shadowpuk — Wed, 17 Oct 2007 15:24:57 GMT

To Chuck:

I also have the "alt-tab" problem with rdpclient 6.0...it's stopping to work sometimes but I really don't know why :/

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Elvis — Wed, 17 Oct 2007 19:38:31 GMT

I have a 22 inch monitor at work that's set to 1680x1050 resolution. I connect from home to work PC via Remote Desktop just fine (using laptop from home - smaller resolution of course). However, when I come to the office, I find a message on my monitor "Set screen resolution to 1680x1050" and only way to recover is to reboot my work PC.

I suspect Remote Desktop is not resetting work PCs resolution to what it's usually set to (1680x1050). Is there anything I could do?

Will this new client remedy this issue?

Windows XP service pack 2 on both work & home pcs.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Yaniv Kaul — Thu, 01 Nov 2007 18:54:52 GMT

I also witnessed the same strange netbios lookups for '..LOCALMACHINE' - using strings, I verified they are in the RDP 6 client code. Any idea how to get rid of this ~7 seconds delay?! very annoying.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

peter — Fri, 02 Nov 2007 23:31:03 GMT

Setting up a new XPe thin client that came with RDC 6 installed.

Trying to connect to a Windows 2003 SP2 terminal server.

The terminal server has Novell Client 4.92 installed (we authenticate against NDS and AD).

With RDC 5.x the user would be delivered directly to the Novell Client login screen.

With this RDC 6 the user is prompted for login credentials which do not seem to work.

If I enter the username password (usernames and passwords are synchronized between NDS and AD) I am told the username/password combination is incorrect. This is because the RDC is trying to connect to a local account on the terminal server where the user has no account. The user then has to change the setting from the local machine to the domain, uncheck the workstation only checkbox on the Novell Client and log in. The same problem occurs when using a fully qualified name.

The only way I have managed to get the users to connect is to have them enter a bogus name in the username field and leave the password empty.

Is there any way of turning off authentication?

Is there way of changing the default user name?

Is there any way of uninstalling RDC 6 from an XPe build that has it as a defualt so I can install RDC 5.2? I tried installing RDC 5.2 but was told that I could not as RDC 6 was already installed.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Chris — Thu, 08 Nov 2007 20:19:46 GMT

Hi, we're having a strange problem that appears to be happening since upgrading to mstsc 6,

we have four windows 2003 servers that we connect to via remote desktop / terminal server sessions.

the mojority of the time we log on and off without issue, however sometimes the log off is not smooth.

i click 'log off' and confirm this, desktop/explorer closes and i'm left with the blue background and the yellow task bar across the top of the screen, the sessin will stay like this for as long as you are prepared to leave it.

if i press ctrl+alt+end whilst in this hung session i can choose log off again and the session closes.

Strangely there are no entries in the event log to give me an ide how to troubleshoot.

through testing i've found this happens more often if i fire up a connection and immediatly log off.

Any thoughts as this ones driving me crazy

Thanks in advance

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Chris — Thu, 15 Nov 2007 15:18:58 GMT

Found out what my logoff problem was, it was cured by editing default.rdp and adding enablecredsspsupport:i:0

the problem was related to RSA

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Steph Jones — Wed, 21 Nov 2007 18:03:14 GMT

What about the domain:s: parameter - will this ever be fixed? Its causing major headaches for our multi-domain, multi-terminal server situaton across domains and trusts!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Jarmo — Fri, 30 Nov 2007 03:22:12 GMT

You guys complaining about the Windows key *not* working are the lucky ones ;-)

I have 6.0 build 6000 and it thinks the Windows key is permanently depressed! So if I press the letter 'e' it will invoke explorer, 'r' the run menu etc. Really tiresome, but not 100% reproducible.

Pressing and releasing the Windows key stops this behavior. And no, I do not have a stuck Windows key -- I never have this issue anywhere else on my machine except in a new terminal services session.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Daniel — Fri, 30 Nov 2007 03:58:49 GMT

Accidentally pushed this out to some client PCs via WSUS, and realized it crippled our ability to connect to a Windows 2003 terminal server. Now manually removing update 1 at a time. This should have been marked as experimental, not a critical update :p

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Oisin Grehan — Thu, 06 Dec 2007 01:18:24 GMT

I also have the random "windows-key is acting like its stuck" issue with RDP 6.0 from XP to XP (both sp2).

Just slapping the windows key a few times sometimes works, but occassionally it doesn't go away at all until I disconnect/reconnect a few times.

Weird.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Steve — Wed, 16 Jan 2008 12:44:05 GMT

Remove the double authentication requirement.

To stop the RDP client prompting for credentials before showing the actual remote machine login screen, append the following two lines to your My Documents\Default.rdp file, and any other .rdp files you have saved:

prompt for credentials:i:0

enablecredsspsupport:i:0

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Dave Huang — Sat, 26 Jan 2008 00:19:58 GMT

If NLA is not supported on XP or Server 2003, why is it listed as the very first bullet point in this blog post?

Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

We've released the new version of the Remote Desktop Client corresponding to Vista. Here are some of the new features:

* Network Level Authentication

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Thendralvanan — Wed, 20 Feb 2008 14:35:11 GMT

Hi,

I couldnot remotely connect our server suddenly its running on windows server 2003 am using XP proff.After rebooted its working can any one tell me what was the prob?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Thendralvanan — Wed, 20 Feb 2008 14:35:36 GMT

Hi,

I couldnot remotely connect our server suddenly its running on windows server 2003 am using XP proff.After rebooted its working can any one tell me what was the prob?

Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Asset Management — Tue, 06 May 2008 15:56:09 GMT

Hello there,

I have trouble with the printer redirection on the XP computers with RDC 6.0 installed.

Anything I can do?

Cheers

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Elspeth O'Brien — Thu, 08 May 2008 11:39:33 GMT

I was recently experiencing an issue mentioned earlier in this blog: "The client could not connect. You are already connected to the console of this computer. A new console session cannot be established."

The client was running Win XP SP2 and the server was Win Svr 2003 Std Edn SP1. I was able to resolve this issue by installing Win XP Service Pack 3 on the client. SP3 upgrades the Remote Desktop Protocol to v6.1.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Peter — Sat, 10 May 2008 22:19:48 GMT

Today installed XP Professional SP3 from the updatecenter and getting same error signature as I reported on 8/oct/2007.

AppName: mstsc.exe AppVer: 6.0.6001.18000 ModName: unknown

ModVer: 0.0.0.0 Offset: 00e65c50

Any suggestion to stop this error?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Di Han — Wed, 14 May 2008 01:23:23 GMT

Recently updated to RDP 6.0. on Win XP SP2. My connection to different customer servers all work fine. But I receive error message when logging out of the session "The instruction at '0x00e..' referenced memory at '0x...'. The memory could not be 'read'. This occurs to all my connections. What should I do?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

John — Wed, 14 May 2008 09:28:32 GMT

Is the "Windows key *not* working" has been resolved so far?

I used RDP 6.0 on my XP SP2 and it was a huge pb. In each TS session, the keyborad shortcut did not work despite I enable this dfeature in the .rdp files! I uninstall the RDP 6.0 client to the 5.2... which worked perfectly.

But i've just install XP SP3... and you know what? RDP client is bundled! So I've still got my pb... Hey MS gus, don't tell me you did not solved the pb with some registry tweaks!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

James — Wed, 14 May 2008 22:52:27 GMT

When using the new 6.0 client and trying to access my terminal sever, which is running a novell client login, I have some issues. After entering the machine name to RDP to I am immediately asked for a user name and password. If I enter both to move on the TS screen pops up for a second like it is going to work and then goes away, coming back to the prompt for the IP or machine name I want to connect to. If I leave the password field blank I can then get to the log in screen on the terminal server. Is there a fix for this issue?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

John — Tue, 20 May 2008 17:49:28 GMT

I've found the resaon of "Windows key *not* working" problem!

If you're experiencing trouble with Windows key cobinations you have to start the terminal services service on your client computer.

For example if you want to have alt+tab working in the remote TS session, you have to start the terminal services service on your Windows....

very funny

Tell me Guys, where is it documented?

Network Level Authentication with XP SP3

Nere — Wed, 21 May 2008 10:08:35 GMT

Even with XP SP3, Network Level Authentication does not work by default from the RDP client. You have to activate CredSSP: http://support.microsoft.com/kb/951608/en

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Corey — Fri, 30 May 2008 18:48:22 GMT

I am using Windows XP Pro with Terminal Services Client 6.0 running. I am connecting from the XP machine to a Windows Vista Ultimate machine. I have no problems connecting, but I am having problems with certain keyboard keys when accessing the remote Vista machine. When I type the 'e' key it opens a computer window. When I hit the space key it changes the fcous of the windows. When I hit the 'r' key it opens the run dialog. When I hti the 'u' key it opens the ease of access center. This only occurs when I am using remote desktop from my XP to vista machine. Anyone have any thoughts?

Thanks!

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Rob McInnes — Sat, 07 Jun 2008 13:17:58 GMT

> I've found the reason of "Windows key *not* working" problem!

Brilliant solution and well-found, sir! I'd been hunting for a solution to this, as I'm one of those who turns off all unwanted services...

-RM

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Faizal — Fri, 04 Jul 2008 10:39:37 GMT

With regards to Dale's and Redowa's problem with incompatible smartcards, i believe that this is caused when the server that is hosting the card is not able to communicate with the Smart Card Issuing Certification Authority.

The only workaround that i know is to uninstall this patch which to me has no added value for Windows server 2003 or Windows XP users.

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Sylv — Thu, 10 Jul 2008 22:51:29 GMT

I have setup Remote Desktop web Connection on a office machine and have forward the relevant ports - configured firewall etc, but all I get when I click on connect from the Remote Desktop web Connection page is a white box - nothing else. the error message states

const L_ClientNotSupportedWarning_Text = "Remote Desktop 6.0 does not support CredSSP over TSWeb. If you cannot connect to this server because of Network Level Authentication problems, please visit Windows Update to obtain the latest update to Remote Desktop Connection."

' error messages

const L_RemoteDesktopCaption_ErrorMessage = "Remote Desktop Connection"

const L_DisconnectedCaption_ErrorMessage = "Remote Desktop Disconnected"

const L_InvalidServerName_ErrorMessage = "An invalid server name was specified."

Can anyone help me please?

how to span screen in vb using mstscax.dll

Abdul jalil — Tue, 22 Jul 2008 08:16:51 GMT

i have register mstscax.dll and use in vb, i have doual monotor support. i can span the screen by uing the comman mstsc /span but i use activeX in vb to span the screen. which property is to be set that span the screen on multiple monitor

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

alGore — Fri, 01 Aug 2008 09:05:27 GMT

every few minutes while being connected to Server 2008 Standard by way of Remote Desktop the connection continually drops. I've tried it with other routers and other computers. It has been narrowed down to the Server 2008 O.S.

Has anyone experienced the same ordeal?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

montu — Wed, 10 Sep 2008 09:32:07 GMT

please understood me about remote desktop in simple word and how to make this software in vb ?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

montu — Wed, 10 Sep 2008 09:40:14 GMT

please understood me about this software in simple word and how to make in visual basic? who read please send me answer in this id king_6021@yahoo.com

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Roger Stumbaugh — Thu, 13 Nov 2008 21:49:45 GMT

I was just curious if anyone has run into this. I have noticed recently on a few machines that my connections aren't being saved. I don't have alot of info to provide, but it seems to be related to the shortcut. I am not sure if the actual shortcut was always in the Terminal Services folder in Administrative tools, but that seems to be where the problerm lies. I have noticed this issue in Vista Ult, sp1 and server 2008 ent(sp1). If I just open the console and add a few connections, then close the console and open it again, the connections I added are all gone. I've noticed this on both OS's. Even if I open the console and change it from author mode to user mode full, the same thing happens and the console defaults back to author mode. However, if I create a new console and add remote desktops(add snapin) and save this and change it from author mode to user-full everthing saves and works well. Has anyone ran into this?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

margaret — Sat, 15 Nov 2008 18:46:33 GMT

Hi, I am running XP SP3 on a laptop. After an automatic Windows update, my remote data connection no longer works. Something called data execution prevention keeps shutting down the connection, even after I told it to protect everything EXCEPT rdc. Any ideas?

Can not access USB eToken from Aladdin from RDP

Leif Jansson — Thu, 15 Jan 2009 10:21:48 GMT

Installed drivers and management SW for USB eToken from Aladdin on Windows Server 2003.

Starting management SW locally and all works.

Starting management SW via RDP and USB eToken is not found by the management SW.

Any idea for a solution?

Downgrading the connection

Jeff — Wed, 21 Jan 2009 21:25:19 GMT

Hi,

If my server is running Windows 2008, is there a way connect to the server using an old RDP version say RDP 5?

Thanks in advance...

Jeff

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Eric Holk [MSFT] — Wed, 21 Jan 2009 22:15:39 GMT

@Jeff,

Windows Server 2008 is largely backwards compatible with previous versions of the client. The one thing that older clients do not support is Network Level Authentication. If you want your Windows Server 2008 installation to accept connections from the RDP 5 client or earlier, you will have to configure it to not require Network Level Authentication. Other than that, previous clients should work fine.

-Eric

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Denver — Tue, 10 Feb 2009 03:34:42 GMT

Hi, home destop is XPProSP3, laptop(home) is also XPProSP3, work desktop is Vista SP1. Ever since SP3 install on Home desktop I have to reboot home desktop to regain RDC. If I logoff today and try and reconnect tomorrow, "can't connect to remote computer" Is there a timeout setting or some fix regarding this new RDC?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Bob — Tue, 24 Mar 2009 20:18:07 GMT

my RDP users lose their in session printers. When they log off and log back on the printers are not reconnected. I have to reboot the server for the printers to reconnect in a session. When the problem begins, users currently logged on will keep their printers but as each user is timed out or loggs off they lose their printer when they log back on. This problem is intermintent it is not happening all the time. It just starts happening sometimes and I can not find a pattern or cause. When it happens, I have to reboot the server for the printers to start reconnecting at logon. After the reboot, it may be fine for several hours or days. Then it will do it again. Today it has done it several times. Any ideas as to what may be causeing this?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

Shaun Cobb — Thu, 02 Jul 2009 23:38:43 GMT

After installing SP3 I can no longer connect to the Console session when using the Remote Desktop mmc. It now creates and new RDP session which doesn't allow me to connect to the active Retrospect session. It's still using the same Remote Desktop mmc version 5.2.3790.1830 and the other IT computer that doesn't have SP3 connects properly. Does anybody have an idea what changed in SP3 that could cause these new sessions?

re: Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 (English Only) released

bonsaikitten@spake.the.cat — Mon, 30 Nov 2009 05:50:44 GMT

I hope motherboard manufactures collude with ram manufacturers to make the twenty four PETAbyte requirements of windows 8 affordable to those who make less than USD $60,000 annually.