17.7.6 Packet Tracer - Troubleshoot Connectivity Issues (Answers)

17.7.6 Packet Tracer - Troubleshooting Connectivity Issues Answers

17.7.7 Packet Tracer - Troubleshoot Connectivity Issues

Topology

17.7.6 Packet Tracer - Troubleshoot Connectivity Issues topology

17.7.7 Packet Tracer - Troubleshoot Connectivity Issues

Addressing Table

Device Interface IP Address Subnet Mask Default Gateway
R1 G0/0 172.16.1.1 255.255.255.0 N/A
R1 G0/1 172.16.2.1 255.255.255.0 N/A
R1 S0/0/0 209.165.200.226 255.255.255.252 N/A
R2 G0/0 209.165.201.1 255.255.255.224 N/A
R2 S0/0/0 (DCE) 209.165.200.225 255.255.255.252 N/A
PC-01 NIC 172.16.1.3 255.255.255.0 172.16.1.1
PC-02 NIC 172.16.1.4 255.255.255.0 172.16.1.1
PC-A NIC 172.16.2.3 255.255.255.0 172.16.2.1
PC-B NIC 172.16.2.4 255.255.255.0 172.16.2.1
Web NIC 209.165.201.2 255.255.255.224 209.165.201.1
DNS1 NIC 209.165.201.3 255.255.255.224 209.165.201.1
DNS2 NIC 209.165.201.4 255.255.255.224 209.165.201.1

Objectives

The objective of this Packet Tracer activity is to troubleshoot and resolve connectivity issues, if possible. Otherwise, the issues should be clearly documented and so they can be escalated.

Background / Scenario

Users are reporting that they cannot access the web server, www.cisco.pka after a recent upgrade that included adding a second DNS server. You must determine the cause and attempt to resolve the issues for the users. Clearly document the issues and any solution(s). You do not have access to the devices in the cloud or the server www.cisco.pka. Escalate the problem if necessary.
Router R1 can only be accessed using SSH with the username Admin01 and password cisco12345.

Contents

Note: Follow the steps in order and fix only one issue at a time. The answers of each step depend on what has already been fixed: for example, PC-01 and PC-02 cannot reach PC-A and PC-B until the R1 G0/1 address is corrected in Step 3.

Step 1: Determine the connectivity issue between PC-01 and web server.

a. On PC-01, open the command prompt. Enter the command ipconfig to verify what IP address and default gateway have been assigned to PC-01. Correct as necessary according to the Addressing Table.

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::2
   IPv6 Address....................: 2001:DB8:ACAD::2
   IPv4 Address....................: 172.168.1.3
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: FE80::1
                                     172.16.1.1

The IPv4 address of PC-01 is 172.168.1.3, which is not in the LAN 172.16.1.0/24 (the second octet is wrong). Change it to 172.16.1.3.
Fix 1: On PC-01, click Desktop > IP Configuration and change the IPv4 Address to 172.16.1.3.
17.7.6 PC-01 IP Configuration with the corrected IP address

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::2
   IPv6 Address....................: 2001:DB8:ACAD::2
   IPv4 Address....................: 172.16.1.3
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: FE80::1
                                     172.16.1.1

b. After verifying/correcting the IP addressing issues on PC-01, issue pings to the default gateway, web server, and other PCs. Were the pings successful? Record the results.

C:\> ping 172.16.1.1

Pinging 172.16.1.1 with 32 bytes of data:

Reply from 172.16.1.1: bytes=32 time<1ms TTL=255
Reply from 172.16.1.1: bytes=32 time<1ms TTL=255
Reply from 172.16.1.1: bytes=32 time<1ms TTL=255
Reply from 172.16.1.1: bytes=32 time<1ms TTL=255

Ping statistics for 172.16.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\> ping 209.165.201.2

Pinging 209.165.201.2 with 32 bytes of data:

Request timed out.
Reply from 209.165.201.2: bytes=32 time=5ms TTL=126
Reply from 209.165.201.2: bytes=32 time=1ms TTL=126
Reply from 209.165.201.2: bytes=32 time=5ms TTL=126

Ping statistics for 209.165.201.2:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 5ms, Average = 3ms

C:\> ping 172.16.1.4

Pinging 172.16.1.4 with 32 bytes of data:

Reply from 172.16.1.4: bytes=32 time=6ms TTL=128
Reply from 172.16.1.4: bytes=32 time<1ms TTL=128
Reply from 172.16.1.4: bytes=32 time<1ms TTL=128
Reply from 172.16.1.4: bytes=32 time<1ms TTL=128

Ping statistics for 172.16.1.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 6ms, Average = 1ms

C:\> ping 172.16.2.3

Pinging 172.16.2.3 with 32 bytes of data:

Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.

Ping statistics for 172.16.2.3:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\> ping 172.16.2.4

Pinging 172.16.2.4 with 32 bytes of data:

Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.

Ping statistics for 172.16.2.4:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Ping to default gateway (172.16.1.1)?
Yes

To web server (209.165.201.2)?
Yes

Ping to PC-02?
Yes

To PC-A?
No

To PC-B?
No

c. Use the web browser to access the web server on PC-01. Access the web server by first entering the URL http://www.cisco.pka and then by using the IP address 209.165.201.2. Record the results.

Can PC-01 access www.cisco.pka?
Yes
17.7.6 PC-01 web browser opens http://www.cisco.pka

Using the web server IP address?
Yes
17.7.6 PC-01 web browser opens the web server by IP address 209.165.201.2

d. Document the issues and provide the solution(s). Correct the issues if possible.
The IP address on PC-01 is incorrectly configured. To resolve the issue, the IP address is changed from 172.168.1.3 to 172.16.1.3. PC-01 cannot successfully ping the PCs on the 172.16.2.0/24 network.

What we learned:
PC-01 was in the wrong network (172.168.1.0 instead of 172.16.1.0). After the fix it reaches its gateway, PC-02 and the web server, but not PC-A or PC-B. The Destination host unreachable replies come from 209.165.200.225 (the ISP router R2): R1 has no route to 172.16.2.0/24, so it forwards the packets to its default route, and R2 does not know that network either. The problem with LAN 172.16.2.0/24 is on R1 (Step 3).

Step 2: Determine the connectivity issue between PC-02 and web server.

a. On PC-02, open the command prompt. Enter the command ipconfig to verify the configuration for the IP address and default gateway. Correct as necessary.

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::2
   IPv6 Address....................: 2001:DB8:ACAD::3
   IPv4 Address....................: 172.16.1.4
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: FE80::1
                                     172.16.1.11

The default gateway of PC-02 is 172.16.1.11, but the R1 G0/0 address is 172.16.1.1. Change the default gateway to 172.16.1.1.
Fix 2: On PC-02, click Desktop > IP Configuration and change the Default Gateway to 172.16.1.1.
17.7.6 PC-02 IP Configuration with the corrected default gateway

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::2
   IPv6 Address....................: 2001:DB8:ACAD::3
   IPv4 Address....................: 172.16.1.4
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: FE80::1
                                     172.16.1.1

b. After verifying/correcting the IP addressing issues on PC-02, issue pings to the default gateway, web server, and other PCs. Were the pings successful? Record the results.

C:\> ping 172.16.1.1

Pinging 172.16.1.1 with 32 bytes of data:

Reply from 172.16.1.1: bytes=32 time<1ms TTL=255
Reply from 172.16.1.1: bytes=32 time<1ms TTL=255
Reply from 172.16.1.1: bytes=32 time<1ms TTL=255
Reply from 172.16.1.1: bytes=32 time<1ms TTL=255

Ping statistics for 172.16.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\> ping 209.165.201.2

Pinging 209.165.201.2 with 32 bytes of data:

Reply from 209.165.201.2: bytes=32 time=9ms TTL=126
Reply from 209.165.201.2: bytes=32 time=5ms TTL=126
Reply from 209.165.201.2: bytes=32 time=6ms TTL=126
Reply from 209.165.201.2: bytes=32 time=7ms TTL=126

Ping statistics for 209.165.201.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 9ms, Average = 6ms

C:\> ping 172.16.1.3

Pinging 172.16.1.3 with 32 bytes of data:

Reply from 172.16.1.3: bytes=32 time<1ms TTL=128
Reply from 172.16.1.3: bytes=32 time<1ms TTL=128
Reply from 172.16.1.3: bytes=32 time<1ms TTL=128
Reply from 172.16.1.3: bytes=32 time<1ms TTL=128

Ping statistics for 172.16.1.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\> ping 172.16.2.3

Pinging 172.16.2.3 with 32 bytes of data:

Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.

