Azure VNet Peering - Only communication in one way

Lucas Hökerberg 0 Reputation points
2024-01-31T11:55:32.5433333+00:00

So, after a lot of troubleshooting back and fourth, and different issues (sometimes full connectivity both ways, sometimes no connectivity at all), I'm now stable in the following issue. I have two VNets in the same region (different subscriptions), let's call them vnet-1 (172.16.1.0/24) and vnet-2 (172.16.2.0/24). I have configured peering between them and the peering status is all fine. I have active and valid system routes to each peered VNet in all machines in both networks. I can ping and RDP to a Windows VM in vnet-1 from vnet-2, but not the other way around (no ping nor RDP). Windows Firewall is completley off in both test VMs, and the NSGs in both VNets are allowing the traffic. Troubleshooting the connection between vnet-1 and vnet-2 gives me the below outcome (note all the failed probes): User's image What am I doing wrong? Or are there any issues in Azure?

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
{count} votes

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.