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
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.
Latest posts by Shishir Chandrawat (see all)
- Exchange 2010 Std: Mailbox server has reached the maximum database limit of 5 Error RcrExceedDbLimitException - December 12, 2016
- Exchange 2010: Unable to add Mailbox Database copies on DAG member servers, Error: An error occurred while processing a request on server - December 12, 2016
- Unable to Mount Microsoft Exchange DAG Database, Error: Failed to determine the mount status of the active database copy - December 12, 2016