Ping statistics for 172.16.2.3:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\> ping 172.16.2.4

Pinging 172.16.2.4 with 32 bytes of data:

Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.
Reply from 209.165.200.225: Destination host unreachable.

Ping statistics for 172.16.2.4:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Ping to default gateway (172.16.1.1)?
Yes

To web server (209.165.201.2)?
Yes

Ping to PC-01?
Yes

To PC-A?
No

To PC-B?
No

c. Navigate to www.cisco.pka using the web browser on PC-02. Record the results.

Can PC-02 access www.cisco.pka?
Yes.
17.7.6 PC-02 web browser opens www.cisco.pka

Using the web server IP address?
Yes

d. Document the issues and provide the solution(s). Correct the issues if possible.
PC-02 can access the web server using the IP address after correcting the default gateway. The default gateway should be configured as 172.16.1.1 on PC-02. PC-02 cannot successfully ping the PCs on the 172.16.2.0/24 network.

What we learned:
A wrong default gateway does not affect traffic inside the LAN, only traffic to other networks. After the fix PC-02 reaches the web server; like PC-01 it still cannot reach LAN 172.16.2.0/24.

Step 3: Determine the connectivity issue between PC-A and web server.

a. On PC-A, open the command prompt. Enter the command ipconfig to verify the configuration for the IP address and default gateway. Correct as necessary.

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::2
   IPv6 Address....................: 2001:DB8:ACAD:1::2
   IPv4 Address....................: 172.16.2.3
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: FE80::1
                                     172.16.2.1

The IP address, subnet mask and default gateway of PC-A are correct (172.16.2.3/24, gateway 172.16.2.1). No change is needed on PC-A.

b. After correcting the IP addressing issues on PC-A, issue the pings to the web server, default gateway, and other PCs. Were the pings successful? Record the results.

C:\> ping 209.165.201.2

Pinging 209.165.201.2 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 209.165.201.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\> ping 172.16.2.1

Pinging 172.16.2.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 172.16.2.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\> ping 172.16.2.4

Pinging 172.16.2.4 with 32 bytes of data:

Reply from 172.16.2.4: bytes=32 time<1ms TTL=128
Reply from 172.16.2.4: bytes=32 time<1ms TTL=128
Reply from 172.16.2.4: bytes=32 time<1ms TTL=128
Reply from 172.16.2.4: bytes=32 time<1ms TTL=128

Ping statistics for 172.16.2.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\> ping 172.16.1.3

Pinging 172.16.1.3 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 172.16.1.3:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\> ping 172.16.1.4

Pinging 172.16.1.4 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 172.16.1.4:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

To web server (209.165.201.2)?
No

Ping to default gateway (172.16.2.1)?
No

Ping to PC-B?
Yes

To PC-01?
No

To PC-02?
No

c. Navigate to www.cisco.pka using the web browser on PC-A. Record the results.

Can PC-A access www.cisco.pka?
No

Using the web server IP address?
No

d. Document the issues and provide the solution(s). Correct the issues if possible.
PC-A can only access the local LAN. The interface G0/1 on router R1 is incorrectly configured. Correct the IP address on interface G0/1. Access router R1 using SSH from PC-01 or PC-02 to change the IP address from 172.16.3.1 to 172.16.2.1.

How to reach R1

Start from Method Login Why this PC
PC-01 or PC-02 (after Fix 1 / Fix 2) SSH to 172.16.1.1 (R1 G0/0) Username Admin01, password cisco12345 Their LAN reaches R1 G0/0. PC-A and PC-B cannot reach R1, because their gateway address 172.16.2.1 does not exist yet.

Note: The SSH session uses R1 G0/0, so changing the G0/1 address does not drop it.

On PC-01, go to Desktop tab -> Telnet / SSH Client


17.7.6 PC-01 Desktop Telnet / SSH Client
Enter the IP address (172.16.1.1), username (Admin01) and password (cisco12345):
17.7.6 SSH Client login to R1 as Admin01
17.7.6 SSH session to R1 opened from PC-01
Or open the Command Prompt on PC-01 and connect with SSH (password cisco12345):

C:\> ssh -l Admin01 172.16.1.1

Password:

Warning: Unauthorized Access is Prohibited.

R1#

Note: The password cisco12345 is not displayed while you type it. The session opens directly at the privileged EXEC prompt R1#, so no enable password is needed.
Check the interface addresses of R1 before changing anything:

