I have created one virtual machine on azure windows 2012 datacenter.
I am not able to take remote while clicking on RDP file it gives error
Remote access to server not enable
Remote computer is turned off
Remote computer is not available on the network
You need to enable RDP inbound in 2 places:
1) the Azure Network Security Group (assuming you created the VM as an Azure Resource Manager VM instead of a "classic" VM), and
2) the firewall on the VM itself.
Related
I created a Server 2019 VM in Azure and want to use nested virtualization. On the 2019 VM, I created a Windows 10 VM in Hyper-V. The problem is that the Windows 10 VM does not have internet connection. Even though a virtual switch was created on the 2019 VM, the nested Windows 10 VM is not able to reach the Azure gateway.
Here's the Server 2019 Network settings
This is the Hyper-V Switch
And finally this is the Windows 10 VM network settings. It never gets an IP address from the host and even when assigned a static IP it cannot route to the gateway. What am I missing?
The overall problem I'm trying to solve is to have Apache Guacamole able to connect to nested VMs, which isn't possible with NATing.
You cannot reach the internet because your default gateway is blank.
You are getting auto configured IP addresses without default gateway (169....) (probably) because you do not have a DHCP server.
You can configure the DHCP server on the Hyper-V host running in Azure
or on a nested Hyper-V VM if needed.
see: https://www.nakivo.com/blog/hyper-v-nested-virtualization-on-azure-complete-guide/
Going through exercises of Fundamentals of Azure, we(me and my team) are unable to connect via our Windows 10 desktops to RDP 3389.
Attached screen-shot.
Test connections outbound of RDP on the portal work as expected. Connection is successful.
But via clicking "Connect" from the dowloaded RDP file we get this error.
There is section to setup Linux VM via windows; currently exploring that but we see little hope.
There can be various reasons that RDP to Azure VM can fail.
Please check Troubleshoot Remote Desktop connections to an Azure virtual machine section if this helps.
If you just created a new VM in Azure it might be a firewall restriction that is causing the error. You can check if the RDP port 3389 be allowed from your client IP address in the network security group.
While performing ASR migration from VMWare Vsphere VMs to azure portal, I have reached till creating a protection group step in azure portal.
The configuration server, master target, process server and Vcenter Host server are all up and running in azure and are shown as "Healthy" and in sync.
But while adding the on premise VMWare Virtual Machines to the protection group, its showing their IP addresses as invalid. Also mobility service is installed on the VMs (manually), still it is showing in the portal as not installed.
My Network reference:
Azure IP Range: 10.99.18.0/24
On-Prem VMware VM's: 10.209.113.0/24
Connection from On-Prem to Azure is VPN/express route.
both end-to-end are able to connect each other.
The IPs of the VMs are now public and outside any firewall.
Error Screenshot from Azure ASR:
Install the VMWare tools by downloading them local on the vm or network drive. Once installed it will ask for restart. Wait for replication to take effect for about 15 min minimum with enhanced version. Now you should not see any error.
Regards
Ravichander Pinnaca
I have created virtual machine in Azure cloud and connected to it using remote desktop, installed IIS in it and copy pasted XAP file from my desktop to remote and configured in IIS, i can able to browse application in remote but it cannot be accessed in my local desktop or out of remote, any ideas would be appreciated..
Tnx..
Remote Desktop cannot route network traffic to your VM.
In your case I would suggest you to use a Point-to-Site (P2S) connection to access your website.
For that reason you have to create a virtual network in Azure, deploy your VM into that virtual network and use P2S to connect to your virtual network via VPN. After that you can access your VM's webserver from your local computer.
Here you find a step-by-step guide how to do this: https://azure.microsoft.com/en-us/documentation/articles/vpn-gateway-point-to-site-create/
By the way, you cannot move an existing VM into a virtual network. But there is a very easy workaround. Delete your VM, but DO NOT delete the associated disks or VHDs. Then create a new VM and select in the creation wizard to use an existing disk. There you select the disk from your just deleted VM.
I created a VM on Windows Azure. My actions
1) "File and Printer Sharing (Echo Request - ICMPv4-In)" set On
2) Windows Wirewall set Off
It still does not ping.
UPD: The network is working properly.
What do you mean by not pinged?
ICMP as protocol is disabled/blocked at Azure LoadBalancer level. So no matter what you do in your VM, you will never get ICMP traffic from the Internet inside the VM. The only way to get ISMP traffic into a VM is via Azure Virtual Network, and Azure Connect and from a valid joined computer.
Your actions (1) and (2) will help you get ICMP traffic from either:
Another Virtual Machine in the same Cloud Service
Another Virtual Machine in the same Virtual Network
Your computer, if it is part of the same Virtual Network
Your Computer if it and the target VM are in the same Group from Windows Azure Connect
** UPDATE **
After clarifying the question, you still will never be able to successfully execute ping whatever.cloudapp.net. In order to "make visible iis site", you need to add an Endpoint to your VM from the portal or the Management API for the port you need. In your case - port 80.