Troubleshooting basic network routing is an important skill. This troubleshooting scenario is an opportunity to assess your skills in this area. In this hands-on lab, you are trapped in an escape room. To escape, you need to troubleshoot the networking issues so that you can connect to the jumpbox and access the escape room exit on the web server.
> **Note:** If you are completing this lab as part of the *Hands-On Network Troubleshooting with Azure Infrastructure as a Service (IaaS): An Escape Room Adventure* course, you will receive a key upon successful completion of this hands-on lab that you can use to unlock the door in the next hands-on lab in that course.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Confirm Virtual Network Peering Configuration
- Check that virtual network peering exists between the
hubvnetvirtual network and thejumpboxvnetvirtual network in both directions. - Check that virtual network peering exists between the
hubvnetvirtual network and theworkloadvnetvirtual network in both directions. - Check that the Traffic forwarded from remote network setting is correct on all the virtual network peers.
- Check that virtual network peering exists between the
- Determine If the Virtual Network Routing Configuration Is Correct
- Determine if the route table configuration for the
AzureFirewallSubnetsubnet is correct. - Determine if a route table is linked to either the subnet or network interface for
JumpBox1. - Determine if a route table is linked to either the subnet or network interface for
WebServer1. - Determine if a route exists in the linked route table to direct traffic to the Azure Firewall’s private IP.
- Determine if the route table configuration for the
- Connect to WebServer1 from JumpBox1
- Use Remote Desktop to connect to
JumpBox1using the public IP address for the Azure Firewall. - Use Microsoft Edge on
JumpBox1to connect toWebServer1using the addresshttp://10.1.0.80.
- Use Remote Desktop to connect to
