1and1 Help Centre Categories

print article

Resolve a Failed Connection to Remote Desktop

This article lists potential reasons for a failed Remote Desktop connection, as well as ways to resolve connectivity problems.

Remote Desktop may suddenly become unavailable for a number of reasons. The most common one being that the server has been shut down or not fully booted. Wait a few minutes and then try to connect via Remote Desktop again. If Remote Desktop has been unavailable for several minutes, a firewall or network configuration may be misconfigured. The following steps show how to resolve these problems.

Step 2
Create and log into a new command prompt channel as the administrator user.
Step 3
Ping another address such as google.com by typing ping google.com to ensure that outgoing connections are not being blocked. Ping google.com
Ping google.com
Step 4
If you do not receive a response, investigate your inaccessible Windows server. If you have received ping responses, it is likely that a firewall is blocking the Remote Desktop connection. Type net start | more and press ENTER to view the current services running on the machine. Access List of Current Running Services
Access List of Current Running Services

Use ENTER to read through the list line by line or press the SPACE bar to read page by page. If IPSec Policy Agent or the Windows Firewall service is running, these may be blocking the Remote Desktop Connection. List of Running Windows Services
List of Running Windows Services
Step 5
To disable the Windows Firewall, type netsh firewall set opmode disable. Request to Disable Firewall
Request to Disable Firewall
Step 6
The terminal will output Ok. If the firewall was successfully disabled, Test the Remote Desktop connection again. If still unable to connect, follow the next step. Firewall Disabled
Firewall Disabled
Step 7
To disable the IPSec Policy Agent, type net stop "ipsec policy agent" for Windows ServerĀ® 2003 or net stop "ipsec policy agent" for Windows ServerĀ® 2008 and press ENTER. Once the IPSec Policy Agent has stopped, test the Remote Desktop connection again. IPSEC Policy Agent was stopped successfully
IPSEC Policy Agent was stopped successfully
If you are still having problems connecting via Remote Desktop, there are other possible reasons:
  • You have multiple IPs and are trying to connect via an IP that has not been added to the server or a hostname that does not resolve to the correct IP address.
  • Another software firewall that was manually installed may be blocking the connection.
  • The external firewall configurable through the 1&1 Control Panel may be blocking the connection.
  • Terminal services or other services that Remote Desktop rely on may have failed to start.