I have created a couple of Virtual Networks on my Azure account. All of them have point-to-site connectivity enabled. But I dont have any connections actively connected to the network. When I go to the "configure" page for eahc of these networks in the management portal, I see a message sayingthe network is in use and I am unable to delete these networks.
Why does this happen? How can I delete these networks?
Apparently you also have created Gateways for these networks. You have to delete the gateway for the network first, before you are able to delete the network.
This particular part of online documentation describes how to delete a Virtual Network Gateway.
The gateway and the virtual machines attached to the availability set. When you delete the virtual machine but don't delete the disk, you can restore it again.
Related
I have Two Azure VMs which has been created for about 6 months now. The VMs are in use by different members of the same project teams, now I want to know how I can network the VMs together (for direct transfer of large files) without having to delete and recreate them.
#faruq bello If the VMs are in the same Virtual Network you should be able connect them without any additional configuration, if not please check the NSG rules or firewall on the VMs to see if it is blocking any connectivity.
If they are not in the same virtual network I think you can establish connectivity by using Virtual network peering in this scenario. If the VMs are in the same Azure region you can use Virtual network peering and across Azure region you can use Global virtual network peering. Please be aware of constraints for globally peered virtual networks.
I am unable to access Blob Service from Azure Virtual Machines running in the same region. I have created a storage account and planned to access to selected IP addresses i.e. MY Laptop, My Office PC and My Virtual Machine which is running is Azure. After whitelisting 3 of the IP's I am able to access the Blob Service from MY Laptop and MY Office PC but unable to access the same of Virtual Machine which is running in Azure.
Pl. let me know if anyone is facing similar issues and the resolution. Thanks in Advance.
Check the NSG the VM belongs to and see if you are allowing the VM to communicate outbound, if so check if Azure storage is allowing incoming connections from the network to which the VM is connected to.
Your VM uses the internal network to attempt to access the Storage so adding the public IP won't work and you can't use internal IP's.
The easiest way would be adding the Virtual Network subnet of the VM to the firewall rules and add Azure.Storage as service endpoint to the subnet. If you add the subnet using the Azure Portal the service endpoint will be automatically added as well. Another way would be setting up a private endpoint.
I have to test the behavior of a SharePoint migration tool installed on my Azure VM when Internet connection is lost.
I access to this VM by RDP.
How can I cut off Internet connection of my VM and restore it later ?
Thanks in advance.
I second the suggestions posted by 4c74356b41, you could also disable the Network Adapter and then reset the Network adapter to restore the connection. If you wish to take this approach checkout these steps:
For VMs deployed in Resource group model
Go to the Azure portal.
Select the affected Virtual Machine.
Select Network Interfaces.
Select the Network Interface associated with your machine
Select IP configurations.
Select the IP.
If the Private IP assignment is not Static, change it to Static.
Change the IP address to another IP address that is available in the Subnet.
The virtual machine will restart to initialize the new NIC to the system.
Try to RDP to your machine. If successful, you can change the Private IP address back to the original if you would like. Otherwise, you can keep it.
Delete the unavailable NICs
After you can remote desktop to the machine, you must delete the old NICs to avoid the potential problem:
Open Device Manager.
Select View > Show hidden devices.
Select Network Adapters.
Check for the adapters named as "Microsoft Hyper-V Network Adapter".
You might see an unavailable adapter that is grayed out. Right-click the adapter and then select Uninstall.
Ref: https://learn.microsoft.com/en-us/azure/virtual-machines/windows/reset-network-interface
Create a deny internet outgoing rule on the network security group and attach it to the VM network adapter.
https://blogs.msdn.microsoft.com/igorpag/2016/05/14/azure-network-security-groups-nsg-best-practices-and-lessons-learned/
You may have to create allow rules for Azure storage for outbound traffic for VM agent to work.
I am using AZURE and have created several webapps and one Virtual Machine. I need all of them to be part of a virtual network so that cookies/and other packets transferred between them work properly. I created the VM and the network at the same time. But when I try to add networking to the webapps it shows the network but says that it does not have a gateway.
I don't know how to add a gateway to that VPN or how to make it work. Can anyone please help me?
You have to configure point to site in your virtual network before you can connect a web application to your vnet. Basically, you need to create a gateway and then configure point to site.
Since you already have a virtual network, follow steps 4 and 5 only:
Create a VNet with a Site-to-Site VPN connection using the Azure Portal
Later, configure P2S:
Configure a Point-to-Site connection to a virtual network using PowerShell
If everything goes right, you will be able to select the VNET in your app settings instead of a greyed item.
I wrote about this process a while ago and you can find my notes here.
I am trying to connect my Windows Azure Virtual machines to my On Premise network. I have established a site to site VPN tunnel, and have created the appropriate subnets and placed a virtual machine in one of the subnets that isn't the gateway subnet.
My on premise test network is 192.168.9.x/24 my Azure Network is 10.4.x.x/16 with a subnet for DMZ - 10.4.2.x/24 and ServerNetwork at 10.4.3.x/24.
I have confirmed that the tunnel is up and running both on the Windows Azure side, as well as on my Cisco ASA 5505.
I want my servers to be able to communicate across the tunnel, however currently they cannot see each other. I am missing something, I tried static routes between the two servers, and have not had any success. Has anyone gotten this to work? If so what did you do on the networking side of the config to make it work?
Thanks,
Steve
Windows Azure Virtual Network enables you to create secure site-to-site connectivity, as well as protected private virtual networks in the cloud.
You can specify the address space that will be used for both your virtual network and the virtual network gateway.
Additionally, new name resolution features allow you to connect directly to role instances and virtual machines by hostname.
These features allow you to use Windows Azure as you would a branch office, or as a protected private virtual network in the cloud.
You can read more about it here:
http://msdn.microsoft.com/en-us/library/windowsazure/jj156007.aspx
Here is a lab exercise to walk you through the process:
http://www.windowsazure.com/en-us/manage/services/networking/create-a-virtual-network/