My VM became unconnectable after i did a static IP on network adapter

Mei XIAO 0 Reputation points
2025-03-03T13:34:38.42+00:00

I was able to connect to my VM when i signed up. But after I configured VM for my domain setup by adding my Public IP as my static Ip in my network adapter, I am not able to connect to my VM. Every time i tried to connect, REmote Desktop Connection would say "can't connect to the remote computer for one of these reasons:

  1. Romote access to the server is not enable
  2. the remote computer if off
  3. The remote computer is not available on the network" Can you help me with it?
Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,846 questions
{count} votes

1 answer

Sort by: Most helpful
  1. TP 125.9K Reputation points Volunteer Moderator
    2025-03-03T13:41:20.1866667+00:00

    Hi,

    Inside of your VM, it should always use private IP, assigned via DHCP in majority of cases. If you need the private IP to be static you set this on the Azure network interface. This is how Azure networking works.

    You associate the public IP address with the Azure network interface.

    Associate a public IP address to a virtual machine

    https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/associate-public-ip-address-vm?tabs=azure-portal

    Are you using Azure Virtual Desktop (AVD) service? Generally you don't assign public IP address to a VM that is used for AVD, but you may have some sort of special requirement.

    Please click Accept Answer and upvote if the above was helpful.

    Thanks.

    -TP


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.