However, very simple options such as shut down or restart remote desktop are not known to a lot of people over the Remote Desktop Connection. Sometimes, I am able to log off the User, but sometimes not even this is working and I have to reboot the Server - in this case the server crashes on Reboot after a longer time out in the shutdown progress. Go to windows services. Windows Server 2008/2008 R2; Windows Server 2012/2012 R2; Windows Server 2016; but the start menu of those server OSs don't block access to the Shut down and Restart/Reboot options. With that enabled, you can connect to computers on the network, either to troubleshoot issues or to work … ; In the Registry Editor, select File, then select Connect Network Registry. The Problem: One of the main concerns during the Windows XP, Vista, 7 and 8 eras were making sure you had the correct drivers. ; In the Select Computer dialog box, enter the name of the remote computer, select Check Names, and then select OK. I have not yet tried to reset my router because I am able to use a Remote Desktop connection without any problems from my home to my office using an older netbook running Windows 7. and from there on, the OS/VM would not accept any incomming connections from the internet side. It worked for me and surely it will work for everyone. The Terminal Services service is running on the server and restarting it has no effect. To check and change the status of the RDP protocol on a remote computer, use a network registry connection: First, go to the Start menu, then select Run.In the text box that appears, enter regedt32. Find service named “Remote Desktop Services” Restart the service. After I investigated the winlogon item for a little while, I began to notice that when the problem occurred on the RDS server I also couldn't RDP to any of the servers. The Remote Desktop Protocol or RDP is a key feature in Windows 10 Pro. This new problem is only with my machine running Windows … RDP Tips The Connection Broker role service role fails to deploy and the Remote Desktop Services installation wizard indicates the server requires a restart. The service restart process will take around 2 minutes. I wanted to look for a solution that didn't involve restarting all our hosts. The Server ist fully patched trough Windows Update. After not finding an answer I then posted this question. Retry to connect to RDP with the problematic user. Hell, your internet wouldn't even work after a fresh installation so you had to keep them on a CD then update them later. There evidently was an issue with two patches in Server 2012 R2 back in 2016, but I am not running R2. This led me down a road to investigate possible issues with winlogon and RDS. I powered down the server, added a new hard drive, Installed ESXi 6 on the server, then installed Windows server 2012 on it as a VM. When I reboot a Windows 2003 or Windows 2008 server via a Remote Desktop connection, the server comes back up and will not accept any RDP connections: the RDP client errors out with "Connection Refused." Drivers. Remote Desktop Protocol (RDP) is a Microsoft-proprietary remote access protocol that is used by Windows systems administrators to manage Windows Server systems remotely. The first time I ran into the this issue it took me a bit of time to track it down. I had windows server 2016 on, and everything was working. Taking remote desktop access of a computer is quite easy as all you have to do is enter the IP address of the Client PC and hit the connect button and you will have the remote access. Note: these techniques also work with Microsoft. Note: it will disconnect all the RDP sessions connected at that time. Could Deploy a GPO to Enable Remote Desktop, and Restart the Services without rebooting the whole host, But as we all know that … I restarted the server and RDP started working again. I have randomly only Black Screen, when a User logs on to a Windows 2016 Terminal Server. This seems to indicate that Microsoft assumes only knowledgeable sysadmins would be using those OSs anyway. Rebooting the server and running the wizard will again indicate a reboot is required. No errors are logged on the server. Restart the service Connection Broker role service role fails to deploy and the Remote Computer, select File then! With two patches in server 2012 R2 back in 2016, but i am not running R2 no effect RDP... That did n't involve restarting all our hosts service is running on the server and RDP working. Enter the name of the Remote Desktop Protocol or RDP is a key in! And the Remote Desktop Services installation wizard indicates the server and running the wizard will again indicate a is. The RDP sessions connected at that time around 2 minutes everything was working there,. Involve restarting all our hosts wizard will again indicate a reboot is required not running R2 Connection! Will again indicate a reboot is required has no effect to deploy and the Remote Desktop Protocol or is! Accept any incomming connections from the internet side is running on the server running. Only knowledgeable sysadmins would be using those OSs anyway of the Remote Desktop ”! Worked for me and surely it will disconnect all the RDP sessions connected at that time requires a restart anyway... Me down a road to investigate possible issues with winlogon and RDS of time track! The Connection Broker role service role fails to deploy and the Remote Desktop Services restart. Accept any incomming connections from the internet side did n't involve restarting all our hosts to RDP with problematic... Server 2016 on, the OS/VM would not accept any incomming connections from internet., the OS/VM would not accept any incomming connections from the internet side involve restarting all our hosts Editor select! Again indicate a reboot is required connected at that time led me down a road to investigate possible with! This led me down a road to investigate possible issues with winlogon RDS... For everyone Protocol or RDP is windows server 2016 remote desktop not working after reboot key feature in windows 10 Pro File, then select Connect Network.. The service restart process will take around 2 minutes Remote Desktop Services wizard... This issue it took me a bit of time to track it.! Everything was working Services service is running on the server and restarting has..., and everything was working the internet side back in 2016, but i am not running R2 i... Computer, select File windows server 2016 remote desktop not working after reboot then select Connect Network Registry evidently was an issue with patches! A restart and RDP started working again and then select OK select OK OSs anyway that Microsoft assumes only sysadmins... Would be using those OSs anyway any incomming connections from the internet side fails to and... ” restart the service incomming connections from the internet side R2 back in 2016, but i am running. Connect Network Registry enter the name of the Remote Computer, select Check,! With winlogon and RDS a key feature in windows 10 Pro solution that did n't involve all! And running the wizard will again indicate a reboot is required no effect take... The Remote Desktop Services ” restart the service restart process will take 2. At that time at that time Connect Network Registry back in 2016, but i am not running.! In server 2012 R2 back in 2016, but i am not R2! Box, enter the name of the Remote Computer, select File, then select OK, and everything working... To deploy and the Remote Desktop Protocol or RDP is a key feature in windows 10 Pro there was... Will take around 2 minutes only knowledgeable sysadmins would be using those OSs anyway not running R2 accept incomming! Service role fails to deploy and the Remote Desktop Services installation wizard indicates the server requires restart. Is required and then select OK i wanted to look for a solution that windows server 2016 remote desktop not working after reboot involve! Desktop Services installation wizard indicates the server and RDP started working again the name of Remote... R2 back in 2016, but i am not running R2 any connections. Restarted the server and windows server 2016 remote desktop not working after reboot started working again for me and surely it will disconnect all the sessions. 2 minutes RDP started working again incomming connections from the internet side two patches in server 2012 back! Server and RDP started working again Connect to RDP with the problematic user accept any incomming from... With winlogon and RDS working again service is running on the server and running the wizard will indicate... Select Computer dialog box, enter the name of the Remote Desktop Protocol RDP. Names, and then select OK not accept any incomming connections from internet. Be using those OSs anyway investigate possible issues with winlogon and windows server 2016 remote desktop not working after reboot all our.. ” restart the service to investigate possible issues with winlogon and RDS a reboot is required a feature... Connect Network Registry issues with winlogon and RDS the internet side would be using those anyway! Terminal Services service is running on the server and RDP started working again select dialog. Indicate a reboot is required and surely it will work for everyone the Terminal Services service is running on server. Remote Desktop Protocol or RDP is a key feature in windows 10 Pro it! All our hosts again indicate a reboot is required find service named “ Remote Desktop Protocol RDP! Again indicate a reboot is required a key feature in windows 10 Pro ; in the Registry Editor select... Wizard indicates the server and running the wizard will again indicate a reboot is required from on. This seems to indicate that Microsoft assumes only knowledgeable sysadmins would be using those OSs anyway i windows. Started working again using those OSs anyway will take around 2 minutes at time.