Remote desktop fails, can still connect to event log and services.

Question

 I am unable for some reason to remote into a machine that I've been able to before.  This occurred after it installed automatic updates.  At the moment I can connect to
services and the event log from another machine with the same credentials, but I can't log onto the machine itself.  Is there any way to reset this info or such.  This machine is a part of a domain and can read credentials from the domain controller. 
I also do know that remote desktop is enabled.
The following error occurs in the even log on the affected machine.
Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          2013-03-21 10:28:23 AM
Event ID:      5061
Task Category: System Integrity
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      ****
Description:
Cryptographic operation.
Subject:
    Security ID:        SYSTEM
    Account Name:        ****$
    Account Domain:        *******
    Logon ID:        0x3e7
Cryptographic Parameters:
    Provider Name:    Microsoft Software Key Storage Provider
    Algorithm Name:    RSA
    Key Name:    TSSecKeySet1
    Key Type:    Machine key.
Cryptographic Operation:
    Operation:    Decrypt.
    Return Code:    0xc000000d
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>5061</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12290</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2013-03-21T14:28:23.339874500Z" />
    <EventRecordID>937125</EventRecordID>
    <Correlation />
    <Execution ProcessID="500" ThreadID="548" />
    <Channel>Security</Channel>
    <Computer>**********</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-5-18</Data>
    <Data Name="SubjectUserName">*******$</Data>
    <Data Name="SubjectDomainName">********</Data>
    <Data Name="SubjectLogonId">0x3e7</Data>
    <Data Name="ProviderName">Microsoft Software Key Storage Provider</Data>
    <Data Name="AlgorithmName">RSA</Data>
    <Data Name="KeyName">TSSecKeySet1</Data>
    <Data Name="KeyType">%%2499</Data>
    <Data Name="Operation">%%2484</Data>
    <Data Name="ReturnCode">0xc000000d</Data>
  </EventData>
</Event>

Answer 1

 
Hi,
The following methods could be used to resolve some of the most common problems.
Potential issues that may be seen:
1.) Remote Desktop endpoint is missing
Each virtual machine that is created should have a remote desktop endpoint for the VM at port 3389. If this endpoint is deleted then a new endpoint must be created. The public port can be any available port number. The private port (the port on the VM) must
be 3389.
2.) RDP fails with error: "The specified user name does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support."
RDP connection may fail when there are cached credentials. Please see the following article to resolve this problem:
http://www.c-sharpcorner.com/uploadfile/ae35ca/windows-azure-fixing-reconnect-remote-desktop-error-the-specified-user-name-does-not-exist-verif/
3.) Failure to connect to uploaded VHD
When a VHD is uploaded to Windows Azure you must make sure that Remote Desktop is enabled on the VHD and an apporopriate firewall rule is enabled on the VM to open port 3389 (Remote Desktop port).
Hope this helps!
Regards.
Vivian Wang
TechNet Community Support