Unable to RDP to a classic VM after DNS change

Ori Gilgun 61 Reputation points
2020-09-07T15:09:37.8+00:00

So I changed my VM's DNS settings and now I cannot remote it.
It is a Domain Controller. I changed the DNS so it points to the other DC as the primary DNS server instead of itself, I clicked OK and got disconnected for good.

It is a classic VM, it had no endpoints but RDP worked. I created a new endpoint for RDP but still I cannot connect.

No idea what else to do, please help :[

Ori.

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
9,044 questions
{count} votes

1 answer

Sort by: Most helpful
  1. whoward-msft 2,771 Reputation points
    2020-09-08T19:29:11.817+00:00

    Hi @Ori Gilgun ,

    After you created a new endpoint can you verify the default port for RDP is open The default TCP port is 3389. A rule to permit RDP traffic may not be created automatically when you create your VM. You can do this by selecting your VM in the Azure portal. Then clicking the Endpoints button to view the endpoints currently configured for your VM. Verify that endpoints exist that allow RDP traffic on TCP port 3389.

    Since you are having trouble using RDP to connect your VM I'd advise you to take a look at this doc here. That doc goes over the best troubleshooting tips to get back into your VM after being unable to do so.

    Hope this helps!

    If this answer helped you solve your issue, please mark this answer as accepted to help others in the community with similar issues.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.