We've released the new version of the Remote Desktop Client corresponding to Vista. Here are some of the new features:
More details on the features are in a Knowledge Base article.
To install the new version, go to Windows Update on the target computer and look for optional software updates, or download it from the Microsoft Download Center.
Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 (KB925876)
Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 x64 Edition (KB925876)
Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP (KB925876)
Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP x64 Edition (KB925876)
Localized versions and the Multi-User Interface Pack will be released in the coming months.
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.
This is controlled by a Group Policy setting.
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?
Search this page for the word "uninstall" and you'll find the answer.
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?
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?
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?
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.
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?
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,
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?
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).
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?
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.
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.