CHAPTER 1

INTRODUCTION OF CISCO PACKET TRACER

What is Packet Tracer?

Packet Tracer is a protocol simulator developed by Dennis Frezzo and his team at Cisco
Systems. Packet Tracer (PT) is a powerful and dynamic tool that displays the various
protocols used in networking, in either Real Time or Simulation mode. This includes layer 2
protocols such as Ethernet and PPP, layer 3 protocols such as IP, ICMP, and ARP, and layer
4 protocols such as TCP and UDP. Routing protocols can also be traced.

Purpose:
The purpose of this lab is to become familiar with the Packet Tracer interface. Learn how to
use existing topologies and build your own.

Requisite knowledge:
This lab assumes some understanding of the Ethernet protocol. At this point we have not
discussed other protocols, but will use Packet Tracer in later labs to discuss those as well.

Version: This lab is based on Packet Tracer 4.0 Beta, Test1.

Opportunity
As networking systems continue to evolve in complexity, new curricula and educational tools
are emerging to facilitate teaching and learning about networking technology. The Cisco
Networking Academy® program is designed to keep pace with the evolution of networking
systems by providing innovative curricula and educational tools that help students understand
the complexities of information and communication technologies (ICTs). Within this
framework, the Cisco® Packet Tracer e-learning software was developed to help Networking
Academy students gain practical networking technology skills in a rapidly changing
environment. Students seeking ICT skills can now benefit from the accessibility of online
curricula and new opportunities for social learning, collaboration, and competition.

Page 1 of 33
Solution
Cisco® Packet Tracer is a powerful network simulation program that allows students to
experiment with network behaviour and ask “what if” questions. As an integral part of the
Networking Academy comprehensive learning experience, Packet Tracer provides
simulation, visualization, authoring, assessment, and collaboration capabilities to facilitate
the teaching and learning of complex technology concepts.
Packet Tracer supplements physical equipment in the classroom by allowing students to
create a network with an almost unlimited number of devices, encouraging practice,
discovery, and troubleshooting. The simulation-based learning environment helps students
develop 21st century skills such as decision making, creative and critical thinking, and
problem solving. Packet Tracer complements the Networking Academy curricula, allowing
instructors to easily teach and demonstrate complex technical concepts and networking
systems design. Instructors can customize individual or multiuser activities, providing
hands-on lessons for students that offer value and relevance in their classrooms. Students can
build, configure, and troubleshoot networks using virtual equipment and simulated
connections, alone or in collaboration with other students. Packet Tracer offers an effective,
interactive environment for learning networking concepts and protocols. Most importantly,
Packet Tracer helps students and instructors create their own virtual “network worlds” for
exploration, experimentation, and explanation of networking concepts and technologies.

Page 2 of 33
 Figure. Packet Tracer’s drag-and-drop interface allows students to configure and
validate system architecture.

CHAPTER 2

NEED OF CISCO PACKET TRACER

The Teaching Experience

Cisco Packet Tracer provides multiple opportunities for instructors to demonstrate

networking concepts. Although Packet Tracer is not a substitute for real equipment, it allows
students to practice using a command-line interface. This “e-doing” capability is a
fundamental component of learning how to configure routers and switches. Packet Tracer’s
simulation mode enables instructors to demonstrate processes that were formerly hidden to
students. These simulation capabilities can help simplify the learning process by providing
tables, diagrams, and other visual representations of internal functions such as dynamic data
transfers and packet content expansion. The simulation mode also decreases instructor
presentation time by replacing whiteboards and static slides with real-time visuals. Packet
Tracer helps instructors teach complex networking concepts in the following ways:
• Provides a visual demonstration of complex technologies and configurations

Page 3 of 33
• Allows instructors to author customized, guided activities that provide immediate feedback
using the Activity Wizard
• Facilitates numerous learning activities such as lectures, individual and group lab activities,
homework, assessments, games, network design, troubleshooting, modelling tasks, case
studies, and competitions
• Enables visualization, animation, and detailed modelling for exploration, experimentation,
and explanation
• Supports self-paced learning outside the classroom
• Supports social learning processes by enabling collaboration and competition
• Supports the majority of protocols and technologies taught in the following Networking
Academy curricula: Cisco CCNA® Discovery, CCNA Exploration, and CCNA Security, and
can be used to teach concepts from IT Essentials and Cisco CCNP® courses.

The Student Experience

Students who spend more time in a hands-on mode of learning, with simulation and
interactive capabilities, will be better equipped to apply concepts and configuration
fundamentals when exposed to real equipment. As students gain practical experience with
tasks such as configuration and troubleshooting, they become more confident in their
abilities. Cisco Packet Tracer’s multiuser functionality also provides an opportunity for social
learning, allowing students to collaborate and compete with each other and play games that
enhance the learning experience.

Page 4 of 33
Figure. Multiuser games provide fun learning opportunities for collaboration and
competition.

Page 5 of 33
Figure. The physical workspace provides a graphical view of the logical network

Page 6 of 33
 CHAPTER 3
Cisco Packet Tracer Modes

Cisco Packet Tracer provides two operating modes to visualize the behaviour of a network

 Real-time mode
 Simulation mode.

 In real-time mode the network behaves as real devices do, with immediate real-time
response for all network activities. The real-time mode gives students a viable alternative
to real equipment and allows them to gain configuration practice before working with real
equipment.

 In simulation mode the user can see and control time intervals, the inner workings of data
transfer, and the propagation of data across a network. This helps students understand the
fundamental concepts behind network operations. A solid understanding of network
fundamentals can help accelerate learning about related concepts.

Protocols
Cisco Packet Tracer supports the following protocols:

Layer Cisco Packet Tracer Supported Protocols

Modular Devices: Graphical representations visually simulate hardware and offer the ability
to insert interface cards into modular routers and switches, which then become part of the
simulation.
Multiuser Functionality: Cisco Packet Tracer is a network-capable application, with a
multiuser peer-to-peer mode that allows collaborative construction of virtual networks over a
real network. The multiuser feature enables exciting collaborative and competitive
Page 7 of 33
interactions, providing the option to progress from individual to social learning and features
opportunities for collaboration, competition, remote instructor student interactions, social
networking, and gaming.
Tutorials: Packet Tracer includes several basic step-by-step tutorials that familiarize users
with the product features and explain how to engage in simulations. Additional advanced
tutorials are available for download from Academy Connection.
Help: A help feature is available to familiarize users with the Cisco Packet Tracer interface,
functions, and features. The help area includes important notes and tips and provides
annotated screenshots to aid understanding.
Activity Wizard: The Activity Wizard allows users to author their own learning activities by
setting up scenarios using instructional text, and creating initial and final network topologies
and predefined packets. The Activity Wizard also includes grading and feedback capabilities.

Figure. The Activity Wizard enables the creation of customized learning activities

Additional Features
• Lab grading function
• International language support
• Compatible with the following platforms:
 Windows, Windows XP; Vista (Vista Basic, Vista Premium); Windows 7; and Linux
(Ubuntu, Fedora)
• Available to registered Networking Academy instructors, students, and alumni.

Page 8 of 33
 CHAPTER 4
WORKING IN CISCO PACKET TRACER
Introduction to the Packet Tracer Interface using a Hub Topology

Step 1: Start Packet Tracer and Entering Simulation Mode

Step 2: Choosing Devices and Connections

We will begin building our network topology by selecting devices and the media in which to
connect them.
Several types of devices and network connections can be used. For this lab we will keep it
simple by using End Devices, Switches, Hubs, and Connections.

Single click on each group of devices and connections to display the various choices.

Step 3: Building the Topology – Adding Hosts Single click

Page 9 of 33
Step 3: Building the Topology – Adding Hosts

Single click on the End Devices.

Page 10 of 33
Move the cursor into topology area. You will notice it turns into a plus “+” sign.
Single click in the topology area and it copies the device.

Page 11 of 33
Step 4: Building the Topology – Connecting the Hosts to Hubs and Switches
Adding a Hub
Select a hub, by clicking once on Hubs and once on a Generic hub.

Page 12 of 33
Perform the following steps to connect PC0 to Hub0:
1. Click once on PC0
2. Choose Fast Ethernet
3. Drag the cursor to Hub0
4. Click once on Hub0 and choose Port 0
5. Notice the green link lights on both the PC0 Ethernet NIC and the Hub0 Port 0 showing
that the link is active.

Adding a Switch
Select a switch, by clicking once on Switches and once on a 2950-24 switch.

Page 13 of 33
Add the switch by moving the plus sign “+” below PC2 and PC3 and click once.

Connect PC2 to Hub0 by first choosing Connections.

Click once on the Copper Straight-through cable.

Perform the following steps to connect PC2 to Switch0:

1. Click once on PC2
2. Choose FastEthernet
3. Drag the cursor to Switch0
4. Click once on Switch0 and choose FastEthernet0/1
5. Notice the green link lights on PC2 Ethernet NIC and amber light Switch0 FastEthernet0/1
port. The switch port is temporarily not forwarding frames, while it goes through the stages
for the Spanning Tree Protocol (STP) process.

Page 14 of 33
6. After a about 30 seconds the amber light will change to green indicating that the port has
entered the forwarding stage. Frames can now forwarded out the switch port.

Step 5: Configuring IP Addresses and Subnet Masks on the Hosts

Before we can communicate between the hosts we need to configure IP Addresses and
Subnet Masks on the devices.
Click once on PC0.

Page 15 of 33
Choose the Config tab. It is here that you can change the name of PC0. It is also here where
you would enter a Gateway IP Address, also known as the default gateway. We will discuss
this later, but this would be the IP address of the local router. If you want, you can enter the
IP Address 172.16.1.1, although it will not be used in this lab.

Click on FastEthernet. Although we have not yet discussed IP Addresses, add the IP
Address to 172.16.1.10. Click once in the Subnet Mask field to enter the default Subnet
Mask. You can leave this at 255.255.0.0. We will discuss this later.

Page 16 of 33
Also, notice this is where you can change the Bandwidth (speed) and Duplex of the Ethernet
NIC (Network Interface Card). The default is Auto (auto negotiation), which means the NIC
will negotiate with the hub or switch. The bandwidth and/or duplex can be manually set by
removing the check from the Auto box and choosing the specific option.

Bandwidth - Auto
If the host is connected to a hub or switch port which can do 100 Mbps, then the Ethernet
NIC on the host will choose 100 Mbps (Fast Ethernet). Otherwise, if the hub or switch port
can only do 10 Mbps, then the Ethernet NIC on the host will choose 10 Mbps (Ethernet).

Duplex - Auto
Hub: If the host is connected to a hub, then the Ethernet NIC on the host will choose Half
Duplex.
Switch: If the host is connected to a switch, and the switch port is configured as Full Duplex
(or Auto negotiation), then the Ethernet NIC on the host will choose Full Duplex. If the
switch port is configured as Half Duplex, then the Ethernet NIC on the host will choose Half
Duplex. (Full Duplex is a much more efficient option.)
The information is automatically saved when entered.

Page 17 of 33
Repeat these steps for the other hosts. Use the information below for IP Addresses and
Subnet Masks.

Host IP Address Subnet Mask

PC0 172.16.1.10 255.255.0.0
PC1 172.16.1.11 255.255.0.0
PC2 172.16.1.12 255.255.0.0
PC3 172.16.1.13 255.255.0.0

Verify the information

To verify the information that you entered, move the Select tool (arrow) over each host.

Deleting a Device or Link

To delete a device or link, choose the Delete tool and click on the item you wish to delete.

Step 6: Connecting Hub0 to Switch0

