Vista Remote Desktop Connection Authentication FAQ

Vista Remote Desktop Connection Authentication FAQ

Rate This

 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.

  1. Prompted for Authentication Twice when connecting to TS in Windows Server 2003
  2. Prompted for Authentication Twice when connecting to TS in Windows 2000 Server
  3. Credentials Entered in TS client rejected when connecting to Windows Server 2003
  4. Saved credentials do not work
  5. Cannot use smart card credentials to logon when running Remote Desktop on XP or Windows Server 2003?
  6. How to remove invalid pre-populated domain names
  7. The pre-populated username in the credentials dialog does not match the username that is in the RDP file?
  8. Can’t change domain name when running Vista Remote Desktop Connection client.
  9. How to eliminate the  ‘Remote Desktop Cannot verify the identity of the computer you want to connect to…” messages
  10. When to use the “enablecredsspsupport:i:0” RDP file option.

Prompted for Authentication Twice when connecting to TS in Windows Server 2003

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 1

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.

Picture 3


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:

  1. The most likely is the “Always prompt for password” setting is enabled on the server. In order to disable the setting,  the administrator of the server you are connecting to must run Terminal Server Configuration administrative tool (tscc.msc) and double click on RDP-Tcp. In the “Logon Settings” tab, there is an option labeled “Always prompt for password” (see the option circled in red below).

  2. Alternatively: For Windows Server 2003, an administrator may have set the group policy located at: “Administrative Templates\Windows Components\Terminal Services\Encryption and Security\Always prompt client for password upon connection”. For Vista, this same policy is located “Administrative Templates\Windows Components\Terminal Services\Terminal Server\Security\Always prompt client for password upon connection.”  Note: This policy is set as not configured by default; if this has been set remember it could have been configured either on the local group policy or a domain based group policy.

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.

Prompted for Authentication Twice when connecting to Terminal Services in Windows 2000 Server

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.

Credentials Entered in TS client rejected when connecting to Windows Server 2003

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.

Saved credentials do not work

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:

  1. User tries to connect to server. His username is “MyDomain\test1” and his password is “LogMeOn”
  2. In the credentials dialog, user mistypes his credentials. For his password, instead of typing “LogMeOn”, he types “LogMeO”.
  3. User hits connect, and hits the winlogon screen. There is an error on the server stating “The system could not log you on. Make sure your User name and domain…”, just as in the example above
  4. User properly types his credentials into winlogon, and gets his session.
  5. The next time he goes to connect to the server, the saved credentials will not work.

This is because the credentials that have been saved on the client side are:        

Username: MyDomain\test1

          Password: LogMeO

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.

Cannot use smart card credentials to logon when running Remote Desktop on Windows XP or Windows Server 2003?

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.

  1. Smart cards must be redirected. To redirect smart cards, click “Options” and select the “Local Resources” tab. In the tab, click on the button labeled “More”. In the dialog that pops up, make sure “Smart Cards” is clicked, as shown below:

  2. Use the drop down box in the credentials dialog to select your smart card credentials. In the example below, the user has the credentials “ZK-07\Administrator” selected. Instead, he needs to select the smart card credentials “Foo-Bar - ITG XXXXX” that is circled in red below.

How to remove invalid pre-populated domain names

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:

  1. User wants to connect to a machine via IP address, say
  2. He enters the correct password and username “Administrator”. He successfully logs on.
  3. The next time he attempts to connect to, he sees in the “User name” field of the credentials dialog “\Administrator”. The user deletes the text “\” from the user name field and logs on. On successive connections, he is forced to keep deleting this extraneous text.

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 “”, 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”.

The pre-populated username in the credentials dialog does not match the username that is in the RDP file?

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.

Can’t change domain name when running Windows Vista Remote Desktop Connection client:

In the dialog below, some users don’t see how to change the domain from “” 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.




How to eliminate the ‘Remote Desktop cannot verify the identity of the computer you want to connect to…” messages

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:

  1. Click on “Options”
  2. Click on the “Advanced Tab”
  3. In “Authentication Options”, select “Always connect, even if authentication fails, as seen below:

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.

When to use the “enablecredsspsupport:i:0” RDP file option.

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.

 Update: Some additional improvements are coming in this area.  Please see this article.

