We had a 2012 server which was configured as a terminal server and it was working well, one fine day we found that we were not able to RDP into it with the usual three reason error box. We validated that remote desktop was enabled on the server and the windows firewall did have the rule in place to allow Port 3389, still the RDP wasn’t working fine.

Further investigation revealed that client executed Security configuration wizard on the server after which this RDP stopped working

Solution

To resolve the issue, we reran the Security Configuration Wizard during which we added a windows firewall rule to allow communication on Port 3389, remote port can be anything but we did set it as 3389 as well.

In Security Configuration Wizard add a Windows Firewall rule to allow connection to Local Port number 3389 and Remote port to be any port even though the port number 3389 is already unblocked in the Windows Firewall.

Feel free to report any new issues or problems on forum to seek expert help.

The following two tabs change content below.
An automobile enthusiast at heart and computer geek by profession, started my Career with MS in 2005.Left Jobs and started Pledge Technologies (the parent company to Grishbi) back in 2009.We have been providing IT consulting to various Small and Medium businesses across US and UK since then.Our company specialises in Microsoft Server technologies like AD, Exchange, the rest and with numerous Office 365 migrations under our belt, we quite an expert with that too. Whatever we learn in our day to day life, we share it back on Grishbi as a Thank for all the love and support our customers have given us.
%d bloggers like this: