Now the host and the client are connected via the remote desktop connecting software and both users can share their computer screen with each other.
I have to run for a bit, I'll post the traces soon.When the client enters the same username, password or URL in his browser, the remote connection is established. I can't rdp to either vm which was the problem that started all of this. I still can't rdp to it though even though it is using the same NSG as the original EliteU VM, 10.0.8.37 with RDP port 3389 open. I was actually able to ping the 10.0.9.36 VM but today I can't.
Last night, for sh*ts and giggles, I played around with vnet peering. I've named the VM, VM-Mer-EliteU, residing on the 10.0.9.32/28 subnet.ġ0.0.9.0/24 subnetted into 2, 10.0.9.0/28 on which the vmx (10.0.9.4) resides and 10.0.9.32/28 on which my new VM-Mer-EliteU (10.0.9.36) resides.ġ0.0.8.0/24 also subnetted into 2, 10.0.8.0/28 on which the Bastion, which has been deleted resided and 10.0.8.32/28, on which my original VM-EliteU (10.0.8.37) resides.Īs of yesterday, I was unable to ping or trace to and from anything vmx100 to any of the vnets/subnets or from either of the resources (the 2 VMs) to the Meraki. So now I have a comparison between the traffic coming and going from 10.0.9.36 (subnet of 10.9.0.0/24. I decided to stand up another VM, exactly like the EliteU VM, but on the same vnet as the vmx, different subnet. Thanks for your response and verifying my routes are seemingly correct. This will help us narrow down where the issue lies as your route table is exactly what I would do for this setup. The tracerts will demonstrate that traffic is (or isn't) hitting the VMX appliance as it's next hop.
Also, thanks for sharing the screenshot of your Route Table. When I try to rdp using the Azure rdp client, it tells me another computer has disconnected my session which is not possible since I'm the only one setting this up.Īnyone out there that has successfully set up a Cisco Meraki VMX100 in Azure and is able to access the resources in Azure behind the you are well. However, when I try to rdp using the MS rdp client, I get the generic unable to connect message. When I run the connection test it tells me that access has been granted. I have also set up network security groups allowing inbound and outbound traffic to port 3389 (rdp). I have set up routes but obviously they are not correct or else this would be working! I need, specifically, to be able to rdp to the VMs in Azure. I spoke to Cisco and they confirmed my vmx100 is configured correctly and traffic is reaching the Azure resources however traffic from Azure VM is not being passed back. Although the tunnel is up, running and passing traffic, I can't rdp to my resources in Azure. We have established a site to site vpn between our Azure Meraki vmx100 (managed Azure service/app) and our on premise m圆4.