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?

• Moved by Yolanda ZhuMicrosoft contingent staff, Moderator Friday, March 13, 2015 6:15 AM

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?

We've got a similar problem connnecting from W7 and Vista client machines to a W2008 Application Server on an SBS2003 domain.  Patches had just been applied to the SBS2003 machine.  I managed to overcome by resetting user password which worked for a day and then the same issue reoccured.  I've not investigated further yet.  Has anyone found a fix?

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 11 hours 7 minutes ago

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

We are having the same problems with only Win7 and Win8 machines connecting to terminal server. No problems with thin clients.   Making the changes to the Default.RDP file on the remote desktop suggested as a workaround in http://support.microsoft.com/en-us/kb/941641 worked for us (adding enablecredsspsupport:i:0).  This was only on desktops that had received the updates from the 11th.

Hi DenDiMarco,

How about the issue ?

"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. "

"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."

Do you mean both of them remoted with RDP files and only the VPN connection suffered the issue ?Have you tried to connect without the RDP files to have a check ?

Have you tried to edit the rdp files as I offered before and Michael mentioned again ?

Best regards

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.

• Edited by DenDiMarco Monday, March 16, 2015 7:49 PM

Hi DenDiMarco ,

""Have you tried to remote without the rdp files to have a check ?"

Sorry for not declaring this clearly .I mean that we can run "MSTSC" to open a UI (User Interface) and then try to connect by inputting the computer name(or ip address) and the user name .

Best regards

Yesterday, this RDP connection problem no longer occurred for any of the remote systems.

I'm guessing that additional Windows updates resolved the problem. I don't have any direct evidence of this so I don't think I can unequivocally mark this as the solution, but it seems as reasonable an answer as any.

I dont have the time to investigate this any  furhter and am happy that the problem no longer exists.

MeinoXu, I very much appreciate your efforts to help me with this issue.

• Marked as answer by DenDiMarco 16 hours 11 minutes ago
• Edited by DenDiMarco 16 hours 10 minutes ago

Yesterday, this RDP connection problem no longer occurred for any of the remote systems.

I'm guessing that additional Windows updates resolved the problem. I don't have any direct evidence of this so I don't think I can unequivocally mark this as the solution, but it seems as reasonable an answer as any.

I dont have the time to investigate this any  furhter and am happy that the problem no longer exists.

MeinoXu, I very much appreciate your efforts to help me with this issue.

• Marked as answer by DenDiMarco Wednesday, March 18, 2015 3:08 PM
• Edited by DenDiMarco Wednesday, March 18, 2015 3:08 PM

Hi DenDimarco,

I am glad the issue has been resolved and thanks for updating the message .

Best regards