4

We have a Windows Server on Azure, running flawless in the past year. After a Microsoft scheduled reboot/advisor recommendation, we lost access to this VM.

  • 'Connect' (RDP) button on Azure portal does not work.
  • Already tried resetting NIC, adding new NIC, redeploying to new host, everything without success.

  • Boot Diagnostics shows that VM started, but connection icon on lower right is at disconnected state: enter image description here

  • Pinging from another VM on the same vnet also failed.

Is there anything else that we can try to do to restore access to this VM?

rcmadruga
  • 141
  • 1
  • 3
  • It probably has a new IP address. Did you already account for that in your attempts to connect? – Todd Wilcox Jan 09 '18 at 15:36
  • @ToddWilcox, tried several new public IPs, setting local ip to static, reverting back to dynamic. No luck also. – rcmadruga Jan 09 '18 at 18:26
  • When you added the new NIC, did you make note of the IP address and then tried to RDP to that specific address? If not, try again. Allow that NIC thru the Azure firewall. Provided that your internal Windows firewall is not overly protective ... If that does not work, contact Microsoft support. The screenshot shows that the network is down in your VM. Is the Connect button grayed out or just does nothing? – John Hanley Jan 17 '18 at 00:32
  • Also, make sure that the IP address is actually a public IP address. If not then assign one to the NIC. – John Hanley Jan 17 '18 at 00:33
  • @JohnHanley, added new NIC and added public IP address. The Connect button is enabled. RDP to this public IP results in error as the server was offline. The network down on screenshot may be the issue... Even with two NICs it is offline on boot diagnostics. – rcmadruga Jan 19 '18 at 12:36
  • Time to open a Microsoft support ticket. – John Hanley Jan 19 '18 at 18:26
  • have you configured the public IP properly and do you have any vnet? Looks like a problem with NIC or firewall restriction. If its not solving keep the storage and flash the OS to the VM once again – Srinivas Ramakrishna Oct 04 '21 at 01:21

3 Answers3

0

I had the same issue. I did the following to resolve it.

  1. Login via serial console (instructions below).
  2. At the command prompt, within the guest vm: ipconfig /renew

Logging into serial:

  1. At the serial console type cmd and then enter
  2. Type ch -si 1 and then enter.
  3. Login using the domain admin account or local admin account
  4. ipconfig /release
Swisstone
  • 6,725
  • 7
  • 22
  • 32
Rana Banerjee
  • 1
0

You may have already tried this, but stop the VM, so it shows up as de-allocated, then start it again. If that does not work then you need to raise a support ticket with MS to have them look at it.

Sam Cogan
  • 38,736
  • 6
  • 78
  • 114
0

For the benefit of searchers, I had an issue where my RDP details (I'd saved the details locally) stopped working after a stop/start/reboot.

The problem was the IP address of the VM had changed!

Because I'd saved the details of my RDP, any new downloads of the RDP file didn't bring in the new IP address for some reason.

In the 'Overview' section of the VM on the Azure Portal, check the IP address. If you open the RDP file in notepad, you can see the IP it's trying to use. In my case, they were different (though that file had definitely worked before!).

Instead of using the downloaded RDP file, from my PC I did:

  1. Start > "Remote Desktop"
  2. Enter the new IP (from the overview section in Azure) followed by a colon, followed by the port e.g. 168.xx.xx.xxx:3389
  3. Hit Connect. (If you get asked for a username/password, you've found the server.)
  4. Go to More choices > Use a different account
  5. Enter .\myusername, then the password in the password box.
JsAndDotNet
  • 181
  • 1
  • 8