4.2.6 - Troubleshoot IP Configuration 2

5/17/23, 6:06 PM TestOut LabSim https://labsimapp.testout.com/v6_0_549/simwindow.html?c2ltRGVmVXJsPWh0dHBzJTNBJTJGJTJGY2RuLnRlc3RvdXQuY29tJTJGX3ZlcnNpb25fNT… 1/3 Lab Report Lab Report Time Spent: 19:57 Score: 7/7 (100%) TASK SUMMARY Required Actions & Questions Q1After looking at the exhibits and the results of the tracert command, which of the following IP addresses is assigned to the building A network router Your answer: 192.168.0.5 Correct answer: 192.168.0.5 Q2Which of the following best describes what you have learned from your troubleshooting up to this point Your answer: The connections from building A to the ISP are working. Correct answer: The connections from building A to the ISP are working. Q3Mark all of the observations you found to be true after examining the results of the ipconfig /all command Your answer: The IP address is an APIPA address, not a valid address for this network., The IP information for the Ethernet adapter is obtained from a DHCP server. Correct answer: The IP information for the Ethernet adapter is obtained from a DHCP server., The IP address is an APIPA address, not a valid address for this network. Q4Which of the following is the most likely reason the ping tests to the ISP failed from Exec and ITAdmin, but were successful from CorpServer Your answer: The DHCP server is probably not assigning IP addresses correctly. Correct answer: The DHCP server is probably not assigning IP addresses correctly. Q5Why can the Exec and ITAdmin computers ping each other while they cannot ping CorpServer or ISP Your answer: Both are using an APIPA address. Correct answer: Both are using an APIPA address. In the Networking Closet, activate the DHCP scope for the local network Verify that the Executive Office and IT Administrator workstations can communicate with the internet Show Details EXPLANATION Complete this lab as follows: Troubleshoot 1. From the Exec computer, begin troubleshooting by verifying the scope of the connectivity problem. a. Under Executive Office, select Exec . b. Right-click Start and then select Windows PowerShell (Admin) . c. From the PowerShell prompt, run the following ping commands. Press Enter after each command: ping 192.168.0.10 (CorpServer). ping 198.28.2.254 (The Internet Service Provider, or ISP) . Notice that both pings are unsuccessful. ping ITAdmin (the name of the computer in the IT Administration office). Notice that the ping to ITAdmin is successful. However, it is responding using an APIPA

5/17/23, 6:06 PM TestOut LabSim https://labsimapp.testout.com/v6_0_549/simwindow.html?c2ltRGVmVXJsPWh0dHBzJTNBJTJGJTJGY2RuLnRlc3RvdXQuY29tJTJGX3ZlcnNpb25fNT… 2/3 IP address. This indicates that this computer is not getting its IP address from the DHCP as it should. 2. From CorpServer computer, continue troubleshooting the problem by trying to access the ISP. a. From the top left, select Floor 1 Overview . b. Under Networking Closet, select CorpServer . c. Right-click Start and then select Windows PowerShell (Admin) . d. From the PowerShell prompt, type ping 198.28.2.254 (the ISP). Notice that the ping to the ISP is successful. e. From the PowerShell prompt, type tracert 198.28.2.254 and press Enter . f. From the top right, select Exhibits . g. From the top right, select Answer Questions . h. Answer Question 1. i. Close the Exhibits and Answer Questions windows. 3. From the ITAdmin computer, continue troubleshooting the problem by trying some additional ping tests. a. From the top left, select Floor 1 Overview . b. Under IT Administration, select ITAdmin . c. Right-click Start and then select Windows PowerShell (Admin) . d. From the PowerShell prompt, run the following ping commands. Press Enter after each command: ping 192.168.0.10 (CorpServer). ping 198.28.2.254 (the ISP). Notice that the ping to the ISP fails. ping exec (the name of the computer in the Executive Office). Notice that the ping to Exec is successful. However, the Exec computer is responding with an APIPA IP address. e. From the top right, select Answer Questions . f. Answer Question 2. 4. From ITAdmin, use the ipconfig /all command to continue troubleshooting. a. From the PowerShell prompt, type ipconfig /all and press Enter . b. Answer Questions 3 and 4. 5. From Exec, use the ipconfig /all command to continue troubleshooting. a. From the top left, select Floor 1 Overview . b. Under Executive Office, select Exec . c. From the PowerShell prompt, type ipconfig /all and press Enter . d. Answer Questions 5. e. Minimize the Lab Questions dialog. Fix the Issue Since it appears that the DHCP server is not functioning correctly, check the current state of the DHCP services. 1. Access the CorpDHCP virtual server. a. From the top left, select Floor 1 Overview . b. Under Networking Closet, select CorpServer . c. From Hyper-V Manager, select CORPSERVER . d. Maximize the window to view all virtual machines. e. Double-click CorpDHCP to connect to the server.