It's been sitting at "THE GATEWAY WAS NOT CREATED." for hours after creating a Virtual Network in Azure. Is this normal? What should I do?
We previously created a network in the wrong DC, it didn't seem to be so slow then.
Azure – Creating Virtual Network Azure – The Gateway was not created
azurenetworking
Related Solutions
If by "don't seem to recognize each other" you mean you can't send and receive ICMP pings that's because ICMP is disabled on Azure VMs.
Try opening a TCP socket on the desired port running the service to which you want to verify connectivity instead:
PS C:\Windows\system32> New-Object Net.Sockets.TcpClient "192.168.10.10", 8043
Client : System.Net.Sockets.Socket
Available : 0
Connected : True
ExclusiveAddressUse : False
ReceiveBufferSize : 65536
SendBufferSize : 65536
ReceiveTimeout : 0
SendTimeout : 0
LingerState : System.Net.Sockets.LingerOption
NoDelay : False
According to your description, maybe there are something wrong with the browse, we can use PowerShell to get the status of your Azure VM, in this way we can find the VM's status:
PS C:\Users> Get-azurermvm -ResourceGroupName vm -Name jasonvm -Status
ResourceGroupName : vm
Name : jasonvm
BootDiagnostics :
ConsoleScreenshotBlobUri : https://vmdiag136.blob.core.windows.net/bootdiagnostics-jasonvm-fd5e4f46-55c0-4b6e-9640-a66a175c6f02/jasonvm.fd5e4f46-55c0-4b6e-9640-a66a175c6f02.screenshot.bmp
SerialConsoleLogBlobUri : https://vmdiag136.blob.core.windows.net/bootdiagnostics-jasonvm-fd5e4f46-55c0-4b6e-9640-a66a175c6f02/jasonvm.fd5e4f46-55c0-4b6e-9640-a66a175c6f02.serialconsole.log
Disks[0] :
Name : jasonvm
Statuses[0] :
Code : ProvisioningState/succeeded
Level : Info
DisplayStatus : Provisioning succeeded
Time : 5/16/2017 9:45:28 AM
VMAgent :
VmAgentVersion : 2.2.10
Statuses[0] :
Code : ProvisioningState/succeeded
Level : Info
DisplayStatus : Ready
Message : Guest Agent is running
Time : 5/16/2017 9:51:35 AM
Statuses[0] :
Code : ProvisioningState/succeeded
Level : Info
DisplayStatus : Provisioning succeeded
Time : 5/16/2017 9:47:41 AM
Statuses[1] :
Code : PowerState/running
Level : Info
DisplayStatus : VM running
Also we can use PowerShell command to stop this VM:
Stop-AzureRmVM -Name -ResourceGroupName
For test, we can change another browse to login Azure portal.
Best Answer
Yes, you need to click the create gateway button. :)
Here are the steps to create the site to site VPN. http://blogs.technet.com/b/canitpro/archive/2013/10/09/step-by-step-create-a-site-to-site-vpn-between-your-network-and-azure.aspx
Also this can be done manually: http://blogs.msdn.com/b/igorpag/archive/2013/08/27/manually-adding-a-vpn-gateway-to-azure-virtual-network.aspx