After March 11, 2015 Win updates to 2008 and 2012 servers, RDP to servers from Win 8 fails with "Your credentials did not work"

I start these RDP's using a batch file. Sample contents of the batch file are

mstsc "C:\Users\Den\Documents\Momentum\Remote Desktops\TC-Win08-64.rdp" /f /admin

These worked yesterday. In fact, with one of my 2012 servers, I had connected to it this morning, then restarted it to apply updates and now when I try to connect using RDP I get the message, "Your credentials did not work".

Is there a solution?

March 12th, 2015 4:28pm

Hi, MeipoXu,

Since there are so many Windows updates, I tried to include them as a graphic snapshot. However when I tried to post this message, I was given an error message that I can't include a graphic in this message until my account is verified. So I will just tell you this new information for now and hope it's helpful.

Based upon further investigation, I believe that the issue is not related to Windows 8 but to the fact that I connect from home to my office network using a VPN. I believe that after the Windows update, in some way, the Windows 2012 R2 server (and other computers on the office network) no longer consider my VPN connection safe.

My evidence is this: If I logon to a Windows 8 computer within the office network, I can RDP from that computer to the Win 2012 R2 computer.

I will check your other links, but I first wanted to provide this new information.


  • Edited by DenDiMarco Friday, March 13, 2015 8:12 PM
Free Windows Admin Tool Kit Click here and download it now
March 13th, 2015 8:12pm

Sorry, I've been to busy to try to trouble shoot using your suggestions. I have a work-around, but now I will address you suggesitons.

When you say "Have you tried to remote without the rdp files to have a check ?", I'm not sure what you mean. Do you mean

  • From my home computer to skip using the VPN to conenct to my office netwrok, and try to use File Explorer?
  • Or from my home computer to connect with the VPN the VPN, and then try to use File Explorer? IF so, then how exactly: Look via the Network icon or key the remote address in direcetly?
  • And what exactly does this check?

When you say "We can uncheck the "Always ask for credentials "option to have a check", I already have it set up to automatically log on using the batch file, so I don't understand what you are suggesting here. Again, what exactly does this check?

I will now attempt the first link you referenced.

*** Update

I followed the instructions in the first link

  • Ok, I found that if you save your connection settings to an .rdp file, then edit it with a text editor and add the line:
  • enablecredsspsupport:i:0
  • You can then connect without supplying credentials first.

** Results

  1. I was able to connect
  2. Once connected, I was not logged in
  3. Instead I saw a screen with a different "user name in a tile" display on the left and an "Other User" tiledisplayed to its right
  4. When I clicked on the "Other user" I was presented with a log on window
  5. My correct user name was then dosplayed, but I had to type my password.
  6. Then I was able ot log in.

So I'd consider this a work-around since it requires extra clicks and extar typing each time I log on as opposed to simply double-clicking a batch file.

I will try the other link's suggestion next.

Thanks.

March 16th, 2015 2:52pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics