Addressing Table
Device Interface IP Address Subnet Mask Default Gateway
255.255.255.
R1 G0/0 [Link] 0 N/A
255.255.255.
R1 G0/1 [Link] 0 N/A
Device Interface IP Address Subnet Mask Default Gateway
209.165.200. 255.255.255.
R1 S0/0/0 226 252 N/A
209.165.201. 255.255.255.
R2 G0/0 1 224 N/A
S0/0/0 209.165.200. 255.255.255.
R2 (DCE) 225 252 N/A
PC- 255.255.255.
01 NIC [Link] 0 [Link]
PC- 255.255.255.
02 NIC [Link] 0 [Link]
255.255.255.
PC-A NIC [Link] 0 [Link]
255.255.255.
PC-B NIC [Link] 0 [Link]
209.165.201. 255.255.255. 209.165.20
Web NIC 2 224 1.1
DNS 209.165.201. 255.255.255. 209.165.20
1 NIC 3 224 1.1
DNS 209.165.201. 255.255.255. 209.165.20
2 NIC 4 224 1.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,
[Link] 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 [Link]. Escalate the problem if
necessary.
Router R1 can only be accessed using SSH with the
username Admin01 and password cisco12345.
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.
IP incorrect, change IP address to [Link]
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.
Ping to default gateway ([Link])?
Yes
To web server ([Link])?
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
[Link] and then by using the IP address
[Link]. Record the results.
Can PC-01 access [Link]?
Yes
Using the web server IP address?
Yes
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 [Link] to [Link]. PC-01 cannot successfully ping
the PCs on the [Link]/24 network.
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.
Default Gateway incorrect, change Default Gateway address to [Link]:
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.
Ping to default gateway ([Link])?
Yes
To web server ([Link])?
Yes
Ping to PC-01?
Yes
To PC-A?
No
To PC-B?
No
c. Navigate to [Link] using the web browser on PC-02.
Record the results.
Can PC-02 access [Link]?
Yes.
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 [Link] on PC-02. PC-02
cannot successfully ping the PCs on the [Link]/24 network.
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.
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.
To web server ([Link])?
No
Ping to default gateway ([Link])?
No
Ping to PC-B?
Yes
To PC-01?
No
To PC-02?
No
c. Navigate to [Link] using the web browser on PC-A.
Record the results.
Can PC-A access [Link]?
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 [Link] to [Link].
On PC-01, go to Desktop tab -> Telnet / SSH Client
Enter IP address, Username & Password:
Enter the command below to change the IP address from
[Link] to [Link]
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.
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.
To web server ([Link])?
Yes
Ping to default gateway ([Link])?
Yes
Ping to PC-A?
Yes
To PC-01?
Yes
To PC-02?
Yes
c. Navigate to [Link] using the web browser. Record the
results.
Questions:
Can PC-B access [Link]?
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 DNS-2 server address. This indicates that DNS-2 server may be
incorrectly configured. To resolve this issue temporarily, the DNS server address
can be configured to use [Link].The issue with DNS-2 server needs to be
escalated because you do not have administrative access to devices outside your
network.
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
[Link].
Your completion percentage should be 100%. If not, click Check
Results to see which required components are not yet completed.
