Azure VM正在运行但不可用 [英] Azure VM Running but not available

问题描述

VM BARED-DB原为由于Service Pack安装而重新启动。一旦重新启动并且运行无法远程访问。计算机已停止并从Azure控制台启动
但仍无法访问RDP。  我们已经重新部署了虚拟机，但问题仍然存在。 
即使从AC服务器也无法联系。在控制台中可以看到正在运行但不可用。你能给我们一些帮助吗？

解决方案

我建议你做以下调试：

1。确保没有本地防火墙阻止入站tcp 3389流

2。确保没有NSG规则阻止tcp 3389流程

3。确保您的客户端位于相同的VM Vnet或对等的Vnet位置

4。在本地检查您的服务器正在侦听tcp 3389，cmdlet：  New-Object Net.Sockets.TcpClient（

CurrentComputer， 3389）

The VM BARED-DB was restarted because of Service Pack installation. Once it restart and running was not able to access remotely. The Machine was Stop and start from the Azure Console but still not accessible RDP.  We already Redeploy the VM and still the same issue.  Even from the AC Server it cannot be contacted. In the console can be seen Running but not available. Could you give us some help about it?

解决方案

I would suggest you to do the following to debug :

1. Ensure that no local firewall is blocking inbound tcp 3389 flows

2. Ensure that no NSG rule is blocking tcp 3389 flows

3. Ensure that you client is in the same VM Vnet or in a peered Vnet location

4. Check locally that your servers is listening on tcp 3389 , cmdlet : New-Object Net.Sockets.TcpClient(

CurrentComputer, 3389)

这篇关于Azure VM正在运行但不可用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！