How can adding a server to a domain cause Remote Desktop to stop working?
- by Adrian Grigore
I have two dedicated with Windows 2008 R2 servers which I am using for Web hosting. One Server A is a domain controller, Server B should simply be added to the domain controlled by Server A.
So I RDP'd into Server B and changed the system settings so that Server B is part of that domain. I entered my domain admin credentials, was welcomed to the domain and asked to reboot the server. So far everything seemed to work smoothly
After rebooting, I could not open an RDP connection to Server B anymore:
Remote Desktop can’t connect to the
remote computer for one of these
reasons:
1) Remote access to the server is not
enabled 2) The remote computer is
turned off 3) The remote computer is
not available on the network
Make sure the remote computer is
turned on and connected to the
network, and that remote access is
enabled.
I restored an older backup of Server B and switched off the firewall before adding the server to my domain. But the problem reoccurred just the same.
What could be the reason for this? The domain is brandnew and I did not change any of the default settings. Could this be some kind of domain-wide default policy that shuts down RDP on any domain clients? Or perhaps it has to do with the fact that Server B is virtual?
Thanks for your help,
Adrian