To connect like-devices, like a Hub and a Switch, we will use a Cross-over cable. Click once
the Cross-over Cable from the Connections options.

Page 18 of 33
Move the Connections cursor to Switch0.

Click once on Switch0 and choose FastEthernet0/4 (actual port does not matter).

The link light for switch port FastEthernet0/4 will begin as amber and eventually change to
green as the Spanning Tree Protocol transitions the port to forwarding.

Page 19 of 33
 CHAPTER 5

PROTOTYPING A NETWORK
Objectives
• Prototype a network using Packet Tracer

Background
A client has requested that you set up a simple network with two PCs connected to a switch.
Verify that the hardware, along with the given configurations, meet the requirements of the
client.

Step 1: Set up the network topology

a) Add two PCs and a Cisco 2950T switch.
b) Using straight-through cables connect PC0 to interface Fa0/1 on Switch0 and PC1 to
interface Fa0/2 on Switch0.
c) Configure PC0 using the Config tab in the PC0 configuration window:
1. IP address: 192.168.10.10
2. Subnet Mask 255.255.255.0
d) Configure PC1 using the Config tab in the PC1 configuration window:
1. IP address: 192.168.10.11
2. Subnet Mask 255.255.255.0

Step 2: Test connectivity from PC0 to PC1

a) Use the ping command to test connectivity.
1. Click PC0.
2. Choose the Desktop tab.
3. Choose Command Prompt.
4. Type: ping 192.168.10.11 and press enter.
b) A successful ping indicates the network was configured correctly and the prototype
validates the hardware and software configurations. A successful ping should resemble the
below output:
PC>ping 192.168.10.11
Pinging 192.168.10.11 with 32 bytes of data:
Reply from 192.168.10.11: bytes=32 time=170ms TTL=128
Reply from 192.168.10.11: bytes=32 time=71ms TTL=128
Reply from 192.168.10.11: bytes=32 time=70ms TTL=128
Reply from 192.168.10.11: bytes=32 time=68ms TTL=128
Ping statistics for 192.168.10.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 170ms, Average = 94ms
Close the configuration window.
c) Click the Check Results button at the bottom of the instruction window to check your
work.

Page 20 of 33
 CHAPTER 6

Observing Packets Across the Network

Objectives
• Use ping and tracert to verify connectivity from source to destination.
This activity will begin showing 100% completion. This is because the activity is designed
to demonstrate the behaviour of ping and tracert. This activity is not designed to be graded.

Background
A network administrator wants to verify the path a packet takes to get to a destination web
server.
Step 1: Verify connectivity from the source host to the destination host
a) Open the source host command prompt window and ping the destination
1. Select PC0.
2. Select the Desktop tab > Command Prompt
3. Type: ping 192.168.3.2 and press enter.
*A Reply verifies connectivity from the host to the destination device. It does not indicate the
path that was taken to reach it.
**The first few pings may time out while devices load. If all pings time out, repeat the
command.

Step 2: Determine the path taken to the destination using tracert

a) From within the same Command Prompt window for PC0, type tracert 192.168.3.2 and
press enterI.
*The tracert should display four hops, the fourth hop is the actual destination. This not only
verifies connectivity between the devices, but also provides the exact path the packets
traveled to reach it.
b) Close the PC0 configuration window.

Step 3: View the packet path in simulation mode

a) Open the simulation window by clicking the Simulation tab. It is located behind the Real
time time tab in the lower right-hand corner.
b) Click the Add Simple PDU button. This is the closed envelope located on the right-hand
side of the screen. Once this is selected, click PC0 and PC1. This will create a ping packet
from source to destination
c) Click the Edit Filters button to open the filter list. Ensure that only ICMP is checked.
d) In the work area window, click the network cloud to expand it and view router devices
connected within the cloud. The source and destination devices are off screen. The focus is
on the Routers within the network cloud only and packets forwarded between these devices.
e) Use the Auto Capture / Play button in the Simulation Panel window and observe the path
the packet travels to reach the destination.
*Notice within the Event List, there are three routers used between source and destination.
This is the same path indicated in the earlier PC command prompt window using the tracert
command.

