Troubleshoot IPv4 Connectivity
In this IT Pro Challenges, virtual lab learners are introduced to skills required to troubleshoot IPv4 connectivity. Exercises in this lab teach users how to configure routing, DNS resolution, and egress filter. The topics covered in this lab are critical for learners to be effective in exploitation analyst, system administrator job roles in cyber...
Already have an account? Sign In »
IP stands for Internet Protocol, which is applied to give datagrams between hosts in a network. It is a process by which data is transferred from one machine to another machine through the internet. IPv4 is the fourth version of the Internet Protocol. It was modified and is now extensively used in data communication over various kinds of networks.
In this hands-on virtual lab, you will learn how to troubleshoot IPv4 connectivity. First, you will verify IPv4 connectivity and then verify routing and DNS resolution. Next, you will modify the configuration to allow only HTTP traffic. Finally, you will verify the configuration changes. The other challenges in this series are:
- Configure a DHCP Relay Agent.
- Establish IPv6 Connectivity.
- Administer an IPAM Environment.
- Can You Configure a Multi-Subnet Environment?
Understand the Scenario
In this virtual lab, you are a network administrator, and your job is to troubleshoot network connectivity in a network that contains three subnets connected by a router. To accomplish this task, you will use three subnets that are connected by a router. The router has the following interfaces:
- 10.0.0.62 /26
- 10.0.0.126 /26
- 10.0.0.190 /26
Troubleshoot and resolve IP connectivity issues
In this virtual lab, you will troubleshoot and resolve IP connectivity issues using three machines, DC1, DC2, and SVR1. First, on SVR1, you will sign in and select the Type text icon to enter the associated text into the virtual machine. Next, you will examine the interfaces on the hosts' DC1, DC2, SVR1, and SVR2 by using the Get-NetIPAddress and Get-NetIPConfiguration cmdlets to determine which subnet each host should be on according to its defined default gateway. For all virtual machines, you will sign in as Contoso\Administrator. Next, you will verify IPv4 connectivity to DC1.contoso.com, DC2.contoso.com, and SVR2.contoso.com by using ping or the Windows PowerShell cmdlet Test-NetConnection. For any hosts that you are unable to ping, troubleshoot the issue, and then correct the problem. If needed, you will switch to SVR2 or DC1, and then sign in as Administrator using Passw0rd! as the password. Finally, you will check and confirm that you can ping DC1.contoso.com, DC2.contoso.com, and SVR2.contoso.com from SVR1.
Modify the egress filter on the router to allow only HTTP traffic
Egress filtering is a method in which outbound data is observed or modified, normally using a firewall that prevents packets that fail to meet specific security demands. The word "egress" indicates "outgoing". In this section of the lab, learners will modify the egress filter on the router to allow only HTTP traffic. First, you will modify the egress filter for the interface that connects to the network that SVR2 is on to allow only HTTP traffic. Next, on SVR1, you will verify that you can access http://svr2.contoso.com, and then verify that you are unable to ping SVR2. Finally, you will check and confirm that you were able to access the default webpage on SVR2, and you were unable to ping SVR2 from SVR1.
Lab Summary Conclusion
After completing the "Troubleshoot IPv4 Connectivity" virtual lab, you will have accomplished the following:
- Verified IPv4 connectivity, routing, and DNS resolution for a network that has three subnets.
- Modified the egress filter on a router to allow only HTTP traffic.