Build a Small Office Network in Packet Tracer

Simulate a two-subnet office network with routing and DHCP in Packet Tracer.

Introduction

30 Second Summary

Every time you send a message to a coworker or print a document from across the office, your data travels through a network of routers, switches, and cables. Understanding how that network works is the foundation of every IT and cloud career.

In this project, you will build a two-department office network inside Cisco Packet Tracer, configuring a router to connect separate subnets and setting up DHCP so devices automatically receive IP addresses.

What You'll Build

A simulated office network with two subnets (Engineering and Sales), a central router providing inter-subnet routing and DHCP, and end-user PCs that communicate across both network segments.

By the end of this project, you'll have:

  • A working multi-subnet network topology with a router, two switches, and four PCs inside Packet Tracer.
  • Hands-on experience with the Cisco IOS command-line interface for configuring IP addressing, DHCP pools, and verifying connectivity.
  • A packet trace visualization showing exactly how data travels between subnets through the router, layer by layer.
  • Secret Mission: Add a third subnet with a web server and test HTTP connectivity across all three network segments.

Are there any prerequisites?

No prior networking experience is required. This project walks you through every step, including installing Cisco Packet Tracer and creating a free account.

Before We Start

Cisco Packet Tracer is a free network simulation tool from Cisco. It lets you build, configure, and test virtual networks without needing any physical hardware.

In this step, you'll create a free account, install Packet Tracer on your Windows PC, and sign in so you're ready to start building your network lab.

In this step, get ready to:
  • Create a free SkillsForAll account (or use your existing NetAcad credentials).
  • Download and install Cisco Packet Tracer on your Windows PC.
  • Sign in and confirm the application opens to a blank workspace.
Create your account and download the installer

Packet Tracer requires a free account to sign in. You'll create one on the Cisco Networking Academy platform, then download the installer from the Resource Hub.

  • Open your web browser and navigate to skillsforall.com.
  • Click Sign Up to create a new account.
  • Enter your email address and create a password.
  • Check your email inbox for a verification link and click it to confirm your account.

Already have an account?

If you already have a NetAcad.com or SkillsForAll.com account, skip the sign-up. You'll use those same credentials to sign into Packet Tracer later.

  • Once your account is confirmed, navigate to the Resource Hub download page at netacad.com/resources/lab-downloads.
  • Click the Windows 64-bit download link.
  • Choose a location to save the installer file (your Downloads folder is fine).

What is SkillsForAll?

SkillsForAll is Cisco's free learning platform. It hosts the Packet Tracer download and provides networking courses.

Your SkillsForAll account doubles as your Packet Tracer login credentials.

Run the Packet Tracer installer

With the installer downloaded, you'll run the setup wizard to install Packet Tracer on your PC.

  • Open your Downloads folder and double-click the Packet Tracer .exe file to launch the installer.
  • Read the license agreement, click I accept the agreement, then click Next.
  • In the Select Destination Location window, leave the default and click Next.
  • In the Select Start Menu Folder window, leave the default and click Next.
  • In the Select Additional Tasks window, leave the defaults and click Next.
  • Click Install to begin the installation.
  • When installation completes, make sure the Launch Cisco Packet Tracer checkbox is checked.
  • Click Finish.

What about the multi-user prompt?

Packet Tracer may ask "Would you like to run multi-user when the application starts?" Click No for now. This is an advanced feature you won't need in this project.

You may also see a Windows Security Alert about network access. You can safely click Cancel or allow access if you prefer.

Installer won't run?

Make sure you downloaded the 64-bit Windows version. Packet Tracer requires Windows 8.1, 10, or 11 (64-bit) with at least 4 GB of RAM and 1.4 GB of free disk space.

If Windows blocks the installer with a SmartScreen warning, click More info and then Run anyway.

help me troubleshoot my Packet Tracer installation on Windows

Sign in and verify your workspace

Packet Tracer needs you to sign in with your SkillsForAll account before you can use it. After signing in, you'll see the blank workspace where you'll build your network.

  • The Cisco Packet Tracer Login window appears automatically after launch.
  • In the Login Server dropdown, make sure Worldwide is selected (this is the default).
  • Click the Cisco Skills For All icon.
  • Your default web browser opens to a login page. Enter your email and password, then click Login.
  • After a successful login, the browser displays: "You have successfully logged in to Cisco Packet Tracer. You may close this tab."
  • Close the browser tab and return to Packet Tracer.

You should now see the Packet Tracer workspace. It has a large blank canvas in the center and a device categories panel at the bottom showing categories like Routers, Switches, and End Devices.

Login not working?

Make sure your pop-up blocker is disabled. Clicking the Skills For All icon opens a new browser tab for authentication. If your browser blocks the pop-up, the login flow cannot complete.

If the login window doesn't appear at all, close Packet Tracer completely and reopen it from the Start Menu.

Try logging in at skillsforall.com in your browser first to confirm your credentials work before retrying in Packet Tracer.

help me sign in to Cisco Packet Tracer with my SkillsForAll account

Your environment is ready. Next up, you'll place routers, switches, and PCs on this workspace to build your two-department office network.

Build the Physical Network Topology

With Packet Tracer installed and ready, it's time to build your network from the ground up. In a real office, you'd rack-mount physical hardware and run cables between floors. Here, you'll simulate that entire process by dragging devices onto a virtual workspace and connecting them with virtual cables.

Your network represents two departments in a company. Engineering and Sales each get their own subnet (a separate segment of the network), connected through a central router.

In this step, get ready to:
  • Place network devices (router, switches, and PCs) on the workspace.
  • Cable all devices together with the correct cable type.
  • Rename devices for easy identification.
Place your network devices

Every network starts with hardware. You'll place one router, two switches, and four PCs to represent the two-department office layout.

  • Look at the bottom-left of the Packet Tracer window. You'll see a row of device category icons.
  • Click the Network Devices category icon (looks like a small switch/router).
  • In the subcategory bar that appears, click Routers.
  • Find the 2911 model in the device list. Click it once, then click anywhere in the center-top area of the workspace to place it.
  • Go back to the subcategory bar and click Switches.
  • Find the 2960 model. Click it once, then click on the left side of the workspace to place your first switch.
  • Click again on the right side of the workspace to place your second switch.
  • Now click the End Devices category icon (looks like a computer monitor).
  • Find PC in the device list. Place two PCs below the left switch and two PCs below the right switch (four total).
  • Press Esc to deselect the device tool when you're done placing.

Why this layout?

The router sits at the top because it connects the two subnets together. Each switch represents one department's local network. PCs connect to their department's switch.

This mirrors how real office networks are structured. Departments get their own network segment, and a router handles traffic between them.

Your workspace should now have 7 devices arranged with the router at the top, switches in the middle, and PCs at the bottom.

Can't find the 2911 router?

Make sure you're clicking Network Devices first (not End Devices), then selecting Routers in the subcategory bar. The 2911 appears in the list of available router models.

help me find and place the 2911 router in Packet Tracer

Cable the devices together

Devices sitting on a workspace can't communicate until you connect them with cables. In Packet Tracer, you choose the cable type and click the specific port on each device to form a connection.

  • Click the Connections category icon at the bottom (looks like a lightning bolt).
  • Select Copper Straight-Through (the solid black line icon).

Why Copper Straight-Through?

Straight-through cables connect different types of devices to each other (router to switch, or PC to switch). Crossover cables connect same-type devices (switch to switch, or router to router). Every connection in this topology is between different device types, so straight-through is correct for all of them.

Now connect the router to both switches. Click carefully on the correct port name when the port list appears.

  • Click the router. A list of ports appears. Select GigabitEthernet0/0.
  • Click the left switch (Engineering). Select GigabitEthernet0/1.
  • Click the router again. Select GigabitEthernet0/1.
  • Click the right switch (Sales). Select GigabitEthernet0/1.

Now connect the PCs to their department switches.

  • Click PC1 (top-left PC). Select FastEthernet0.
  • Click the left switch. Select FastEthernet0/1.
  • Click PC2 (bottom-left PC). Select FastEthernet0.
  • Click the left switch. Select FastEthernet0/2.
  • Click PC3 (top-right PC). Select FastEthernet0.
  • Click the right switch. Select FastEthernet0/1.
  • Click PC4 (bottom-right PC). Select FastEthernet0.
  • Click the right switch. Select FastEthernet0/2.
  • Press Esc to deselect the cable tool.