Page 21 of 33
 CHAPTER 7

Connecting to a Web Server Using IP

Objective
• Observe how packets are sent across the Internet using IP addresses
This activity will begin showing 100% completion. This is because the activity is designed
to demonstrate how to connect to a web server using IP. This activity is not designed to be
graded.

Step 1: Verify connectivity to the web server

a) Open the source host command prompt window.
1. Select PC0.
2. Select the Desktop Tab > Command Prompt.
b) Verify connectivity to the web server.
1. At the command prompt, ping the IP address of the web server by typing ping
172.33.100.50 and pressing the enter key.
*A reply verifies connectivity from the client to the destination web server. The reply may
time out initially while devices load and ARP is performed.
c) Close the command prompt window, by selecting the x in the upper right-hand corner of
the command prompt window. Be sure to leave the PC0 configuration window open.

Step 2: Connect to the Web Server via the web client

a) Open the source host web browser client.
1. From within the PC0 desktop window, select the Web Browser, to open the web
client utility.
b) Type 172.33.100.50 into the URL block and select "Go".
*The web client will connect to the web server via IP address and will open the web site.
c) Close the PC0 configuration window. The activity is complete.

Page 22 of 33
 CHAPTER 8

Configuring DHCP on a Multi-function Device

Objective
• Connect three PCs to a Linksys-WRT300N, which is a multi-function device
• Change the DHCP setting to a specific network range
• Configure the clients to obtain an IP address via DHCP

Background
A home user wants to use a Linksys-WRT300N device to connect three PCs. All three PCs
should obtain an IP address automatically from the Linksys device.

Step 1: Set up the network topology

a) Add three PCs to the work area.
b) Add a Linksys-WRT300N to the work area.
c) Connect each PC to an Ethernet port on the Linksys device using a straight through cable.

Step 2: Observe the default DHCP settings

a) Click the Linksys-WRT300N Router to open the configuration window.
b) Click the Config tab and change the Display Name to DHCP Enabled Router.
*Note: A popup window will appear when changing the Display Name warning that
changing the Display Name may affect scoring. Proceed with changing the Display Name
since it must match exactly for the activity to score correctly.
c) Select the GUI tab.
*This navigates to the Setup / Basic Setup page within the Linksys GUI.
d) Scroll through the Basic Setup page to view default settings, including the default IP
address of the Linksys device.
*Note that DHCP is enabled, the starting address of the DHCP range and the range of
addresses available to clients.

Step 3: Change the default IP address of the Linksys device

a) Within the Router IP section, change the IP address of the Linksys device to: 192.168.5.1.
b) Scroll to the bottom of the GUI page and click Save Settings.
c) Scroll back up to the Router IP section to ensure the change is made.

Step 4: Change the default DHCP range of addresses

a) Notice the starting IP address in the DHCP Server Setting is updated to match the same
network as the IP address of the Linksys device: 192.168.5.100.
b) Change the Starting IP Address from 192.168.5.100 to 192.168.5.26.
c) Change the Maximum Number of Users to 75.
d) Scroll to the bottom of the GUI page and click Save Settings.
e) Scroll back up to the DHCP Setting section to ensure the change is made.

Page 23 of 33
*Notice the range of address available to clients has updated to reflect the change.
f) Close the Linksys configuration window.

Step 5: Configure DHCP on the client workstations

a) Enable DHCP on PC0.
1. Click PC0.
2. Click he Config tab. Go to the Interface FastEthernet sub-menu.
3. Enable DHCP by selecting the DHCP button in the IP Configuration panel.
*Notice that an IP address and subnet mask is automatically assigned.
4. Close the configuration window.
b) Observe the IP configuration of a client that does not have DHCP enabled.
1. Click PC1.
2. Click the Desktop tab > Command Prompt.
3. Type ipconfig and press enter.
*Notice that all settings are set to 0.0.0.0. No IP address is assigned statically, and the PC
has not obtained an address automatically from DHCP.
c) Enable DHCP on PC1 and PC2, using the Config tab as outlined in Step 5a.
*Notice that a different IP address from the one assigned to PC0 is automatically assigned to
PC1 and PC2.
d) Close the configuration window.