R1# show ip interface brief
Interface              IP-Address      OK? Method Status                Protocol
GigabitEthernet0/0     172.16.1.1      YES manual up                    up
GigabitEthernet0/1     172.16.3.1      YES manual up                    up
Serial0/0/0            209.165.200.226 YES manual up                    up
Serial0/0/1            unassigned      YES unset  down                  down
Vlan1                  unassigned      YES unset  administratively down down

Fix 3: Enter the command below to change the IP address from 172.16.3.1 to 172.16.2.1.

R1(config)# interface gigabitethernet 0/1
R1(config-if)# ip address 172.16.2.1 255.255.255.0
R1# show ip interface brief
Interface              IP-Address      OK? Method Status                Protocol
GigabitEthernet0/0     172.16.1.1      YES manual up                    up
GigabitEthernet0/1     172.16.2.1      YES manual up                    up
Serial0/0/0            209.165.200.226 YES manual up                    up
Serial0/0/1            unassigned      YES unset  down                  down
Vlan1                  unassigned      YES unset  administratively down down

On PC-A, verify the fix:

C:\> ping 172.16.2.1

Pinging 172.16.2.1 with 32 bytes of data:

Reply from 172.16.2.1: bytes=32 time<1ms TTL=255
Reply from 172.16.2.1: bytes=32 time<1ms TTL=255
Reply from 172.16.2.1: bytes=32 time<1ms TTL=255
Reply from 172.16.2.1: bytes=32 time<1ms TTL=255

Ping statistics for 172.16.2.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\> ping 209.165.201.2

Pinging 209.165.201.2 with 32 bytes of data:

Reply from 209.165.201.2: bytes=32 time=8ms TTL=126
Reply from 209.165.201.2: bytes=32 time=8ms TTL=126
Reply from 209.165.201.2: bytes=32 time=7ms TTL=126
Reply from 209.165.201.2: bytes=32 time=1ms TTL=126

Ping statistics for 209.165.201.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 8ms, Average = 6ms

C:\> ping 172.16.1.3

Pinging 172.16.1.3 with 32 bytes of data:

Reply from 172.16.1.3: bytes=32 time<1ms TTL=127
Reply from 172.16.1.3: bytes=32 time<1ms TTL=127
Reply from 172.16.1.3: bytes=32 time<1ms TTL=127
Reply from 172.16.1.3: bytes=32 time<1ms TTL=127

Ping statistics for 172.16.1.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms


What we learned:
R1 G0/1 was up/up but had the address 172.16.3.1, which is not in the LAN 172.16.2.0/24 (so no shutdown is not needed), so PC-A and PC-B had no working default gateway. After the fix, LAN 172.16.2.0/24 reaches the other LAN and the web server.

Step 4: Determine the connectivity issue between PC-B and web server.

a. On PC-B, open the command prompt. Enter the command ipconfig to verify the configuration for the IP address and default gateway. Correct as necessary.

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::4
   IPv6 Address....................: 2001:DB8:ACAD:1::4
   IPv4 Address....................: 172.16.2.4
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: FE80::1
                                     172.16.2.1

The ipconfig command does not show the DNS server. Use ipconfig /all:

C:\> ipconfig /all

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Physical Address................: 0001.6384.B18C
   Link-local IPv6 Address.........: FE80::4
   IPv6 Address....................: 2001:DB8:ACAD:1::4
   IPv4 Address....................: 172.16.2.4
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: FE80::1
                                     172.16.2.1
   DHCP Servers....................: 0.0.0.0
   DHCPv6 IAID.....................:
   DHCPv6 Client DUID..............: 00-01-00-01-8D-89-37-EC-00-01-63-84-B1-8C
   DNS Servers.....................: 2001:DB8:CAFE::3
                                     209.165.201.4

b. After correcting the IP addressing issues on PC-B, issue the pings to the web server, default gateway, and other PCs. Were the pings successful? Record the results.
Note: These pings succeed only after Fix 3. Before it, the wrong R1 G0/1 address hides the DNS problem of PC-B, because PC-B cannot reach any other network.

C:\> ping 209.165.201.2

Pinging 209.165.201.2 with 32 bytes of data:

Reply from 209.165.201.2: bytes=32 time=1ms TTL=126
Reply from 209.165.201.2: bytes=32 time=6ms TTL=126
Reply from 209.165.201.2: bytes=32 time=7ms TTL=126
Reply from 209.165.201.2: bytes=32 time=9ms TTL=126

