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.
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...".
Should have know it would not work...
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!)
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.
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.
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.
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.
Whats are the names of ActiveX properties to disable/enable sound redirection and Windows key combination?
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?
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.
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.
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
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.
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...
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.
For those annoyed by the new authentication scheme, see this posting:
I haven't tried any of this yet, but I thought it might be helpful.