Step 6: Verify connectivity

a) Click PC1 and select the Desktop tab > Command Prompt.
b) Type ipconfig to view the IP configuration of PC1.
c) Type ping 192.168.5.1 to ping the Linksys device.
d) Type ping 192.168.5.26 to ping PC0.
*You should receive a reply from both devices.
e) Close the configuration window and click Check Results button at the bottom of the
instruction window to check your work.
f) Choose the Assessment Items tab to view any configurations that were not done correctly.

Page 24 of 33
 CHAPTER 9

Examining NAT on a Multi-function Device

Objective
• Examine the Linksys GUI for NAT configuration
• Set up four PCs to connect to the Linksys device with DHCP enabled.
• Examine traffic that crosses the network using NAT.

Step 1: Examine the Linksys external configuration

a) Click the Linksys device to access the configuration window.
*Note: this may take several seconds.
b) Access the Linksys GUI menu by clicking the GUI tab.
c) Click the Status menu option in the upper right-hand corner. It is the last menu option to
the right on the Linksys GUI page. Once selected, this defaults you to the Router page.
d) Scroll down the Router page to the Internet Connection panel. The IP address assigned
to the Linksys device is assigned by the ISP. If no IP address is present, 0.0.0.0 appears. (The
Linksys device is in the process of obtaining an address from the ISP DHCP server.) If there
is no IP address shown, close the window, wait for a few seconds and try again.
*The address shown is assigned to the Internet port on the Linksys device. Is this a private or
public address?

Step 2: Examine the Linksys internal configuration

a) Click the Local Network sub-menu button within the blue menu bar.
b) Scroll down to examine the Local Network information. This is the address assigned to the
internal Linksys network.
c) Scroll down further to examine the DHCP server information, and range of IP addresses
that can be assigned to connected hosts.
*Are these private or public addresses?
d) Close the Linksys configuration window.

Step 3: Connect four PCs to the Linksys device

a) Add four PCs to the PT work area and connect them to the Linksys device with a straight-
through cable. Wait for all link lights to turn green before moving to the next step. This can
take several seconds.
b) Use the Config tab to enable each device to receive an IP address via the Linksys DHCP
server.
c) Check the IP configuration of each PC using the ipconfig /all command in the Command
Prompt found under the Desktop tab.
*Note: These devices will receive a private address. Private addresses are not able to cross
the Internet, therefore, NAT translation must occur.
d) Close all PC configuration windows.

Page 25 of 33
Step 4: View NAT translation across the Linksys
a) Enter Simulation mode by clicking the Simulation tab in the lower right-hand corner. The
Simulation tab is located behind the Realtime tab and has a stopwatch symbol.
b) View traffic by creating a Complex PDU in Simulation mode
1. From the Simulation Panel, select Edit Filters and check only the boxes for TCP
and HTTP.
2. Add a Complex PDU by clicking the open envelope located above the Simulation
mode icon.
3. Click one of the PCs to specify it as the source.
c) Specify the Complex PDU settings by changing the following within the Create Complex
PDU window:
1. Under PDU Settings > Select Application should be set to HTTP.
2. Click the ciscolearn.nat.com server to specify it as the destination device.
3. For the Source Port type 1000.
4. Under Simulation Settings select Periodic Interval and type 120 seconds.
5. Create the PDU by clicking the box Create PDU in the Create Complex PDU
window.
d) Double click the Simulation Panel to unlock it from the PT window. This allows you to
move the Simulation Panel to view the entire network topology.
e) Observe the traffic flow by clicking the Auto Capture / Play button in the Simulation
Panel. Speed up the animation by using the play control slider.
*When the Buffer Full window appears, close the window by clicking the x in the upper
right-hand corner of the window.

