Hello João,
We apologize for the inconvenience. We'll certainly look into this & help you.
To further investigate the root cause of this issue, we've sent you an email with detailed instructions to contact our additional support.
Please check your inbox/spam folders to find the email and use it to contact them at your convenient time.
Since the last two weeks, when we try to reach a PC from outside our office ( example: from home ), when start the RDP connection that we have configured, and after we complete to write the credentials to start the connection ( username and password ), we get a RDP error with the message "internal error".
On windows Logs of the computer that tries to connect whe can see the log error:
RDPClient_SSL: an error was found when making the transition from TsSslStateDisconnecting para TsSslStateDisconnected in response to TsSslEventStartHandshakeFailed (error code 0x80004005).
After several tests, if we disable on Remote Shield the option RDP Protection, the RDP connection can be made with no issues… but is not the correct workarround, because we want RDP Protection of course.
Before this last two weeks, there were no issues connecting with RDP, so we assume, that there was some update in AVG that make this error happens.
We have reinstalled AVG from scratch, our router is properly configured… the only thing that makes this error is the RDP Protection option on Remote Shield when its ON.
We also try the Remote Shield option Block all connections except this … but the result is the same, even when we activate this option and set a Public IP that we own ( my home ip - get it consulting whatismyip.com ), the RDP internal error happens.
Operating system of computer receiving RDP connections is Windows 7 PRO 64 bits ( fully patched )
Operating system of computer trying to connect throught RDP … i have already tested with Windows 7 PRO 64 bits ( fully patched ) and Windows 10 PRO 64 bits ( fully patched ).
I appreciate a quick answer, since this problem is not affecting only one computer… but three at this moment.
João Paulo Silva
Hello João,
We apologize for the inconvenience. We'll certainly look into this & help you.
To further investigate the root cause of this issue, we've sent you an email with detailed instructions to contact our additional support.
Please check your inbox/spam folders to find the email and use it to contact them at your convenient time.