Scribd
Upload
111 views1 page

Explore Network Connectivity

The lab report summarizes troubleshooting network issues using ping, ipconfig, and tracert commands on two devices - ITAdmin and Exec. It explains how ping was used to test connectivity to other devices on the local network and a different network, how ipconfig showed the lack of a default gateway, and how tracert revealed the path and hops to a DNS server and other network device by going through the default gateway and routers between the networks.

Uploaded by

michael
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
111 views1 page

Explore Network Connectivity

The lab report summarizes troubleshooting network issues using ping, ipconfig, and tracert commands on two devices - ITAdmin and Exec. It explains how ping was used to test connectivity to other devices on the local network and a different network, how ipconfig showed the lack of a default gateway, and how tracert revealed the path and hops to a DNS server and other network device by going through the default gateway and routers between the networks.

Uploaded by

michael
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

18/01/2024, 19:39 Learning Platform | CompTIA

Lab Report

Lab Report
Time Spent: 11:35
Score: 1/1 (100%)
TASK SUMMARY
Required Actions
Use tracert on Exec Show Details

EXPLANATION
Complete this lab as follows:

1. Use the ping and ipconfig commands to troubleshoot network issues.


a. Right-click Start and then select Terminal (Admin).
b. At the PowerShell prompt, type ping 192.168.0.30 and press Enter to ping Office1.
You can successfully ping the IP address of Office1 from ITAdmin.
c. Type ping 199.92.0.33 and press Enter to ping Support.
You can't ping Support from ITAdmin. Notice that the IP address for Support is on a different network (network 199.92.0.0 instead of
network 192.168.0.0). Devices on the same local network must have IP addresses in the same network range. If you want to
communicate with Support, you need to change the IP address that is assigned to Support.
d. Type ping 192.168.0.5 and press Enter to ping the router's internal interface.
You can successfully ping the router's internal interface from ITAdmin because ITAdmin and the router's address (192.168.0.5) are on
the same network.
e. Type ipconfig and then press Enter to view the IP settings.
Notice that there is no default gateway assigned.
f. Type ping 163.128.78.93 and press Enter to ping the external DNS Server.
ITAdmin and the ISP are on different networks (network 192.168.0.0 and 163.128.78.0, respectively). Because ITAdmin doesn't have
a default gateway set, it can't communicate with devices on other networks.
2. Use the tracert command to see how network packets are forwarded.
a. From the top left, select Floor 1 Overview.
b. Under Executive Office, select Exec.
c. Right-click Start and then select Terminal (Admin).
d. At the PowerShell prompt, type tracert 198.28.56.1 and press Enter.
When you communicate with devices on other networks, the packets go to the default gateway first (the router between the two
networks). The packets are sent to the router interface on the same network as the sending host. Then they go on to the next hop in the
path. In this case, there are two IP addresses listed in the tracert output, but only one router (hop) between Exec and the internet router.
The last address in the tracert output is the internet router.
e. Enter tracert 163.128.78.93 and press Enter to trace the path to one of the ISP's DNS servers.
When you trace the path between Exec and the ISP's DNS server, the path has additional hops. The first lines in the tracert output are
the routers (hops) between Exec and the DNS server. The last address in the tracert output is the DNS server itself.

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

You might also like