Step 5: View the header information of the packets that travelled across the network
a) Examine the headers of the packets sent between the PC and the web server.
1. In the Simulation Panel, double click the third line down in the Event List. This
displays an envelope in the work area that represents that line.
2. Click the envelope in the work area window to view the packet and header
information.
b) Click the Inbound PDU Details tab. Examine the packet information for the source (SRC)
IP address and destination IP address.
c) Click the Outbound PDU Details tab. Examine the packet information for the source
(SRC) IP address and destination IP address.
*Notice the change in SRC IP address.
d) Click through other event lines to view those headers throughout the process.
e) When finished, click the Check Results button at the bottom of the instruction window to
check your work.

Page 26 of 33
 CHAPTER 10

Observing Web Requests

Objective
View the client/server traffic sent from a PC to a web server when requesting web services.
This activity will begin showing 100% completion. This is because the activity is designed
to demonstrate the flow of packets between a PC and a web server. This activity is not
designed to be graded.

Step 1: Verify connectivity to the web server

a) Click the External Client and access the Command Prompt from the Desktop tab.
b) Use the ping command to reach the URL ciscolearn.web.com.
*Notice that the IP address is included in the ping output. This address is obtained from the
DNS server. All traffic forwarded across the network uses IP address information.
c) Close the Command Prompt window, but leave the External Client desktop window open.

Step 2: Connect to the web server

a) From the desktop window, access the web browser.
b) In the URL block, type ciscolearn.web.com.
*Be sure to read the web page that is displayed. Leave this page open.

Step 3: View the HTML code

a) Click the ciscolearn.web.com server.
b) Click the Config tab > HTTP tab.
c) Compare the text written in the HTML coding on the server to the Web Browser display
page on the External Client. This may require that you re-maximize the External Client
window if it shrunk when you opened the server window.
d) Close both the External Client and web server windows.

Step 4: Observe traffic between the client and the web server
a) Enter Simulation mode by clicking the Simulation tab in the lower right-hand corner. The
Simulation tab is located behind the Realtime tab and has a stopwatch symbol.
b) Double click the Simulation Panel to unlock it from the PT window. This allows you to
move the Simulation Panel to view the entire network topology.
c) View traffic by creating a Complex PDU in Simulation mode.
1. From the Simulation Panel, select Edit Filters and check only the boxes for TCP and
HTTP.
2. Add a Complex PDU by clicking the open envelope located above the Simulation mode
icon.

Page 27 of 33
3. Click the External Client to specify it as the source. The complex PDU window will
appear.
4. Click the ciscolearn.web.com server to specify it as the destination device. Notice the IP
address of the web server will appear in the destination box within the complex PDU
window.
d) Specify the Complex PDU settings by changing the following within the complex PDU
window:
1. Under PDU Settings > Select Application should be set to HTTP.
2. For the Source Port type 1000.
3. Under Simulation Settings select Periodic Interval and type 120 seconds.
4. Create the PDU by clicking the box Create PDU in the Create Complex PDU
window.
e) Observe the traffic flow by clicking the Auto Capture / Play button in the Simulation
Panel. Speed up the animation by using the play control slider.
*When the Buffer Full window appears, close the window using the x.
f) Scroll through the Event List. Notice the number of packets that traveled from source to
destination. HTTP is a TCP protocol, which requires connection establishment and
acknowledgement of receipt of packets, considerably increasing the amount of traffic
overhead.

Page 28 of 33
 CHAPTER 11

Using the Ipconfig Command

Objective
Use the ipconfig command to identify an incorrect configuration on a PC.

Background
A small business owner cannot connect to the Internet with one of the four PCs in the office.
All of the PCs are configured with static IP addressing. Use the ipconfig /all command to
identify which PC is incorrectly configured.

Step 1: Verify configurations

