Scribd
Upload
135 views2 pages

13 The Cisco Troubleshooting Methodology Lab Exercise

This lab tests network connectivity troubleshooting skills using a topology with routers R1, R2, and R3. A DNS server at 10.10.10.10 is not resolving requests, and telnet from R3 times out. Students must troubleshoot and fix connectivity issues so R3 can ping R1 by hostname, addressing potentially multiple problems along the path.

Uploaded by

Tent Dorin
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
135 views2 pages

13 The Cisco Troubleshooting Methodology Lab Exercise

This lab tests network connectivity troubleshooting skills using a topology with routers R1, R2, and R3. A DNS server at 10.10.10.10 is not resolving requests, and telnet from R3 times out. Students must troubleshoot and fix connectivity issues so R3 can ping R1 by hostname, addressing potentially multiple problems along the path.

Uploaded by

Tent Dorin
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/ 2

13 The Cisco Troubleshooting Methodology -

Lab Exercise
This lab tests your network connectivity troubleshooting skills.

Lab Topology

Load the Startup Configurations

Open the ’13 The Cisco Troubleshooting Methodology.pkt’ file in Packet Tracer
to load the lab.

This configures the lab topology as shown above with 10.10.10.10 as a DNS
server and adds static routes between R1 and R3.
Troubleshoot Connectivity to DNS Server

Note that routers cannot be DNS servers in Packet Tracer (it does not
support the ‘ip dns server’ command) so we are using a Packet Tracer
server device as the DNS server.

1) The host with IP address 10.10.10.10 has been configured as a DNS


server and should be able to resolve requests for ‘R1’, ‘R2’ and ‘R3’.
Members of staff have complained that DNS is not working.

2) From R3, use Telnet to check if the DNS service appears operational on
the DNS server at 10.10.10.10.

R3#telnet 10.10.10.10
Trying 10.10.10.10 ...
% Connection timed out; remote host not responding

3) When you have verified that DNS is not working, troubleshoot and fix the
problem. You have fixed the problem when R3 can ping R1 by hostname.
Note that there may be more than one issue causing the problem.

(You can click on the DNS server and then the ‘Services’ tab to check the
server’s DNS configuration.)

Hint: you can use the show ip interface brief command to verify
interfaces are operational on routers and switches. This command will be
covered in more detail in the next section.

You might also like