failed to reconnect to your remote session

FAILED TO RECONNECT TO YOUR REMOTE SESSION WINDOWS

In case the internet connection does not seem to work, check your IP configuration on Command Prompt with the following command. Find the server’s public IP address on your UpCloud Control Panel under Network and Public Network.

FAILED TO RECONNECT TO YOUR REMOTE SESSION WINDOWS

If you enabled the echo requests from Windows Firewall, you can also attempt to ping your server from your own computer. Open the Command Prompt and type cmd in the start menu search. Test the internet connection on your server to make sure all your network resources work as they should. Find out more about the UpCloud firewall at the tutorials. If you have set the default incoming rule to reject, remember to add a rule to permit traffic to the port Remoter Desktop server is listening to, 3389 by default. When you are certain that the Windows Firewall allows Remote Desktop connections, also check the server specific firewall settings at your UpCloud control panel. Press F to find the rules, called File and Printer Sharing (Echo Request - ICMPv4 - In) and v6 for both IP versions. Optionally while at the firewall settings, you may wish to enable ICMP for ping. With 2012 Windows Servers the rules are split between Domain and Private, or Public profiles as well as TCP and UDP protocols, which translates to 4 separate Remote Desktop - User Mode rules, all of which would usually be enabled. Both of these would in most cases be enabled as long as the server still uses the standard 3389 TCP port for RDP connections. Windows Server 2008 should show two rules: Remote Desktop (TCP-In) and Remote Desktop - RemoteFX (TCP-In).

Move to the Inbound Rules list and scroll down to Remote Desktop rules by pressing R. Open the Windows Firewall with Advanced Security by searching for “firewall” in the start menu. The Windows Firewall might be a little restrictive at times, for example, inbound ICMP protocol that ping connections use are disabled by default.

If you were trying to connect with user credentials that do not have admin rights, add the username you wish to connect with to the list of allowed users. All normal users must be added to this list. All users with administrator access are automatically permitted to connect. While still at the RDP settings, check the allowed users by clicking the Select Users or by pressing S. You can find more information about Network Level Authentication at Microsoft’s TechNet. If your server was set to allow remote control with Network Level Authentication, make sure your own computer supports this or select to allow any connection. The Remote Desktop needs to allow connections from other computers for the feature to work. The easiest way to get to the option is to open sysdm.cpl by searching for it on the start menu. When you are logged in and the server seems to be working, but Remote Desktop still cannot connect, make sure a remote connection is allowed. If it does not react to commands you might have to restart your server. If the connection shows something other than the lock screen, try if the server seems responsive. Sign into your server with an account that has administrator privileges to continue troubleshooting. Once you’ve connected to your server, through either of the methods mentioned above, you should be greeted by Windows lock screen. Try UpCloud for free! Deploy a server in just 45 seconds Problems connectingĮven while you might have trouble connecting using Windows Remote Desktop, you should always be able to log in to the web console at your UpCloud control panel, or by VNC connection, which settings are at your server details.

This troubleshooting guide aims to help rule out some of the most common causes for poor functionality. If you have problems using Remote Desktop (RDP) with your Windows server, there are a couple of things you can fix.

Failed to reconnect to your remote session