Eskimo007
There’s a strong password on my PC…
That’s not enough, the issue in many cases are exploits that are leveraged to disrupt your system or bypass security.
My advice if you absolutely must do it is to set a local security policy to lock your account for a few minutes after 3 failed attempts and also whitelist the IP address range you’ll be attempting to access your system from, but even then it’s a horribly insecure mechanism to connect to a PC and no IT person would abide by that.
Here’s another tip though, let’s say your issue is with port translation or port redirection, like your router will forward ports but not redirect them to other ports… you can have terminal server listen on a different port to RDP into, or listen on an additional port.
Export this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
Change .reg file path at the end where it says RDP-Tcp-666 for example
then change the PortNumber to a port you want, it’s in hex so you need to convert it, 666 would be 29A so:
“PortNumber”=dword:0000029A
Then reimport your modified .reg file, reboot your PC, and your Remote Desktop will be accessible on this new 666 port or whatever port you changed it to and you can try poking a hole in your router to forward to the IP address of this system on port 666.
Again, don’t recommend this on its own but it might help you anyhow.