There are many reasons why a server may become inaccessible. If the sites on your server are still up however you are unable to reach the server via Remote Desktop, follow the instructions on Resolving a Failed Connection to Remote Desktop.
If your Web Sites are down, the server does not ping and the server is not reachable via Remote Desktop, either the server has been fully shut down, the server did not fully boot up (due to faulty configuration, corrupted files, file system, a check disk is in progress, etc), or there is simply a misconfiguration in the network adapter settings.
The following steps should help you gather more information about the server's current state.
Once connected, type the
command and press ENTER to reboot the machine.
You should stay connected to the Serial Console while the server reboots. If the server was in the process of a check disk, you will not have seen the progress when initially logging into the Serial Console but the check disk should resume when booting back up, allowing you to view the progress.
If you receive the EVENT: The CMD command is now available message but the server is still inaccessible, skip the next step, otherwise continue.
This will take you to the Windows Advanced Options Menu. Use the arrow keys on your keyboard to select Last Known Good Configuration (your most recent settings that worked) and press ENTER.
Wait for the EVENT: The CMD command is now available message to appear. If the message does not appear within 5-10 minutes, there is most likely a problem with the Operating System. You may continue to wait and check the currently running processes by using the t command and pressing ENTER periodically. If the server will not fully boot up or allow logins via command prompt, you will have no choice but to Reboot the Server into the Windows Rescue System and either try to repair the Operating System or back up your data and re-image the server.
If you receive a response, then the outgoing connections from your server are not being blocked however it is likely that a firewall is blocking incoming connections to your server. Double-check your external firewall rules set in the 1&1 Control Panel to confirm that the correct ports are open. Please reference: Resolving a Failed Connection to Remote Desktop for steps on how to disable Windows services that may be blocking the connection.
If you do not receive a response, proceed to the next step.
If you receive a message that No more data is available, it is likely that the network adapter has been disabled.
When the command prompt returns, type
The terminal should output Ok. and return to the command prompt. You should now be able to log into the server using the original IP that came with the server which can be found in the Server Access Data section of the 1&1 Control Panel.