Scribd Logo
Upload

Welcome to Scribd!

  • 69 views

    Troubleshoot IP Configuration 2troubleshoot IP Configuration 2

    Uploaded by

    michael
    The lab report details troubleshooting a connectivity issue between computers in different offices and an ISP. Running ping and tracert commands revealed the DHCP server was not assigning IP addresses correctly. Activating the DHCP scope for the local network resolved the issue, with confirmation through renewed successful ping tests.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Troubleshoot IP Configuration 2troubleshoot IP Configuration 2

    Uploaded by

    michael
    69 views2 pages
    The lab report details troubleshooting a connectivity issue between computers in different offices and an ISP. Running ping and tracert commands revealed the DHCP server was not assigning IP addresses correctly. Activating the DHCP scope for the local network resolved the issue, with confirmation through renewed successful ping tests.

    Original Title

    Troubleshoot IP Configuration 2Troubleshoot IP Configuration 2

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The lab report details troubleshooting a connectivity issue between computers in different offices and an ISP. Running ping and tracert commands revealed the DHCP server was not assigning IP addresses correctly. Activating the DHCP scope for the local network resolved the issue, with confirmation through renewed successful ping tests.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    69 views2 pages

    Troubleshoot IP Configuration 2troubleshoot IP Configuration 2

    Uploaded by

    michael
    The lab report details troubleshooting a connectivity issue between computers in different offices and an ISP. Running ping and tracert commands revealed the DHCP server was not assigning IP addresses correctly. Activating the DHCP scope for the local network resolved the issue, with confirmation through renewed successful ping tests.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    19/01/2024, 13:13 Learning Platform | CompTIA

    Lab Report

    Lab Report
    Time Spent: 07:32
    Score: 7/7 (100%)
    TASK SUMMARY
    Required Actions & Questions
    Q1After looking at the exhibit and the results of the tracert command from CorpServer to the ISP, 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 learned from the ping and tracert commands performed from
    each computer?
    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 on each
    computer
    Your 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.
    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 not assigning IP addresses correctly.
    Correct answer: The DHCP server is not assigning IP addresses correctly.
    Q5Why can the Exec and ITAdmin computers ping each other while they cannot ping CorpServer or the 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 Terminal (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 IP
    address. This indicates that this computer is not getting its IP address from the DHCP as it
    should.
    2. From the 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. Type ping 198.28.2.254 (the ISP) from the PowerShell prompt.
    Notice that the ping to the ISP is successful.
    e. Type tracert 198.28.2.254 and press Enter from the PowerShell prompt.
    f. From the top right, select Exhibits.
    https://labsimapp.testout.com/v6_0_581/simwindow.html?c2ltRGVmVXJsPWh0dHBzJTNBJTJGJTJGY2RuLnRlc3RvdXQuY29tJTJGX3ZlcnNpb25fODAxN… 1/2
    19/01/2024, 13:13 Learning Platform | CompTIA

    g. From the top right, select Answer Questions.


    h. Answer Question 1.
    i. Close the Exhibits and Lab 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 Terminal (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. Type ipconfig /all and press Enter from the PowerShell prompt.
    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. Type ipconfig /all and press Enter from the PowerShell prompt.
    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.
    2. Confirm that the DHCP service is enabled and activated for the local network.
    a. From Server Manager, select Tools > DHCP to start the DHCP console.
    b. Maximize the window for better viewing.
    c. From the left pane, expand CorpDHCP.CorpNet.local > IPv4.
    The down arrow for Scope [192.168.0.1] Subnet1 indicates that the scope is not active.
    d. Right-click Scope [192.168.0.1] Subnet1 and select Activate.
    The down arrow for the scope is gone, and the DHCP service for the local network is now active.
    3. Verify the fix by viewing the IP information for Exec and using the ping command.
    a. From the top left, select Floor 1 Overview.
    b. Under Executive Office, select Exec.
    c. From the Terminal prompt, type ipconfig /all and press Enter to check the Ethernet configuration.
    Notice that the lines for the default gateway, DNS server, and DHCP server are now configured, along
    with a new IP address within the DHCP scope for the local network.
    d. Type ping 198.28.2.254 and press Enter from the Terminal prompt.
    Notice that the ping to the ISP succeeds.
    e. Type tracert 198.28.2.254 and press Enter from the Terminal prompt.
    f. (Optional) Repeat step 3 for the ITAdmin computer.
    g. From the top right, select Answer Questions.
    h. Select Score Lab.
    i. Select Score.

    https://labsimapp.testout.com/v6_0_581/simwindow.html?c2ltRGVmVXJsPWh0dHBzJTNBJTJGJTJGY2RuLnRlc3RvdXQuY29tJTJGX3ZlcnNpb25fODAxN… 2/2

    You might also like