Look at the link lights (small colored circles) on each connection. The connections between switches and PCs should show green triangles (meaning the link is active). The router connections will show red triangles.

Why are the router lights red?

Router interfaces start in an "administratively down" state by default. Unlike switches (which activate ports automatically), routers require you to manually enable each interface with the no shutdown command. You'll do this in the next step when you configure IP addresses.

PC-to-switch lights not turning green?

Double-check that you used Copper Straight-Through (solid black line), not a crossover or console cable. If you used the wrong cable type, click the cable to select it, press Delete, and reconnect with the correct type.

Also confirm you selected FastEthernet0 on the PC (not a console port) and a FastEthernet0/1 or FastEthernet0/2 port on the switch.

help me fix cable connections that aren't showing green in Packet Tracer

Rename your devices

Default names like "Router0" and "Switch0" get confusing fast. Renaming devices makes your topology readable at a glance.

  • Click the router to open its configuration window.
  • Click the Config tab at the top of the window.
  • In the Display Name field, replace the default text with HQ-Router.
  • Close the router window.
  • Click the left switch, go to the Config tab, and set its Display Name to Eng-Switch.
  • Click the right switch, go to the Config tab, and set its Display Name to Sales-Switch.
  • Click each PC and set their Display Name fields to PC1, PC2, PC3, and PC4 respectively (left-to-right, top-to-bottom).

Your workspace should now display all device names clearly. PC1 and PC2 sit under Eng-Switch on the left. PC3 and PC4 sit under Sales-Switch on the right. HQ-Router connects them at the top.

What should I see?

Your topology should look like an upside-down tree. HQ-Router at the top has two cables going down to Eng-Switch (left) and Sales-Switch (right). Each switch has two cables going down to its pair of PCs.

Green triangles appear on all switch-to-PC connections. Red triangles appear on both router connections. This is expected and correct.

Your physical network is wired up and ready. Next up, you'll bring those red router lights to life by configuring IP addressing on each interface.

Configure IP Addressing on the Router

Your network topology is built and all seven devices are connected. The link lights between switches and PCs are green, but the router connections are still red.

That's because router interfaces are administratively shut down by default in Cisco IOS. In this step, you'll bring them to life by assigning IP addresses and enabling each interface through the router's command-line interface.

In this step, get ready to:
  • Configure GigabitEthernet0/0 as the Engineering subnet gateway.
  • Configure GigabitEthernet0/1 as the Sales subnet gateway.
  • Verify both interfaces are active and correctly addressed.
Open the router CLI and configure the Engineering interface

Each router interface acts as a default gateway for the devices on its subnet. You'll configure GigabitEthernet0/0 first, connecting it to the Engineering network.

  • Click the HQ-Router in your workspace.
  • Click the CLI tab at the top of the device window.
  • Configure the Engineering subnet interface by entering these commands:
enable
configure terminal
hostname HQ-Router
interface GigabitEthernet0/0
description Engineering LAN
ip address 192.168.1.1 255.255.255.0
no shutdown
exit

What do these commands do?

  • enable enters privileged EXEC mode, giving you full access to configuration commands.
  • configure terminal enters global configuration mode where you can change the router's settings.
  • hostname HQ-Router sets the router's display name so it's easier to identify.
  • interface GigabitEthernet0/0 selects the specific port you want to configure.
  • ip address 192.168.1.1 255.255.255.0 assigns this interface the IP 192.168.1.1 with a /24 subnet mask. This becomes the gateway address for all Engineering devices.
  • no shutdown brings the interface online. Without this, the interface stays administratively down.
  • exit returns you to global configuration mode, ready for the next interface.
  • Look at the topology view behind the device window. The link light between HQ-Router and Eng-Switch should turn green.

Still seeing a red link light on the Engineering side?

  • Make sure you typed no shutdown after the IP address line. This is the command that actually activates the interface.
  • Check that you selected GigabitEthernet0/0 (with a zero after the slash, not a one).
  • Verify you entered the full subnet mask 255.255.255.0 (not just the IP address).

