Sometimes I cannot RDP to my virtual machine after creating a new Domain Controller

Question

Here is my scenario, I originally had 1 single Domain Controller that is running Windows Server 2016 in my internal environment. I didn't want to upgrade the server to 2022 as I have had issues trying to update old servers so I created a brand new DC to act as a secondary domain controller and once it was all configured, I would transfer the roles to make it Primary.

I completed all that and the 2022 server is supposed to be Primary. When I shutdown the old Primary, I could not RDP to any of my servers, I turned old server back on and it works. Now sometimes I get an issue after a virtual machine has been reboot, I cannot connect to it by RDP. It gives me error the credentials that were used to connect to did not work but I know they work as I can connect to the server from the Hyper-V console.

After sometime, I can connect with no issues. If I connect by the IP address, it works with no issues. After sometime it seems to work again. It's very frustrating, I want to get rid of the old 2016 virtual machine and just have the 2022 server running. Why does this happen and how can I fix it?

Answer 1

Hello,

If you can connect using an IP address, there might be an issue with your DNS server. It's advisable to check your DNS settings.

---

If the Answer is helpful, please click "Accept Answer" and upvote it.