Ping statistics for 209.165.201.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 9ms, Average = 5ms

C:\> ping 172.16.2.1

Pinging 172.16.2.1 with 32 bytes of data:

Reply from 172.16.2.1: bytes=32 time<1ms TTL=255
Reply from 172.16.2.1: bytes=32 time<1ms TTL=255
Reply from 172.16.2.1: bytes=32 time<1ms TTL=255
Reply from 172.16.2.1: bytes=32 time<1ms TTL=255

Ping statistics for 172.16.2.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\> ping 172.16.2.3

Pinging 172.16.2.3 with 32 bytes of data:

Reply from 172.16.2.3: bytes=32 time<1ms TTL=128
Reply from 172.16.2.3: bytes=32 time<1ms TTL=128
Reply from 172.16.2.3: bytes=32 time<1ms TTL=128
Reply from 172.16.2.3: bytes=32 time<1ms TTL=128

Ping statistics for 172.16.2.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\> ping 172.16.1.3

Pinging 172.16.1.3 with 32 bytes of data:

Reply from 172.16.1.3: bytes=32 time<1ms TTL=127
Reply from 172.16.1.3: bytes=32 time<1ms TTL=127
Reply from 172.16.1.3: bytes=32 time<1ms TTL=127
Reply from 172.16.1.3: bytes=32 time=1ms TTL=127

Ping statistics for 172.16.1.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\> ping 172.16.1.4

Pinging 172.16.1.4 with 32 bytes of data:

Reply from 172.16.1.4: bytes=32 time<1ms TTL=127
Reply from 172.16.1.4: bytes=32 time<1ms TTL=127
Reply from 172.16.1.4: bytes=32 time<1ms TTL=127
Reply from 172.16.1.4: bytes=32 time<1ms TTL=127

Ping statistics for 172.16.1.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

To web server (209.165.201.2)?
Yes

Ping to default gateway (172.16.2.1)?
Yes

Ping to PC-A?
Yes

To PC-01?
Yes

To PC-02?
Yes

c. Navigate to www.cisco.pka using the web browser. Record the results.
17.7.6 PC-B web browser cannot open www.cisco.pka

To see why the name does not work, ask the DNS server directly:

C:\> nslookup www.cisco.pka

Server: [2001:DB8:CAFE::3]
Address:  2001:DB8:CAFE::3
DNS request timed out.
	timeout was 15000 milli seconds.

Server: [2001:DB8:CAFE::3]
Address:  2001:DB8:CAFE::3
DNS request timed out.
	timeout was 15000 milli seconds.

Server: [2001:DB8:CAFE::3]
Address:  2001:DB8:CAFE::3
*** UnKnown can't find www.cisco.pka: Non-existent domain.

Can PC-B access www.cisco.pka?
No

Using the web server IP address?
Yes

d. Document the issues and provide the solution(s). Correct the issues if possible.
PC-B can access the web server using the IP address only. PC-B is also configured with the correct DNS2 server address. This indicates that the DNS2 server may be incorrectly configured. To resolve this issue temporarily, the DNS server address can be configured to use 209.165.201.3. The issue with the DNS2 server needs to be escalated because you do not have administrative access to devices outside your network.

Fix 4: On PC-B, click Desktop > IP Configuration and change the DNS Server to 209.165.201.3 (DNS1). This is a temporary fix; the DNS2 problem must still be escalated.
17.7.6 PC-B IP Configuration with DNS server 209.165.201.3
Verify the new DNS server:

C:\> ipconfig /all

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Physical Address................: 0001.6384.B18C
   Link-local IPv6 Address.........: FE80::4
   IPv6 Address....................: 2001:DB8:ACAD:1::4
   IPv4 Address....................: 172.16.2.4
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: FE80::1
                                     172.16.2.1
   DHCP Servers....................: 0.0.0.0
   DHCPv6 IAID.....................:
   DHCPv6 Client DUID..............: 00-01-00-01-8D-89-37-EC-00-01-63-84-B1-8C
   DNS Servers.....................: 2001:DB8:CAFE::3
                                     209.165.201.3
C:\> nslookup www.cisco.pka

Server: [209.165.201.3]
Address:  209.165.201.3

