You may be frustrated at Microsoft Azure’s lack of ability to power off the Network gateways especially when they are chewing up resources and $. Unfortunately Azure provides no current way to power the gateways down so the only current solution is to delete them, however you need to delete them in the right order to remove the service pre-requisites.
Failed to delete virtual Network Gateway
Failed to delete virtual network gateway 'UKSouthGateway'.
Error: Gateway /subscriptions/xxxxx-xxxx-xxx-xxxx-xxxxxxx/resourceGroups/
The gateway devices must be deleted in a specific order
- Connections (both sides)
- Local Network Gateway (both sides)
- Virtual Network Gateways (both sides)
- IP Ranges (only if necessary)
We found a network bridging issue for a client running VMWare workstation 10. The VM would ‘sometimes’ connect to the production / corporate network and obtain a DHCP address. Othertimes it would not and it would get an APIPA address instead. (169.254.x.x)
Various internet posts suggested
- Disconnecting the Virtual nic – NO SUCCESS
- Upgrade the VM tools – NO SUCCESS
couldn’t even mount the ISO for some reason, so the .iso’s are located here(“C:\Program Files (x86)\VMware\VMware View\Client\Local Mode”) for future reference so you can extract and then manually run the installation.
- Remove and re add the NIC – NO SUCCESS
Turns out that when bridging mode is set to ‘automatic’ VMWare workstation will bind to any and all available network cards. (Bluetooth, wifi, other VMNics, Virtual box etc) So its a bit of pot luck when it connect to the production network and not the others.
- Open the Virtual Network editor
- Edit the appropriate ‘bridged’ network and select the appropriate NIC to bridge
- Be sure the configuration of the VM’s NIC is set to BRIDGED or is bound to the VMNetX that is configured for bridging.
Note: Besure to run the Virtual Network Editor as an administrator else you will not be able to change settings.