Remote Desktop Connection Does Not Work

For Windows Dedicated Servers acquired before 28-10-2018, Server Power Deals, and Value Dedicated Servers

Learn what you can do if your remote desktop connection does not work.

There can be several reasons why a remote desktop connection fails. Most of the time the server is either shut down or has not booted properly. If the connection is still not established after a few minutes, a problem with the network configuration or the firewall may be the cause.

• Log in to the serial console.

• Open a new command prompt channel and log in as an administrator or as a user with administrator rights.

• Try to access an IP address or domain outside your server. You can test this with ping google.com.

  C:\Windows\system32>ping google.com
  
  Ping is performed for google.com [2a00:1450:4001:800::1004] with 32 bytes of data:
  Response from 2a00:1450:4001:800::1004: Time=3ms
  Response from 2a00:1450:4001:800::1004: Time=3ms
  Response from 2a00:1450:4001:800::1004: Time=3ms
  Response from 2a00:1450:4001:800::1004: Time=3ms
  
  Ping statistics for 2a00:1450:4001:800::1004:
  packets: Sent = 4, Received = 4, Lost = 0
  (0% loss),
  Approximate times in milliseconds:
  Minimum = 3ms, Maximum = 3ms, Average = 3ms
  
  C:\Windows\system32>

• If ping works, a firewall or Windows service is likely to block the remote desktop connection. Enter net start | more to display the running services. You can press ENTER to move line-by-line or SPACE page-by-page. If IPSec or the Windows Firewall is running on your server, it is possible that they are blocking the remote desktop connection.

  Ping is executed for google.com [2a00:1450:4001:800::1004] with 32 bytes of data:
  Response from 2a00:1450:4001:800::1004: Time=3ms
  Response from 2a00:1450:4001:800::1004: Time=3ms
  Response from 2a00:1450:4001:800::1004: Time=3ms
  Response from 2a00:1450:4001:800::1004: Time=3ms
  
  Ping statistics for 2a00:1450:4001:800::1004:
  Packets: Sent = 4, Received = 4, Lost = 0
  (0% loss),
  Approximate time in milliseconds.:
  Minimum = 3ms, Maximum = 3ms, Average = 3ms
  
  C:\Windows\system32>net start | more

  The following Windows services are started:
  
  Connection redirection for remote desktop service in user mode
  Application host help service
  Application management
  Workstation service
  Task scheduling
  Basic filter module
  System event notification service
  User profile service
  COM+ event system
  DCOM server process start
  DHCP-Client
  Diagnostic Policy Service
  Distributed Transaction Coordinator
  DNS Client
  Print Queue
  Group Policy Client
  Special Management Console utility
  IKE and AuthIP IPsec Key Creation Modules
  IP Help Service
  IPsec Policy Agent
  Remote Desktop Configuration
  --Continuation --

• At the netsh advfirewall set allprofiles command prompt, type state off to disable the Windows firewall (you can use state on to enable it again later).

  Microsoft Windows [Version 6.1.7601]
  Copyright (c) 2009 Microsoft Corporation. All rights reserved.
  
  C:\Windows\system32>netsh advfirewall set allprofiles state off
  OK.
  
  C:\Windows\system32>

• You will see an OK on the screen when the firewall is disabled. Then test the remote desktop connection. If you are still unable to connect, continue with the next steps.

• Disable IPSec by entering the following command:

Test the Remote Desktop connection again. If you are still not able to connect, investigate whether or not the following may apply to you:

• You have multiple IP addresses for your server and are trying to log in via remote desktop with an IP address that is not yet set up.

• You may have another software firewall installed that is blocking the connection.

• The external IONOS firewall may be blocking the connection.

• Terminal services, or other services that the Remote Desktop requires, may not have started correctly.