Windows 7 remote desktop encryption error every few minutes

Question

Because of an error in data encryption, this session will now end.

This is the error I've been getting more and more frequently over the past few days, to the point that I can't ignore it because it's happening consistently within 5 minutes of connecting - sometimes within a few seconds. Both the remote and local machines are Windows 7 Pro x64. The remote machine is behind a Linksys RV082, and I'm using UPnP to forward a remote port to the correct local port. This setup had been working fine for several months, and I can't think of any recent relevant changes that might have been made.

Things I've already tried:

• Disabling unnecessary components of the network connection on the remote machine, until only IPv4 and Client for Microsoft Networks remain.
• Disabling TCP large send offload on both the remote and local machines.
• Confirming that the remote machine is not mentioned anywhere in any DMZ settings on the Linksys router.
• Confirming that there are no x509-related registry keys screwing things up (this is the suggested fix for a slightly different error anyway).

These are the only solutions I've been able to find after about an hour of searching, and most of them apply to XP or Server 2003 in any case. If anyone could suggest something else, it would be much appreciated.

Answer 1

I have been researching this as well and I feel like I went down the same road is you since every fix applies to vista/xp. However on Microsoft Technet I found someone who fixed this by deleting the certificate then reconnecting:

I just came across this error myself. I was attempting to remote desktop in from one XP machine >to another. To fix, I went into the Registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters

After exporting this for safekeeping, I deleted the Certificate keys. I restarted the target PC >and was able to successfully connect. I can only surmise that the problem is a corrupted >certificate or something. Deleting the certificate stored in the registry seems to have reset it. >The certificate key is different from the previous one, so maybe the target PC's certificate >expired?

Mostly just guesswork here, but this solution worked for me!

It may not be a definitive fix since this issue seems so random because it worked for months before now but I figured it's worth a shot for you to try.

Source

Update

Try deleting the string value for the machine you are trying to connect to under:HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default

Let me know how it goes I'll check back when I get to my hotel after dinner.