Forum Discussion
Solved
VMs on the same VNET can not talk to each other
Not sure what is exactly happening since it was always working before but VMs on different subnets within the same virtual network with no NSGs or firewalls between them can not talk to each other. P...
In that case i suggest you file a ticket so the network can be checked in the back end.
2 things that stands out in OS configuration.
1. The persistent route should be needed
2. Static IP for Azure VM should be setup from the portal and not in the guest OS
Also did the issue start after a change to the environment? (joined domain, etc...)
Since the issue is at the subnet level confirm no subnet NSG or User Define routes on subnet.
Neither persistent route no static IP is required to route between subnets. They shall work per documentation out of the box with no additional changes.
There is no NSGs setup on any level, there is no firewalls on either side.
I'm pretty sure something is broken in Azure specifically for my VNET setup and not something specific to VMs which I put in.
There is no NSGs setup on any level, there is no firewalls on either side.
I'm pretty sure something is broken in Azure specifically for my VNET setup and not something specific to VMs which I put in.
In that case i suggest you file a ticket so the network can be checked in the back end.
- The answer in this area is quet easy. Since the last Azure Network changes and the introduction of "Vnet Peering" each subnet og a VNET has his own NSG and route table assignement. so in this case when you work only in one VNET you Have to create a custom route table an have to set the "virtual Network Gateway route Propagation" to "enabled". So all subnets have a container to publish there gateway and next-Hop configuration. configure each subnet with the same route table and Problem is solved