Why is my router interface still showing red?

Configure the Sales subnet interface

The second router interface connects to the Sales network on a separate subnet. This gives each department its own address space.

  • Still in the router CLI (you should see the HQ-Router(config)# prompt), configure the Sales interface by entering these commands:
interface GigabitEthernet0/1
description Sales LAN
ip address 192.168.2.1 255.255.255.0
no shutdown
exit

What's different here?

This follows the same pattern as the Engineering interface. The key differences are the interface number (GigabitEthernet0/1 instead of 0/0) and the subnet (192.168.2.0/24 instead of 192.168.1.0/24).

The router now has one foot in each subnet. It can forward traffic between the two because it has a directly connected route to both networks.

  • Check the topology view. The link light between HQ-Router and Sales-Switch should now also turn green.

Sales-Switch link still red?

  • Confirm you typed interface GigabitEthernet0/1 (with a one after the slash, not a zero). Using 0/0 again would overwrite your Engineering config.
  • Make sure the IP address is 192.168.2.1 (on the 2.x subnet, not 1.x).
  • Verify no shutdown appears on its own line after the IP address command.

Help me fix my Sales interface configuration.

✔️ Awesome, I've got everything!

Great. Make sure both link lights are green before continuing.

ⓧ I'd like to double check the full configuration

Here's the complete router configuration you should have at this point. You can compare by running show running-config in the router CLI (type end first if you're still in config mode).

hostname HQ-Router
interface GigabitEthernet0/0
 description Engineering LAN
 ip address 192.168.1.1 255.255.255.0
 no shutdown
interface GigabitEthernet0/1
 description Sales LAN
 ip address 192.168.2.1 255.255.255.0
 no shutdown
Verify the interface configuration

Before moving on, confirm that both interfaces are active and addressed correctly using a single verification command.

  • If you're still in configuration mode (the prompt shows (config)#), type end and press Enter to return to privileged EXEC mode.
  • Run the verification command:
show ip interface brief

What should I see?

You should see a table listing all the router's interfaces. Look for these two rows:

  • GigabitEthernet0/0 with IP 192.168.1.1, Status up, and Protocol up.
  • GigabitEthernet0/1 with IP 192.168.2.1, Status up, and Protocol up.

If any interface shows administratively down, you missed the no shutdown command on that interface. Go back and enter it.

  • Confirm all link lights in the topology view are green. Every connection between all seven devices should now show an active (green) link.

Seeing 'administratively down' for an interface?

  • Re-enter configuration mode by typing configure terminal, then select the problem interface (e.g. interface GigabitEthernet0/0), and type no shutdown.
  • Type end to return to privileged EXEC mode, then run show ip interface brief again to confirm the fix.

My interfaces are not showing up/up. Help me fix this.

Both router interfaces are now live and addressed. Next up, you'll configure DHCP on the router so your PCs can automatically receive IP addresses without manual configuration.

Configure DHCP and Assign Addresses

Your router now has IP addresses on both interfaces, connecting the Engineering and Sales subnets. The next step is making sure each PC gets its own address automatically.

Right now, none of the PCs have IP addresses. You could manually assign one to each device, but in a real office with dozens of machines, that would be tedious and error-prone. Instead, you will configure the router as a DHCP server that hands out addresses automatically.

In this step, get ready to:
  • Create DHCP pools on the router for each subnet.
  • Exclude the router's own addresses from being handed out.
  • Configure all four PCs to receive addresses via DHCP.
Create DHCP pools for both subnets

A DHCP pool is a range of IP addresses the router can give out to devices on a particular subnet. You need one pool for Engineering and one for Sales.

  • Click HQ-Router in your topology, then go to the CLI tab.
  • Create both DHCP pools by entering these commands:
configure terminal
ip dhcp pool ENGINEERING
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 8.8.8.8
exit
ip dhcp pool SALES
network 192.168.2.0 255.255.255.0
default-router 192.168.2.1
dns-server 8.8.8.8
exit

