Update: Some additional improvements are coming in this area. Please see this article.
There has been a lot of feedback about the new authentication features introduced in the latest version of the Remote Desktop Connection client. These features are part of our efforts to improve security for Terminal Services (TS) in Windows Vista and Windows Server code name “Longhorn” , however some users have run into a variety of problems that have caused frustration. In order to alleviate some of the frustrations, below is an FAQ on various symptoms users have run into, along with solutions and workarounds.
When using Remote Desktop Client 6.0 to connect to a Windows 2003 machine, some users have to enter credentials twice. Once before connection they will see Picture 1 below if they have Windows XP or Windows Server 2003 as the client or Picture 2 if they are using Windows Vista as the client.
Picture 1 - Windows XP - Windows Server 2003
Picture 2 - Windows Vista
The second time they will be prompted as the remote servers logon screen (picture 3)
No error messages will be shown.
Answer: This is most likely the result of the way the remote server is configured. There are two possible settings that may be causing this:
When either the option in Terminal Server Configuration administrative tool (tscc.msc) is selected or the group policy is enabled, the TS server will always show a winlogon prompt, regardless of what version of the Remote Desktop Client the user is running.
Why do users always have to enter credentials twice on Windows 2000 Server?
Answer: The setting in tscc.msc mentioned in the first question is enabled by default on Windows 2000. The administrator should disable this setting to fix the undesired behavior. Afterwards, the user can expect to not run into the winlogon screen or duplicate prompts.
Why is it that when connecting to Windows Server 2003, the credentials entered in the credentials dialog are rejected as follows:
Answer: The above behavior is caused when winlogon on the TS server cannot validate your credentials. This may be from a number of reasons: For example, the password or username may be incorrect. Other times, (and this may be the most frustrating to users), the domain may be in a format that is not recognized by the TS server. The best thing to do, when entering credentials into the credentials dialog, is to make sure that the domain, username, and password are all in a format that the server will accept. For example, let’s say one tries to connect to MyServer and you intend to log in with the MyUserName account from the MyDomain domain. If the user will just type in “MyUserName” in the User Name field in Credentials Dialog, the Windows 2003 Server will automatically pick “MyServer” as the domain value for login and the login will fail. But if the user provides “MyDomain\MyUserName” as input for the User Name, logon will complete successfully.
Despite having saved credentials, users are still prompted to enter credentials on the remote server’s winlogon screen.
Answer: This can be due to one of two reasons. Either one of the policies mentioned in the answer to the first question are enabled, or the credentials that have been saved are not valid.
In instances where the saved credentials are not valid, there is one possible scenario that may lead to this behavior and cause user confusion. Consider the following:
This is because the credentials that have been saved on the client side are:
Note that the password saved is not correct. This happens because whenever the user selects “Remember my credentials” in the credentials dialog, the credentials that are saved are whatever was typed in the credentials dialog. If the credentials are updated after connecting to the server, the correct credentials are not propagated back to the TS client and updated.
If the saved credentials are not correct, you may edit or delete them in Remote Desktop by clicking on the “Options” button. The dialog below should appear. Clicking “delete” will delete the saved credentials, and clicking “edit” will allow you to modify them.
Note that if the text “The saved credentials for this…” do not appear, then credentials are not saved.
Some users are having trouble using smart card credentials to logon.
Answer: To ensure that you can connect to Windows XP or Windows Server 2003 with smartcards, make sure that smartcards redirection is enabled.
Some users have noticed that an invalid pre-populated domain name is placed in front of the user name in the credential dialog. Users are frustrated at having to delete this bad domain on every connection. The sequence of steps causing this behavior is as follows:
Answer: When a domain is not presented for the username, Remote Desktop assumes by default that a local server account will be used and the domain name is pre-filled accordingly. In this case, the server name entered was “127.0.0.1”, and as a result, the domain entered was the same. This was done for various reasons in Vista that are too complicated (and irrelevant) to go into detail here.
The best workaround for this behavior is to always enter a proper domain into the credentials dialog. If you are connecting to machine “MyMachine” using the “Administrator” account, do not just enter “Administrator” as the username, enter “MyMachine\Administrator”. From there on out, the proper domain and username will be prepopulated in the credentials dialog. Alternatively, if the user account is an account named “DomainUser” in the domain “MyDomain”, use “MyDomain\DomainUser” instead of just “DomainUser”.
Despite having a string in the RDP file “username:s:Machine\Administrator”, the pre-populated username in the credentials dialog is something different (or maybe even blank).
Answer: This is a result of a design change. Instead of populating the credentials dialog with the last username used to connect to any server, we felt (and received positive feedback) that we should populate the credentials dialog with the last username used to connect to the specific server the user is connecting to. We felt this would provide a better experience. The downside is that users connecting to various machines with the same username would now have to reenter the username once upon their first connection to a machine. From then on, the username will be pre-populated on subsequent connections.
In the dialog below, some users don’t see how to change the domain from “127.0.0.1” to “MyDomain”
Answer: To change the domain used in the credential dialog box show above you simply put a fully qualified domain username or UPN. For example if the domain is called “MyDomain”. Simply enter “MyDomain\<username>” or username@domain.<fqdn> into the username field and the domain will automatically be updated, as shown in the two examples below.
When you connect to server with the ‘always connect, even if authentication fails’ setting set you will see the following notification dialog:
Answer: Before connecting, in Remote Desktop, do the following:
This will disable the warning prompt. Please be aware that selecting this option makes it possible for attackers to intercept and modify the data exchanged between client and server.
Several other forums on the internet have suggested placing “enablecredsspsupport:i:0” in the RDP file used by the Remote Desktop client.
Answer: This option does disable the new credential prompting behavior, but it also disables support for Network Level Authentication for Vista (and Longhorn Server) RDP connections; Network Level Authentication requires credentials to be provided by the client before a session is created on the server side.
This option is meant for dealing with unexpected failures on connections using Network Level Authentication.
We strongly recommend users avoid using this flag unless none of other fixes described in this post work and no other alternative is available. If this setting is used try to limit its scope as much as possible by using it only those RDP files meant for connections to specific servers (i.e. avoid setting it in your Default.rdp file).
Deploying this configuration option widely will cause hard to diagnose issues when connecting to Vista and Longhorn Server computers that require Network Level Authentication.
PingBack from http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-connection-authentication-faq.aspx
Great post. One question, for the item "How to eliminate the ‘Remote Desktop cannot verify the identity of the computer you want to connect to…” messages," I think it is obvious to any slightly observer that the warning message can be suppressed.
Supressing the message isn't the same as solving the problem, however. So what I am really wondering is whether Microsoft plans to release an updated server component for Windows Server 2003 R2, WinXP, etc. that will add the security mechanism to avoid the issue you stated: "Please be aware that selecting this option makes it possible for attackers to intercept and modify the data exchanged between client and server."
Unfortunately, we do not know when the required pieces for Windows Server 2003 R2, WinXP, etc. will be available.
If you haven't noticed my links on the left hand side of my blog you really need too!!! I've had the
Como sabéis al usar el cliente 6.0 de Remote Desktop normalmente pide validación antes de entrar en el
Aki az új RDC klienst (6.0) használja, annak érdemes figyelnie ezt a blogot. There has been a lot of
Some places have been suggesting to use 'enablecredsspsupport:i:0' as a way to avoid getting prompted for username and password on RDP connections. The side effect is that it also disables Network Level Authentication support in Vista and Longhorn, whic
So I've posted this before but not received a response. Server authentication with the older clients will simply refuse to connect if you dont have a trusted certificate on your client. Good for some rudimentary security. Now with the vista client you are providing a way to bypass this. Sure you can override this behaviour - if you own the client. Not the smartest move no?
I've experienced a delay between the first prompt and when the terminal session window finally comes up. Its not uncommon for that delay to last almost 30 seconds as I just see a box with "Connecting to <servername>" displayed.
Is there anyway to remedy this? The only suggestion that I've found that worked was to disable Netbios over TCP/IP. That's not really feasible for me as it disables too many other features as well.
If I (or my users @ work) install this update I/we can no longer access our extranet via our Juniper server.
I forget what the cause is. But, I remember that they are working on a fix. Until then, I have to remind users not to install update this at home. But, I'm guessing that anyone running Vista will have no choice?
Good work on the updates, though. Works a treat on my work pc to our servers (same LAN).
Why mess with a good thing? Not one admin I've spoken to since 6.0 has said anything nice about the new RDP client. In fact, many times over, there have been dismay and expressions of anger.
If anything, the 6.0 client SHOULD have a check box where we can either do it the way it's always been done (i.e, 5.0 way of doing things) or the new Microsoft way.
I HATE having to type credentials in only to find out I can't connect to the box.
I've actually heard colleagues try to find 3rd party RDP clients because of this situation. JavaRDP comes to mind.
And frankly, this situation could have been avoided if more customers were involved in that strategic direction.
Connects fine to W2K server and from there to Win XP Pro but any attempts to connect directly to XP Pro result in a sort of "half way connection" with a black (not blue!) screen and no further activity, not even another request for credentials.
I too get the various combinations of error messages and have obediently followed the article's suggestions to no avail. Time-wasting and disappointing.
Have exhausted all possible combinations of settings and do not want to connect through a production server all the time to get to my main work-horse PC.
Please publish the equivalent settings to make the new client behave in the old client way. If that is possible.
@Jonathan: "Why mess with a good thing?"
It's called improvement. The new RDP adds additional authentication, which is something that many of us want to see. There may be some problems in the implementation, although it works for me just fine on the machines I maintain. I just want to see Microsoft release RDP server for Windows 2003 that includes authentication.
I think a lot of people get caught up in the "change is bad" attitude. I suggest you find jobs in more slow-changing industries. If you don't like change, then IT is not for you.
As is typical you have destroyed something that worked perfectly.
I have many RDP profiles (files.) I have several per machine. I often need to login as more than one person per machine and can do it easily prior to 6.0. I simply had one profile (RDP file) per user, pre-configured. Now I have to enter credentials every time.
What's worse is that I can't seem to figure out how to uninstall this pitiful update.
Great job. Thanks for taking us backwards. I guess it's time for VNC.
@Patrick, My RDC client in Vista saves all my user name/passwords for all the different machines I connect to, without having to save individual RDP files, as I did in XP. Is that not working for you? I think the new system is more convenient, because it stores the credentials without having to save lots of files.