Nested Hyper-V VMs running on Azure VMs (hosts) in EAST US and EAST US 2 can't communicate directly with each other.
Clark Warren
0
Reputation points
The nested Hyper-V VMs can ping the Azure VMs (hosts) across my peered VNETs in both directions, but they cannot ping each other directly. The nested Hyper-V VMs are attached to internal virtual NAT switches per MS documentation, so traffic goes out from them correctly to other end points inside the two VNETs, but inbound traffic is not making it past the Azure VM (host) to the Hyper-V VM running on it.
What is required to make the nested Hyper-V VMs communicate directly with each other successfully in this scenario?
Sign in to answer