I have a server with 1and1 and they have given up trying to restore RDP access (not trying at all) and told me to re-image the server. As this is a production machine, I'd like to avoid this since it would involve a slow FTP restoration, and I'm not sure it would actually fix the problem.
The machine was rebooted, lost RDP connection with existing credentials. I managed to get access to the command prompt on the remote server as the adminastrator by following these directions: http://help.1and1.com/servers-c37684/windows-server-c39510/system-recovery-c76208/resolving-a-failed-connection-to-remote-desktop-a627381.html
Now, I've terminated the firewall and the ipsec process. Still no dice. What can I do with CMD.exe to
1) diagnose the situation (is it windows, or a network issue)
2) possibly remedy the loss of RDP connection
- Windows Server 2012
- Sites are running (IIS/W3P is fine)
- Terminal Services is running
- Firewall disabled
- Ipsec disabled
- No network firewall (disabled in hosting control panel for now)
- Can ping from current location (worked fine before reboot)
- Not sure about the domain-specific network setup internally...
Added the registry values to make sure remote connections are enabled: http://expertpandas.com/blog/index.php/enabledisable-rdp-using-command-prompt-for-windows-2012/
Also found this: But I'm not sure how to set the startup policy with CMD... http://www.techrepublic.com/forums/questions/remote-desktop-does-not-connect-after-a-restart/