What do these commands do?

  • configure terminal enters global configuration mode so you can make changes to the router.
  • ip dhcp pool ENGINEERING creates a named pool of addresses for the Engineering subnet.
  • network 192.168.1.0 255.255.255.0 tells the pool which subnet it serves.
  • default-router 192.168.1.1 tells PCs to use this address as their gateway (the door to other networks).
  • dns-server 8.8.8.8 gives PCs a DNS server address so they can resolve domain names.
  • exit leaves the pool configuration and returns to global config mode, ready for the next pool.

You will not see a change on the topology yet. The pools are ready but no PC has requested an address.

Seeing an "Invalid input" error?

  • Make sure you are in global configuration mode (the prompt reads HQ-Router(config)#). If you see HQ-Router# instead, type configure terminal first.
  • Check that you typed ip dhcp pool ENGINEERING with a space between pool and the pool name.

Still stuck? Help me fix an invalid input error on the router CLI.

Exclude router addresses from DHCP distribution

The router's own interface addresses (192.168.1.1 and 192.168.2.1) live inside the pool ranges you just created. You need to exclude them so the router does not accidentally give its own address to a PC.

  • Exclude both gateway addresses and exit configuration mode by entering these commands:
ip dhcp excluded-address 192.168.1.1
ip dhcp excluded-address 192.168.2.1
end

What does this do?

ip dhcp excluded-address reserves a specific IP so the DHCP server never offers it to a client. The end command exits all configuration modes and returns you to privileged EXEC mode (HQ-Router#).

  • Verify your DHCP setup is ready by running:
show running-config | section dhcp

You should see both pool names (ENGINEERING and SALES) and both excluded addresses listed.

Command not recognized?

Make sure you typed end before running the show command. Show commands only work in privileged EXEC mode (the HQ-Router# prompt), not in configuration mode.

Need more help? Help me verify my DHCP configuration on the router.

✔️ Awesome, I've got everything!

Great. Double check you see both pools and both excluded addresses, then move on to configure the PCs.

ⓧ I'd like to double check the full config

Here is the complete router configuration you should have at this point:

hostname HQ-Router
ip dhcp excluded-address 192.168.1.1
ip dhcp excluded-address 192.168.2.1
ip dhcp pool ENGINEERING
 network 192.168.1.0 255.255.255.0
 default-router 192.168.1.1
 dns-server 8.8.8.8
ip dhcp pool SALES
 network 192.168.2.0 255.255.255.0
 default-router 192.168.2.1
 dns-server 8.8.8.8
interface GigabitEthernet0/0
 description Engineering LAN
 ip address 192.168.1.1 255.255.255.0
 no shutdown
interface GigabitEthernet0/1
 description Sales LAN
 ip address 192.168.2.1 255.255.255.0
 no shutdown
Set each PC to use DHCP

With the router pools ready, each PC just needs to be told to request an address automatically instead of waiting for a manual assignment.

  • Click PC1 in your topology.
  • Go to the Desktop tab at the top of the device window.
  • Click IP Configuration.
  • Select the DHCP radio button (instead of Static).
  • Wait a few seconds for the fields to populate with an IP address, subnet mask, default gateway, and DNS server.

PC1 should receive an address in the 192.168.1.x range with gateway 192.168.1.1.

  • Repeat the same process for PC2, PC3, and PC4.

What addresses should each PC get?

  • PC1 and PC2 are connected to Eng-Switch, so they receive 192.168.1.x addresses with gateway 192.168.1.1.
  • PC3 and PC4 are connected to Sales-Switch, so they receive 192.168.2.x addresses with gateway 192.168.2.1.
  • The router knows which pool to use based on which interface the request arrives on.
  • Confirm all four leases on the router by clicking HQ-Router, going to the CLI tab, and running:
show ip dhcp binding

You should see four entries, each showing a leased IP address and the hardware address of the PC that received it.

A PC shows 0.0.0.0 or no address?

  • Make sure you selected the DHCP radio button, not Static. The fields should auto-populate within a few seconds.
  • Check that the cable between the PC and its switch shows green link lights on both ends. A red or amber light means the connection is down.
  • Verify the router interface for that subnet is still up by running show ip interface brief on the router.

Still not getting an address? Help me troubleshoot why my PC is not receiving a DHCP address.

Every device now has an IP address and knows how to reach its gateway. Next up, you will test whether the PCs can actually talk to each other across subnets and visualize the packets in motion.

Test Connectivity and Visualize Packet Flow

Your network is fully configured with IP addresses and DHCP. Every device has an address and a default gateway. But configuration alone does not prove the network works.

In this step, you will send traffic between devices to verify communication both within a single subnet and across subnets. Then you will use Packet Tracer's Simulation mode to watch a packet travel hop by hop through your network.

In this step, get ready to:
  • Test same-subnet connectivity with a ping between PCs on the Engineering subnet.
  • Test cross-subnet connectivity by pinging a PC on the Sales subnet from the Engineering subnet.
  • Visualize the packet's journey through the network using Simulation mode.
Test same-subnet connectivity

A ping sends a small packet from one device to another and waits for a reply. If the reply comes back, you know the two devices can communicate. Start by testing within the Engineering subnet, where both PCs share the same network segment.

  • Click PC1 on your topology.
  • Go to the Desktop tab.
  • Click Command Prompt to open the simulated terminal.
  • Type the following command and press Enter:
ping 192.168.1.3

What does this command do?

The ping command sends four ICMP echo request packets to PC2's IP address (192.168.1.3). If PC2 is reachable, it replies to each one.

Since both PCs are on the same subnet (192.168.1.0/24) and connected to the same switch, this traffic never touches the router. It goes directly through Eng-Switch.

You should see 4 successful replies, each showing a round-trip time in milliseconds.

Your PC addresses may differ

DHCP assigns addresses in the order devices request them. If PC2 has a different address than 192.168.1.3, check its IP by clicking PC2, opening Desktop then IP Configuration. Use whatever address is shown there.

Seeing Request timed out?

Make sure PC2's IP Configuration still shows a DHCP-assigned address. If it shows 0.0.0.0, toggle back to Static then back to DHCP to force a renewal.

Also confirm all link lights between PC2 and the switch are green. A red light means the cable connection is broken.

Why is my same-subnet ping failing in Packet Tracer?

Test cross-subnet connectivity

Same-subnet pings only prove the switch works. The real test of your network design is routing traffic between the Engineering and Sales subnets. This forces the packet through HQ-Router.

  • Stay in PC1's Command Prompt (from the previous substep).
  • Type the following command and press Enter:
ping 192.168.2.2

What happens during a cross-subnet ping?

PC1 sees that 192.168.2.2 is not on its own subnet (192.168.1.0/24). So it sends the packet to its default gateway (192.168.1.1 on HQ-Router).

HQ-Router receives the packet, checks its routing table, and forwards it out GigabitEthernet0/1 toward the Sales subnet. Sales-Switch delivers it to PC3. The reply travels the same path in reverse.

You should see 4 successful replies. If this works, you have a fully functioning multi-subnet network with working inter-subnet routing.

Cross-subnet ping failing?

Check that both router interfaces show up/up by clicking HQ-Router, going to the CLI tab, and running show ip interface brief.

Verify PC1's gateway is 192.168.1.1 and PC3's gateway is 192.168.2.1. If either gateway is blank or wrong, the PC cannot reach the router.

Help me debug why my cross-subnet ping is failing

Visualize packet flow in Simulation mode

Ping proves connectivity works, but it does not show you how. Packet Tracer's Simulation mode lets you freeze time and step through each hop one by one, watching the packet travel from device to device.

  • Look at the bottom-right corner of the Packet Tracer window. You will see two tabs: Realtime and Simulation (the Simulation tab has a stopwatch icon).
  • Click the Simulation tab to switch modes.

The Simulation Panel opens on the right side, showing an Event List and playback controls.

  • In the Simulation Panel, click Edit Filters.
  • Click Show All/None to deselect all protocols.
  • Under the IPv4 tab, check the ICMP checkbox only. This filters out background traffic (like STP) so you only see your ping packets.
  • Close the filter window.

Why filter for ICMP only?

Switches constantly send Spanning Tree Protocol (STP) packets in the background. Without filtering, the Event List fills up with STP traffic and makes it hard to follow your ping. Filtering to ICMP shows only the packets you care about.

  • Click PC1 on the topology, go to Desktop, and open Command Prompt.
  • Type the following command and press Enter:
ping 192.168.2.2
  • Return to the Simulation Panel. You will see ICMP entries appear in the Event List.
  • Click Capture / Forward to advance the simulation one hop at a time.
  • Watch the packet envelope move from PC1 to Eng-Switch, then to HQ-Router, then to Sales-Switch, and finally to PC3.
  • Click on the packet envelope at any hop to open the PDU Information window. This shows OSI layer details: the source and destination MAC addresses (Layer 2), the source and destination IP addresses (Layer 3), and the protocol type (ICMP).
  • Continue clicking Capture / Forward until the reply packet returns from PC3 all the way back to PC1.

What should I see at each hop?

  • PC1 to Eng-Switch: the packet leaves PC1 with the router's MAC as the destination (because the target IP is on another subnet).
  • Eng-Switch to HQ-Router: the switch forwards the frame to the router based on MAC address.
  • HQ-Router to Sales-Switch: the router re-encapsulates the packet with a new Layer 2 header destined for PC3's MAC address.
  • Sales-Switch to PC3: the switch delivers the frame to its final destination.

You have just watched a cross-subnet packet traverse four devices and two subnets, proving your routing configuration works at every layer.

Seeing too many packets in the Event List?

If you see pink or red envelopes alongside your ICMP packets, those are STP or DTP control packets from the switches. Go back to Edit Filters and confirm only ICMP is checked under IPv4.

Help me filter Simulation mode to show only my ping packets

  • Save your work by pressing Ctrl+S (Windows) or Cmd+S (macOS).
  • Choose a location on your Desktop and name the file something memorable like office-network-lab.pkt.

Your saved .pkt file contains the entire topology, all configurations, and the DHCP leases. You can reopen it anytime to continue experimenting.

Secret mission

Add a Web Server Subnet

Your two-subnet office network is working. But real offices need shared services like intranet sites. Can you add a third subnet with a web server and prove that any PC in the building can load a web page hosted on it?

Clean Up Your Resources

Clean Up Your Resources

Decide whether to keep your resources running, pause them to come back later, or delete them entirely. This project runs entirely locally in Cisco Packet Tracer, so there are no ongoing costs.

Resources you used:

  • Cisco Packet Tracer application (installed on your PC).
  • Your saved .pkt lab file (the network topology you built).
  • SkillsForAll or NetAcad account (used to sign in to Packet Tracer).

Keep everything running

No action needed. Choose this if you plan to continue building on your network lab, adding more subnets, VLANs, or security configurations.

  • Your .pkt file stays saved wherever you stored it.
  • Cisco Packet Tracer remains installed and ready for future labs.
  • Your SkillsForAll or NetAcad account stays active for other Cisco courses and labs.

Pause - I'll come back to this later

Close Packet Tracer to free up system memory. Your saved file and installation will be waiting when you return.

  • Save your topology one more time by pressing Ctrl+S in Packet Tracer.
  • Close Cisco Packet Tracer.
  • When you return, double-click your .pkt file to reopen it directly in Packet Tracer.

Delete - I don't want to use this again

Remove all project resources and the application from your system.

  • Delete your .pkt lab file. Right-click the file in File Explorer and select Delete.
  • Uninstall Cisco Packet Tracer. Open Settings.
  • Select Apps, then Installed apps.
  • Search for Cisco Packet Tracer, click the three-dot menu next to it, and select Uninstall.
  • Your SkillsForAll or NetAcad account is free and useful for future Cisco courses. There is no need to delete it.

Nice Work!

Nice Work!

Nice work! You just built a fully functional multi-subnet office network from scratch in Cisco Packet Tracer.

You've learned how to:

  • Built a complete multi-subnet network topology with a Cisco 2911 router, 2960 switches, and end-user PCs, all cabled and configured from scratch.
  • Configured IP addressing and DHCP pools on a Cisco router using the IOS command-line interface to automatically assign addresses to devices on separate subnets.
  • Verified inter-subnet routing with ping tests and visualized packet flow hop-by-hop using Simulation mode to see how data travels through the network layer by layer.
  • Secret Mission: Extended the network with a third server subnet and tested full Layer 7 HTTP connectivity across all three segments.

Ready to quiz yourself?