@MRCUR big thanks. I'll try that right now. ... View more

@MRCUR I did a new vNET-subnet and put a Win10 there.... and still no way to ping between the VM and the vMX.   If you're up for the challenge to resolve my issue....   https://drive.google.com/drive/folders/1qhdXhyeHAr68ZenRvfj_-2Ot90Io4ajc?usp=sharing   You will find there a lot of stuff.    You could reach me with : luc.paquet@gmail.com   Thanks ... View more

@MRCUR - I'll do that tonight   Question: Do I have to peer the 2 vNET in Azure or the vMX will do the job?   Thanks ... View more

I restarted my proof of concept Site to site VPN (MX and vMX) in Azure. I'm lost. Here my setup: 2 Windows 10 VM in Azure, both in the same vNet as the vMX, one in the same subnet,  Windows 10 - 1 : 10.0.0.x and a public IP Windows 10 - 2 : 10.0.2.x and a public IP vMX : 10.0.0.4 Azure Route table 1 - 10.0.0.0/24 next hop : 10.0.0.4 Azure Route table 2 - 10.0.2.0/24 next hop : 10.0.0.4 MX - 192.168.1.1 MX and vMX can ping each other. That's the only thing the vMX can ping. Both Windows 10 are not able to ping each other.  Windows Firewalls are turned OFF on both Windows 10 and Azure NSG is open to any-any for inbound and outbound. Route tables in the MX and vMX network are perfect. So, why the vMX and the 2 Windows 10 cannot see each other? ... View more

Hi Ping that are ok - MX (192.168.1.1) <--> vMX (10.1.1.4) - Mac (192.168.1.22) <--> MX (192.168.1.1) - vMX(10.1.1.4) <--> VMwin2016(10.1.1.5)   Ping that are not OK - MX <--> VMwin2016 - vMX <--> Mac - Mac <--> VMwin2016   The GTW for PC is the MX and for the PC2 is the vMX. Both MX and vMX are in a DMZ with natting.  I'm new to Azure, what you mean by ARM? How to check what I used? Thanks ... View more

Same problem here. Ping is working fine between the MX and the vMX but cannot goes further. "Still having some issues pinging from Azure to our on-prem site, but I think that could be resolved once we look into the routings a bit more." Have you solve that one? ... View more

Check my post. This will help you.   https://community.meraki.com/t5/Security-SD-WAN/vMX100-Azure-Cloud/m-p/10121/highlight/true#M2490     ... View more

Because of the lock problem with my 2 vMX, I was not able to stop 2 VMs in Azure. I open a case with Meraki support and here their response. I did it and it worked fine.  "When the appliance is created and you create a new Resource group it also creates another read only resource group. This is what is locked and caused a lot of the issues as I create the network during setup it became read only effecting the rest of our Azure setup. If you need to delete the appliance and start again you need to do the following: 1) Bring up all the resource groups in the Azure portal. 2) open the resource group that you created in the guide above. 3) In this resource group you will see a managed application which is a large bunch of letters and numbers. This is also the name of the lock that is in the read only resource group. If you delete this managed application it will also delete the read only resource group and the locks allowing you to start again." ... View more