a) Access the Command Prompt on each PC and type the command: ipconfig /all.
b) Examine the IP address, subnet mask, and default gateway configuration on each PC.
*Be sure to record this IP configuration for each PC to help identify any PCs that are
incorrectly configured.

Step 2: Correct any misconfigurations

a) Select the PC that is incorrectly configured and access the Config tab.
b) Click the Desktop tab > IP Configuration tab to correct the misconfiguration.
c) Click the Check Results button at the bottom of the instruction window to check your
work.

Page 29 of 33
 CHAPTER 12

Using the Ping Command

Objective
Use the ping command to identify an incorrect configuration on a PC.

Background
A small business owner learns that the user of PC2 is unable to access a website. All PCs are
configured with static IP addressing. Use the ping command to identify the issue.

Step 1: Verify connectivity

a) Access the Desktop tab > Web Browser of each PC and type the URL
ciscolearn.more.com.
b) Which PCs are unable to connect to the web server?
*Note: All of the devices require time to complete the boot process. Please allow up to one
minute before receiving a web response.

Step 2: Ping the web server from PC2

a) On PC2, access the Command Prompt from the Desktop tab.
b) Type: ping ciscolearn.more.com.
c) Did the ping return a reply? What is the IP address returned, if any?

Step 3: Ping the web server from PC1

a) On PC1, access the Command Prompt from the Desktop tab.
b) Type: ping ciscolearn.more.com.
c) Did the ping return a reply? What is the IP address returned, if any?

Step 4: Ping the IP address of the web server from PC2

a) On PC2, access the Command Prompt from the Desktop tab.
b) Attempt to reach the IP address of the web server with the command ping 192.15.2.10.
c) Did the ping return a reply? If so, then PC2 is able to reach the web server via IP address,
but not domain name. This could indicate a problem with the DNS server configuration on
PC2.

Step 5: Compare the DNS server information on PC2 with other PCs on the local
network
a) Access the Command Prompt of PC1.
b) Using the command ipconfig /all, examine the DNS server configuration on PC1.
c) Access the Command Prompt of PC2.
d) Using the command ipconfig /all, examine the DNS server configuration on PC2. Do the
two configurations match?

Step 6: Make any necessary configuration changes on PC2

a) Using the Config tab of PC2, make any necessary configuration changes.

Page 30 of 33
b) Using the Web Browser within the Desktop tab, connect to ciscolearn.more.com to
verify that configuration changes resolved the problem.
c) Click the Check Results button at the bottom of the instruction window to check your
work.

Page 31 of 33
 CHAPTER 13
Troubleshooting a Wireless Connection
Objective
Identify and correct any misconfiguration of a wireless device.

Background
A small business owner learns that a wireless user is unable to access the network. All of the
PCs are configured with static IP addressing. Identify and resolve the issue.

Step 1: Verify connectivity

a) Access the Desktop > Web Browser of each wireless PC and type ciscolearn.more.com
into the URL. Identify any PCs that are not connecting to the web server.
b) Which wireless PCs are unable to connect to the web server?
*Note: All of the devices require time to complete the boot process. Please allow up to one
minute before receiving a web response.
Step 2: Examine the IP configuration of PCs
a) On the PC that is unable to connect, access the Command Prompt from the Desktop tab.
b) Type the ipconfig /all command.
c) What IP addressing information is available?

Step 3: Examine the Wireless Settings on the Wireless Client

a) Access the Config tab of any PC that is unable to connect.
b) Click the Desktop tab > Wireless tab to examine the wireless settings.
c) Record the SSID, Security Configurations, and IP address Configuration.

Step 4: Examine the Wireless Settings on the Linksys Device

a) Access the Linksys GUI.
b) On the Basic Setup page, examine the DHCP Server Setting configuration. Is DHCP
enabled?
c) Click the Wireless tab.
d) Examine the information under the Wireless tab. What is the SSID? Does it match the
SSID configured on the client?

Page 32 of 33
Page 33 of 33