Hey everyone! I set up an isolated network for some disaster recovery tests, complete with its own subscription and no peering. Within this network, I have a default subnet and a bastion subnet, along with a specific NSG for the default subnet. I restored a virtual machine (vm1) to this setup yesterday, and while I can see that it's up and running, I'm struggling to connect to it using Bastion. As a test, I created another VM (vm2) in the same subnet, and I can connect to that one via Bastion without any issues. I can also ping vm1 from vm2. However, when I try to log into vm1, I get an error saying, "the target machine is either unreachable/unavailable or your username/password is not correct." I've already tried resetting the username/password and redeploying the VM, but nothing seems to work. Any advice on how to move forward would be greatly appreciated!
1 Answer
Have you tried accessing the VM through the serial console? It's a good way to get more insights. Also, check if the guest agent is running since it can affect connectivity.
I looked for the serial console option, but instead, I just got a health report for the VM, stating that the guest agent is installed and running. Everything in the report seems fine.