0% found this document useful (0 votes)
1K views3 pages

5.8.8 Exploring TCP-IP Communications

This document describes steps to explore TCP/IP communications and default gateways using ping, traceroute, and IP addresses. It has students complete steps like pinging between devices, using traceroute to trace routes, and configuring IP addresses and default gateways on switches to allow or block communication between devices. The key findings are that switches are not shown in traceroute outputs, incorrectly configured IP addresses can block communication, and default gateways must be configured properly for devices to communicate across networks.

Uploaded by

Ricardo Ferreira
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
1K views3 pages

5.8.8 Exploring TCP-IP Communications

This document describes steps to explore TCP/IP communications and default gateways using ping, traceroute, and IP addresses. It has students complete steps like pinging between devices, using traceroute to trace routes, and configuring IP addresses and default gateways on switches to allow or block communication between devices. The key findings are that switches are not shown in traceroute outputs, incorrectly configured IP addresses can block communication, and default gateways must be configured properly for devices to communicate across networks.

Uploaded by

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

5.8.

8 Exploring TCP/IP Communications


In this lab, you will explore how ping, traceroute, and the default gateway setting affect device
communication. Devices on this network use the following IP addresses:

Device IP Address

Wrk1 192.168.11.1

Wrk2 192.168.11.2

Branch1 192.168.11.250

SFO Fa0/0 192.168.11.254

SFO Fa0/1 192.168.12.254

Wrk12 192.168.12.1

Complete the following steps:

1. Open the command prompt for the Wrk1 device. Verify that you can ping the Wrk2 device.
2. Use the tracert command on Wrk1 and trace the route to Wrk2.
Why doesn't the switch show in the path between Wrk1 and Wrk2?
3. On the Branch1 switch, use the show ip interface brief command.
What is the IP address assigned to the switch?
4. From the Branch1 switch, try to ping Wrk1.
Why does the ping fail?
5. Configure the Branch1 switch with the following IP address: 192.168.1.1 with a mask of
255.255.255.0.
6. From the Branch1 switch, try to ping Wrk1.
Why does the ping fail?
7. On Wrk1, try to ping Wrk2.
What effect does the IP address configured on the switch have on the ability of workstations to
communicate through the switch?
8. Change the IP address on Branch1 to the correct IP address noted in the table above.
9. From the Branch1 switch, try to ping Wrk1.
Why does this now succeed?
10. On Wrk1, use tracert to trace the path between Wrk1 and Wrk2.
What effect does the IP address on the switch have on the trace route output?
11. On Branch1, try to ping the SFO Fa0/0 interface.
Why does the ping fail? Use the show ip interface brief command on the switch and the
router to identify and correct the problem.
12. After fixing the problem, verify that the Branch1 switch can communicate with
the SFO router.
13. On Wrk1, try to ping Wrk12.
Does this test succeed?
14. On Branch1, try to ping Wrk12.
Why does the ping fail?
15. On Branch1, configure 192.168.11.254 as the default gateway.
16. From Branch1, try to ping Wrk12.
Why does this test now succeed?
17. On Wrk1, use tracert to trace the path between Wrk1 and Wrk12.
What effect does the presence of the switches in the path have on the trace route output?

Score Report
Start Lab

You might also like