Non-authoritative answer:
Name:   www.cisco.pka
Address:   209.165.201.2

After the change, PC-B opens www.cisco.pka:
17.7.6 PC-B web browser opens www.cisco.pka after the DNS fix

What we learned:
PC-B reaches the web server by IP address, so routing works. PC-B uses DNS servers 2001:DB8:CAFE::3 and 209.165.201.4 (DNS2); nslookup times out and then reports a non-existent domain, so the name www.cisco.pka cannot be resolved. After the change, DNS1 (209.165.201.3) returns 209.165.201.2 for www.cisco.pka. The IPv6 DNS entry 2001:DB8:CAFE::3 is left unchanged: replacing only the IPv4 DNS server 209.165.201.4 with 209.165.201.3 is enough, as the nslookup and web browser results show. DNS2 is in the cloud and cannot be repaired from your network, so PC-B is pointed to DNS1 and the DNS2 fault is escalated.

e. Could all the issues be resolved on PC-B and still make use of DNS2? If not, what would you need to do?
No. DNS2 apparently has configuration issues. You would need to contact the person in charge of the DNS2 server and report your findings.

Step 5: Verify connectivity.

Verify that all the PCs can access the web server www.cisco.pka. Your completion percentage should be 100%. If not, click Check Results to see which required components are not yet completed.
Note: Open Desktop > Web Browser on PC-01, PC-02, PC-A and PC-B and browse to http://www.cisco.pka. Every PC should display the web page.
17.7.6 PC-A web browser opens www.cisco.pka after the R1 fix

Issues Found and Solutions

# Device Issue Solution
1 PC-01 Wrong IP address (172.168.1.3; the second octet is incorrect) Change the IP address to 172.16.1.3
2 PC-02 Wrong default gateway (172.16.1.11) Change the default gateway to 172.16.1.1
3 R1 G0/1 Wrong interface IP address (172.16.3.1) Change it to 172.16.2.1 (CLI over SSH)
4 PC-B DNS server points to DNS2, which is faulty Point DNS to 209.165.201.3 (DNS1) as a temporary fix, then escalate

Device Configs - Final

ROUTER R1

! ==============================================================
!--- 17.7.6 Packet Tracer - Troubleshoot Connectivity Issues
!--- FIX SCRIPT FOR ROUTER R1
!--- Usage: R1 can only be reached over SSH. On PC-01 (after fixing its IP address) open Desktop > Telnet / SSH Client, connect to 172.16.1.1 with username Admin01 and password cisco12345 (or run "ssh -l Admin01 172.16.1.1" in Command Prompt). The session lands directly at R1#; paste this file there (the "enable" line below is harmless at R1#). This is a troubleshooting activity: the script contains only the fix for R1. Every line beginning with "!" is a comment; IOS ignores it.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Step 3: Determine the connectivity issue between PC-A and web server.
! --------------------------------------------------------------

!--- Step 3d: G0/1 is configured with 172.16.3.1, so PC-A and PC-B have no working default gateway. Replace it with 172.16.2.1/24 from the Addressing Table (a new primary IPv4 address replaces the old one). The SSH session runs through G0/0, so it is not dropped.
interface gigabitethernet 0/1
 ip address 172.16.2.1 255.255.255.0
 exit

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   show ip interface brief  -> GigabitEthernet0/1 172.16.2.1 up/up
!---   From PC-A: ping 172.16.2.1 and ping 209.165.201.2 -> replies
!--- Note: the PC fixes (PC-01 IP address, PC-02 default gateway, PC-B DNS server) are made in Desktop > IP Configuration.
! ==============================================================

PC-01

PC-01PC
IP Address172.16.1.3
Subnet Mask255.255.255.0
Default Gateway172.16.1.1
Command Promptipconfig 172.16.1.3 255.255.255.0 172.16.1.1

PC-02

PC-02PC
IP Address172.16.1.4
Subnet Mask255.255.255.0
Default Gateway172.16.1.1
Command Promptipconfig 172.16.1.4 255.255.255.0 172.16.1.1

PC-B

PC-BPC
IP Address172.16.2.4
Subnet Mask255.255.255.0
Default Gateway172.16.2.1
DNS Server209.165.201.3
Command Promptipconfig 172.16.2.4 255.255.255.0 172.16.2.1

Download Packet Tracer (.pka) file:

Subscribe
Notify of
guest

2 Corrections & Clarifications