Leave a Comment
  • Please add 4 and 4 and type the answer here:
  • Post
  • is it no longer possible to save more than one username/pwd pair for a particular terminal server? I rely on the security of my workstation, and thus trus that my .rdp files and saved username/pwd combinations are safe. What possible security beneffit could be derived from no longer being able to store more than one username/pwd pair for a particular terminal server?!?!?

  • Is there a way to create two instances of an RDP connection to the same terminal server that use different credentials?  I have tried to do this and it seems that the credentials are stored by server name.  

    Just wondering if there is a way to accomplish what I want with this new RDP client.

  • In the "How to remove invalid pre-populated domain names", I want to know the details why this was done for various reasons in Vista.

    Even if they are too complicated the users should still have the right to know.

  • For some time now I’ve been trying to use Windows Vistas Remote Desktop Connection Application to remotely connect from one Computer with Windows Vista Ultimate installed to another Computer with Windows Vista Ultimate installed on the same local area network and workgroup.

    But every time I try to connect to the other PC from either the first or second PC I get the following message:

    “The authentication certificate received from the remote computer has expired or it not valid.”

    And the thing is I’ve tried pretty much everything from Windows Vista’s Online Help to this Windows Vista Remote Desktop Connection Authentication FAQ and lots more… and still no luck!

    So I’m hoping that someone can help me out here, there has to be someone that has experienced exactly (or very similar) the same problem as me and managed to fix it.

    So thanks in advance for everyone’s help.

    Picture of the error here:">


    Darren Straight

    Microsoft Student Partner

  • I have recently upgraded the remote desktop client on my windows xp box and one of my win2003 servers. I can no longer connect to the win2003 server anymore from the xp workstation. I keep getting the error

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

    Tried connecting to the console session with /console. Tried rebooting both boxes as well - no avail.

    I can connect to another (non upgraded) server OK and from that connect to the actual server I want, but this is not a satisfactory solution.  Do you know what I need to do.


  • Steve Lavaysse's post above fixed my problem.  Thanks Steve!


  • So if I use the new client on an XP box to connect to another XP box, and the destination XP box has the Novell Client installed, will I always have to be prompted for credentials twice?  I'm assuming yes, and that's really annoying.

  • My opinion:  Annoying useless changes.

  • I've searched around but can't find any information on how to set it so that when anybody connects to a Vista RDP session, they have to manually type in the username/password, versus having the popup screen with the available accounts displayed.

    We've already tried setting "Do not Enable Ctrl-Alt-Del" and set it to Disabled.

    That works for the interactive desktop, but not remote desktop sessions.

    Any thoughts or pointers in the right direction?


  • RDP Client on Vista saves credentials per address, using only the machine part of the address but not he port. This creates a problem when someone wants to access multiple machines that are behind a firewall and use the same external address. There is any way to change this behaviour?

  • No matter how hard you guys try to explain this, it remains a frigging nightmare for a system administrator. Easy solution: detect remote server, if Vista or Longhorn use new way, if anything else use old method.

    This is costing me so much freaking time it's not even funny, way to release beta crap to the public. Gimme back my old RDP client.

  • We are doing exactly what you are proposing, stay tune, the help is under way.

    More details coming...

  • I can only say that at EVERY SINGLE SYSTEM I sit down that where the 6.0 client is installed I install the 5.2 R2 client even on Vista machines (I carry it on a USB key it’s that annoying to me).  The 6.0 client is just flat out horrible.  It's dog slow, dangerous (saving the username gives someone 1/2 of what they need to get into a remote system and offering to save a pwd EVERY SINGLE time is just flat out ridiculously dangerous with all the laptops that get stolen each year), and VERY time consuming.  What, ‘how is it time consuming’ you ask, ponder this...  A customer domain and username that's 20+ characters long with a pwd that's equally as long, it's 2AM and I get a page saying something on their LAN is flaky so I get out of bed and try to connect only to find out their TS is not online either.  I’ve spent the time entering the domain\username and pwd only to find out their TS isn’t available.  This is the flat out dumbest thing I've ever heard.  

    Yes, I can use the hack to stop it from prompting me but I have 200+ .rdp files, how do you suggest I make this global change?

    Under an SRX we opened with this we had many other concerns about the 6.0 client that just make the 6.0 client unusable for an admin (or support desk tech) who connects to dozens if not hundreds of remote systems.  First, the PR about how you authenticate before you connect is almost laughable (exactly how many production Terminal Servers support this today?).  I’m sorry but a connection is a connection, period unless you’re going to start issuing some sort of cert to each and every user but even then you’re sending info that cannot be authenticated because you offer to save usernames & pwds.  If I pass a username and pwd either in the background or in the foreground it's still passing.  Second, you claim you're saving resources on the remote server by doing it this way, sorry MS but last I checked WE paid for the hardware NOT you so if we want to be prompted for a username & pwd and that wastes OUR resources that's our right.

    Anyway, for those of you who dislike the 6.0 client, find a 2003 Server and install the 5.2 client over the 6.0 client and restore logic to your daily tasks.  The 5.2 client works equally well in Vista as it does on 2k SP4.

    Note to MS, please stop breaking things.  Perhaps in Longhorn's later betas you'll listen update this to 6.1 and remove or allow us to disable some of the stuff in the 6.0 client.  If you’re going to break things we’ve used for almost 10 years, please add options to allow admins capabilities to easily turn it off like HKCU (or HKLM)\Software\Microsoft\Terminal Server Client\SecurityLevel=0 that turns of drive warnings for every connection.  Would it be that hard to have the client look to the registry to disable the prompting for and saving of usernames/pwds?  Should take about 10 minutes to add that code.

  • luogo grande:) nessun osservazioni!

  • When I try to connect using remote desktop in Windows Vista, it suddenly stops working.  McAfee firewall has been disabled and it doesnt work in safe mode with networking.  Any ideas>

Page 5 of 17 (244 items) «34567»