Hello this workaround works for most Windows Server
Changing Security of RDP in Group Policy Editor
Go to the Start Menu, search for Local Group Policy and open up ‘Edit group policy’.
Navigate to the following directory:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
On the right-hand side, locate the ‘Require use of specific security layer for remote (RDP) connections’ and double-click it to edit it.
If it is set to ‘Not configured’, select Enabled and then in front of Security Layer, choose RDP.
Click Apply and then hit OK.
Restart your system so that the changes take effect.
Try connecting again.
For more options click here
Denial of Service attacks on port 3389 (RDP) can also cause this issue. Just had to block request on a public webserver which had thousands of records revealing external entities attacking that port. After about 5 minutes of blocking external access to that port the internal network access worked.
ReplyDeleteNickolaiMcghie-7555
Indeed, since none of the suggestions above worked for me, I took a look in the event viewer. It appeared there were thousands and thousands of failed login attempts. The event viewer won't show the external IPs, so I used a port monitor for that. It's very unfortunate that RDP does not offer a block after N failed attempts, though there are 3rd party programs that can do this for you. Eventually I got rid of the hack-attempts by changing the RDP port number in the registry.
ReplyDelete//Daniel
Hi, I find reading this article a joy. It is extremely helpful and interesting and very much looking forward to reading more of your work.. hacker for Hire
ReplyDeleteThanks for posting this info. I just want to let you know that I just check out your site and I find it very interesting and informative. I can't wait to read lots of your posts. hacker for Hire
ReplyDelete