Intermediate · Peering · 5 of 15

Spoke can't reach the hub after peering

Problem

vm-spoke1 can't connect to vm-hub on 443.

Your job

Get the peering Connected on both sides
Get vm-spoke1 reaching vm-hub on 443

Background

The app on vm-spoke1 (10.1.1.4, in vnet-spoke1) needs the shared service on vm-hub (10.0.1.4, in vnet-hub) on port 443. Yesterday a colleague set up peering between the two networks and said it was done before going home. vm-spoke1 still can't connect. Working means vm-spoke1 reaches vm-hub on 443.

How to work it

1See it fail
Prove the problem yourself before you change anything. Reports are often wrong.
VM commands forVMs
1. ssh vm-spoke1
  What's this?
  Opens a shell on vm-spoke1, so the next commands run on that VM. In this lab it's a shortcut. In real Azure you'd connect through something like Azure Bastion, or SSH to an address you can reach.
2. nc -zv 10.0.1.4 443
  What's this?
  netcat, a standard Linux tool. Tries to open a TCP connection and reports whether it worked.
  - -z only check whether the port answers. Send no data
  - -v print the result in words
  - 10.0.1.4 where to connect
  - 443 the port to try
Ticks off when the test runs on vm-spoke1.
2Find where it stops
3Name the cause
4Fix it and test again
5Explain it

Sources on Microsoft Learn (2)

Create, change, or delete a virtual network peering az network vnet peering

0/1 changes

Network map

Resource group, the outer dashed frame
Virtual network, with its address space top right
Subnet, with range and usable IPs (5 reserved)
Network security group. A small shield on a VM's NIC means the NIC has one too
Route table on the subnet
VM Appliance Private endpoint
Peering Connected Initiated or access off
Goal working Goal broken, X marks where it stops
Private DNS zone, dotted lines go to linked VNets
Orange pulse: what your last command changed. Drag to pan, Ctrl and scroll to zoom.

vm-spoke1 → vm-hub:443should work: not working

Goals 0/3

Cloud Shell · bashVMsrg-lab · eastus2

cloudshell:~$