The reports site is down
Problem
Finance can't open the reports site.
Your job
- Let Finance open the reports site (vm-finance to vm-reports on 443)
Without breaking
- Keep SSH to vm-reports blocked from the users subnetbroken
Background
"Finance can't open the reports site since this morning. It worked yesterday, and nobody here touched anything." The reports site runs on vm-reports (10.1.1.4) over HTTPS. Finance works from subnet-users, like vm-finance. SSH to the reports server must stay locked down for users.
How to work it
- 1See it fail
Prove the problem yourself before you change anything. Reports are often wrong.
VM commands forVMsssh vm-financeWhat's this?
Opens a shell on vm-finance, 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.
nc -zv 10.1.1.4 443What's this?
netcat, a standard Linux tool. Tries to open a TCP connection and reports whether it worked.
-zonly check whether the port answers. Send no data-vprint the result in words10.1.1.4where to connect443the port to try
Ticks off when the test runs on vm-finance.
- 2Find where it stops
- 3Name the cause
- 4Fix it and test again
Sources on Microsoft Learn (2)
0/2 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-finance → vm-reports:443should work: not workingvm-finance → vm-reports:22should stay blocked: blocked
Goals 0/2
Cloud Shell · bashVMsrg-lab · eastus2
cloudshell:~$