I ran a repair install on a domain PC in my environment last week to correct an issue it was having. The users profile was also corrupt, so I created a new profile for him on the machine and transferred his file to it. I noticed this morning that I cannot RDP into his machine. As soon as I type the username and password via RDP on my machine, I get the error "Can't connect to remote computer". I searched high and low to find a solution and finally came about one. In the Event Viewer (on the remote machine) there was error 36888 (Source Schannel) in the System log. There were two of these errors generated every time I tried to connect. The first time I tried to connect after rebooting the remote machine I received error 56 (TermDD) in the System log, also. In the Security log, I received error 5061 (Microsoft Software Key Storage Provider) twice every time I tried to connect. To resolve the issue, I went into the Certificates console (for the Computer Account) and deleted the computer name certificate from the Remote Desktop certificates folder (after backing the certificate up for good measure). I then disabled Remote Desktop and re-enabled it (I don't know if this step is necessary, but I tried it, thinking it might regenerate the certificate). I then tried to connect from my remote machine, and it connected just fine. It appears that the certificate re-generated on the initial connect after I deleted the certificate. Problem solved! Hope this helps someone.Drew Green MCSA, CCENT, Security+, Network+, A+

Yes! This worked for me. I had a 2008 R2 server that had to have it's motherboard replaced. After that, I was no longer able to RDP to it. After digging in the logs I found the schannel error followed by a TermDD error and then the schannel error at the time of my attempted RDP session. I deleted the RDP cert (but did not have to disable/re-enable the RDP settings) re-booted the server and was then able to RDP into the system again. Thanks for posting.

Would it be possible to give a more step-by-step version of how you did this? I'm having the same problem with a PC in our domain. Thanks!