Build Your First Virtual Wired LAN

Build a two-PC wired LAN and troubleshoot IPv4 connectivity.

Introduction

30 Second Summary

Two computers can sit side by side with a cable between them while their messages still go nowhere. Finding the fault means checking the cable before tracing the device addresses.

In this project, you will build a small office-style wired LAN in Cisco Packet Tracer. A deliberate IPv4 mismatch gives you a failed ping to diagnose before you repair the addresses.

What You'll Build

Your finished Packet Tracer lab shows a working two-PC network with green links, compatible addresses, successful pings, and a saved file ready to demonstrate.

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

  • A visible wired topology shows two PCs connected through a switch. Green link lights confirm both Ethernet connections are active.
  • A troubleshooting demonstration exposes how incompatible static IPv4 settings stop communication. Successful two-way ping results prove the repair.
  • A saved Packet Tracer Activity File named first-wired-lan.pkt lets you reopen the lab for future demonstrations.
  • Secret Mission: Add a third wired host with a unique address. Prove it belongs to the same LAN with two-way ping tests.

Are there any prerequisites?

You need a Windows computer with internet access. No prior networking experience is required.

Before We Start

You are about to build a switched LAN to see how Ethernet cabling works with IPv4 addressing. Before any hands-on work, lock in why a successful ping matters when devices need to communicate.

Set Up Cisco Packet Tracer

A physical networking lab needs hardware that many beginners do not have at home. A virtual lab lets you experiment without risking real equipment.

Cisco Packet Tracer provides that virtual lab. You can safely test a LAN before working with physical devices.

Access starts with a free Cisco Networking Academy account. This step ends with the simulator installed in an authenticated blank Logical topology workspace.

In this step, get ready to:
  • Enroll in the free beginner course using a new Cisco Networking Academy account.
  • Install Cisco Packet Tracer on your Windows computer.
  • Complete browser authentication to reach the blank Logical workspace.
Create your Cisco account and enroll

Cisco lists the beginner course as free. Your account also handles Packet Tracer authentication when you launch the application.

  • In your web browser, visit the official Cisco Networking Academy course catalog.
  • Select Getting Started with Cisco Packet Tracer from the beginner course listing.
  • Follow Cisco's account prompts to create your free account.
  • Enroll in the course with the account you created.
  • Confirm that the course appears in your enrolled learning area.

Good progress: your free account is ready for this project's official learning resources.

Download and install Cisco Packet Tracer

The official Resource Hub provides the current Windows installer. Using that download keeps your setup current without relying on a guessed version number.

  • In your browser, visit the official Cisco Resource Hub.
  • Sign in with your Cisco account if the Resource Hub asks you to authenticate.
  • Select the current Windows download offered for Cisco Packet Tracer.
  • Wait until your browser marks the download as complete.

You'll see the downloaded Packet Tracer installer listed as complete in your browser.

  • Open the downloaded Packet Tracer installer from your browser's downloads list.
  • Accept the License Agreement.
  • Choose the destination folder for Cisco Packet Tracer.
  • Choose the Start Menu folder for Cisco Packet Tracer.
  • Review the additional tasks shown by the installer.
  • Select Install.
  • Close the installer after it confirms that installation is complete.

That is the software in place: your Windows computer can now run the virtual networking lab.

Having trouble with the installation?

  • Restart the current Windows download from the Resource Hub if the first download does not complete.
  • Reopen the downloaded installer if the installation window closes before completion.
  • Confirm that you accepted the License Agreement before looking for the Install option.

Still stuck? Help me troubleshoot the Cisco Packet Tracer installation.

Complete the first launch

Packet Tracer hands authentication to your browser before opening the workspace. The multi-user startup option is unnecessary for this local two-PC lab.

  • Press the Windows key to open Windows search.
  • Type Cisco Packet Tracer into the search field.
  • Press Enter to launch the application.
  • Select No when Packet Tracer asks Would you like to run multi-user when the application starts?.
  • Select LOGIN in the Cisco Packet Tracer Login window.
  • Complete authentication in the browser using your Cisco account.

Your browser confirms the handoff with You have successfully logged in to Cisco Packet Tracer. You may close this tab.

Before you switch back, consider whether Packet Tracer should show an existing project or a blank workspace.

  • Switch back to Cisco Packet Tracer from the Windows taskbar.
  • Confirm that the workspace is empty with Logical selected.

You'll see a large blank canvas with Logical selected. This confirms that Packet Tracer is installed and authenticated.

You're set: your virtual lab is open and ready for its first network.

Still waiting for the workspace?

  • Keep the browser tab open until it confirms that authentication succeeded.
  • Return to the Packet Tracer window after the browser confirms the login.
  • Repeat the LOGIN flow with the Cisco account enrolled in the beginner course if the login window remains open.

Need another pair of eyes? Help me finish the Cisco Packet Tracer browser login.

Your Packet Tracer lab is ready. Next, you'll place the two PCs and switch that form your wired LAN.

Build and Cable the LAN

Your Cisco Packet Tracer lab is ready. The blank Logical workspace can now become your first network.

Every working wired LAN begins at the physical layer. You will place two end devices around a Layer 2 switch.

Each PC needs an Ethernet path through a specific switch port.

In this step, get ready to:
  • Place one 2960 switch in the Logical workspace.
  • Add two named PC-PT end devices.
  • Create two active copper straight-through Ethernet links.
Place the network devices

A network topology is the visible map of your devices. The switch belongs in the middle because both PCs connect through it.

  • In the device picker at the bottom left, select the network-device category icon.
  • Select the switch subcategory icon.

You will see the available switch models in the device picker.

  • Select the 2960 switch model.
  • Click near the center of the blank Logical workspace.

You will see one switch in the center of the workspace.

  • Select the end-device category icon in the device picker.
  • Select the PC-PT model.

The PC-PT model is now ready to place.

  • Click an empty area to the left of the switch.
  • Click an empty area to the right of the switch.

The Logical workspace now shows one switch between two PCs.

Missing a device?

  • Check that the switch model shows 2960 before placing the switch.
  • Check that each computer model shows PC-PT.

Get help finding the correct devices in Packet Tracer.

Name and connect PC-A

A copper straight-through cable connects unlike Ethernet devices such as a PC and a switch. The first cable uses the first available switch port.

  • Click the PC on the left side of the workspace.
  • Select the Config tab.

You will see the device configuration window with a Display Name box.

  • Click the Display Name box.
  • Replace the current value with PC-A.

The label below the left PC now reads PC-A.

  • Close the device configuration window.
  • Select Connections in the device picker.
  • Select Copper Straight-Through.

The cable tool is now active.

  • Click PC-A.
  • Select FastEthernet0.

Packet Tracer is now waiting for the other end of the cable.

  • Click the 2960 switch.
  • Select FastEthernet0/1.

You will see a cable between PC-A and the switch. One link indicator may begin amber while the switch activates the port.

No cable between PC-A and the switch?

  • Confirm that you selected Copper Straight-Through from Connections.
  • Confirm that the PC endpoint uses FastEthernet0.
  • Confirm that the switch endpoint uses FastEthernet0/1.

Get help checking the first Ethernet connection.

Name and connect PC-B

The second PC needs its own switch port. Using FastEthernet0/2 keeps each physical connection separate.

  • Click the PC on the right side of the workspace.
  • Select the Config tab.

You will see the configuration window for the right PC.

  • Click the Display Name box.
  • Replace the current value with PC-B.

The label below the right PC now reads PC-B.

  • Close the device configuration window.
  • Select Connections in the device picker.
  • Select Copper Straight-Through.

The second cable is ready to place.

  • Click PC-B.
  • Select FastEthernet0.

The PC end of the second connection is selected.

  • Click the 2960 switch.
  • Select FastEthernet0/2.

You will see the second cable between PC-B and the switch. A short amber phase is normal while the switch activates the port.

Before you check both links, picture the color you expect after the switch finishes activating the ports.

  • Wait roughly one minute for the switch ports to finish activating.
  • Inspect both ends of the PC-A connection.
  • Inspect both ends of the PC-B connection.

You should see green indicators at both ends of both cables. This proves that each PC has an active physical connection to the switch.

That is your first physical-layer win. Both virtual PCs now have an active Ethernet path through the switch.

Still seeing amber or red indicators?

  • Wait a full minute if the indicator is amber.
  • Check that both cables use Copper Straight-Through.
  • Check that the switch connections use FastEthernet0/1 for PC-A plus FastEthernet0/2 for PC-B.

Get help diagnosing a link that does not turn green.

The physical path is live. Next, you will prove that green links still need compatible IPv4 addressing.

Test a Subnet Mismatch

PC-A now has a green link to the 2960 switch in Cisco Packet Tracer. PC-B has one too.

Green links confirm the physical layer. This step tests whether IPv4 traffic can cross the LAN when the hosts use different /24 network prefixes.

In this step, get ready to:
  • Assign static IPv4 settings to each PC.
  • Inspect the address settings from each PC's command line.
  • Test connectivity from PC-A.
Configure PC-A

A static IPv4 configuration gives a host a fixed address. A subnet mask tells the host which addresses belong to its local network.

  • Select PC-A in the Logical workspace.

You should see the PC-A device window.

  • Select the Desktop tab.
  • Select IP Configuration.

You should see the fields for the PC's IPv4 settings.

  • Enter 192.168.1.10 as the static IP address.
  • Enter 255.255.255.0 as the subnet mask.

The configuration now shows PC-A's fixed address with its subnet mask.

  • Leave the default gateway field blank.

PC-A now displays 192.168.1.10 with the mask 255.255.255.0. Its link to the switch remains green.

Configure PC-B

PC-B needs its own address. You will use a different network prefix so the connectivity test can reveal what the green links do not prove.

  • Close the PC-A device window.
  • Select PC-B in the Logical workspace.

You should see the PC-B device window.

  • Select the Desktop tab.
  • Select IP Configuration.

The IPv4 configuration fields are ready for PC-B's settings.

  • Enter 192.168.2.11 as the static IP address.
  • Enter 255.255.255.0 as the subnet mask.

The configuration now shows PC-B's fixed address with the same subnet mask as PC-A.

  • Leave the default gateway field blank.

PC-B now displays 192.168.2.11 with the mask 255.255.255.0. Its link to the switch remains green.

Inspect and test the addresses

The configuration windows show what you entered. The command line confirms what each PC is actually using before you test connectivity.

  • Close the PC-B device window.
  • Return to PC-A in the Logical workspace.

The PC-A device window is back in view.

  • Select the Desktop tab.
  • Select Command Prompt.
  • Inspect PC-A's saved network configuration by running this command:
ipconfig /all

What does this command check?

The ipconfig command reads the PC's active network configuration. The /all option displays the complete configuration for its adapters.

You should find 192.168.1.10 with the mask 255.255.255.0. No default gateway should be configured.

  • Close the PC-A device window.
  • Return to PC-B in the Logical workspace.

The PC-B device window is now in view.

  • Select the Desktop tab.
  • Select Command Prompt.
  • Inspect PC-B's saved network configuration by running this command:
ipconfig /all

Why check both PCs?

This command confirms that PC-B kept the address you entered. Checking each host rules out an input mistake before the connectivity test.

You should find 192.168.2.11 with the mask 255.255.255.0. No default gateway should be configured.

Do the displayed addresses look wrong?

  • Return to IP Configuration on the PC with the incorrect value.
  • Correct the static IP address shown for that PC.
  • Confirm that its subnet mask is 255.255.255.0.

Still stuck? Help me compare my Packet Tracer PC configuration with the values shown by the command line.

  • Close the PC-B device window.
  • Return to PC-A in the Logical workspace.

The PC-A device window is ready for the connectivity test.

  • Select the Desktop tab.
  • Select Command Prompt.

Before you run the test, do you think green link lights guarantee an echo reply?

  • Test connectivity from PC-A by running this command:
ping 192.168.2.11

Why does the ping fail?

You do not receive successful echo replies. Both Ethernet links remain green.

The ping command sends ICMP echo requests to the target address. A reply would prove IP-level connectivity.

With a /24 mask, the two addresses belong to different networks. The LAN has no router or default gateway to move traffic between them.

That failed test proves the distinction between green physical links and working Layer 3 connectivity.

Did the ping return successful replies?

A successful reply means one of the configured addresses differs from this test setup.

  • Return to PC-B's IP Configuration screen.
  • Confirm that PC-B uses 192.168.2.11.
  • Confirm that PC-A uses 192.168.1.10.

Need another pair of eyes? Help me diagnose why this deliberate subnet-mismatch ping succeeded.

You have proved that working cables cannot overcome incompatible network prefixes. Next, you will repair PC-B's address and prove two-way connectivity.

Repair and Verify Connectivity

Your Cisco Packet Tracer links proved that the Ethernet path works. The failed ping exposed a separate addressing problem.

PC-B currently belongs to a different IPv4 subnet. No router exists to carry traffic between the two subnet prefixes.

You will place both hosts in the same /24 subnet. You will prove the repair in both directions before saving the lab.

In this step, get ready to:
  • Repair PC-B's IPv4 configuration.
  • Prove two-way connectivity with ping.
  • Save the repaired topology as first-wired-lan.pkt.
Repair PC-B's IPv4 address

Hosts with the same subnet prefix can communicate directly. Changing PC-B's address places both PCs in the 192.168.1.0/24 network.

  • Return to PC-B in the Logical workspace.
  • Select the Desktop tab.
  • Select IP Configuration.
  • Replace the value in the IP Address field with 192.168.1.11.
  • Leave the Subnet Mask set to 255.255.255.0.
  • Leave the Default Gateway field blank.

PC-B now shares PC-A's subnet prefix. The green links still confirm the physical path.

  • Return to the Desktop tab on PC-B.
  • Select Command Prompt.
  • Verify PC-B's saved configuration by running this command:
ipconfig /all

What does this command show?

The ipconfig /all command displays the full TCP/IP configuration for PC-B.

This output proves that Packet Tracer kept the new address.

You should see 192.168.1.11 for PC-B. You should also see the subnet mask 255.255.255.0.

The default gateway entry should remain empty.

Still Seeing PC-B's Old Address?

  • Return to IP Configuration if the output still shows 192.168.2.11.
  • Set the IP address to 192.168.1.11.
  • Set the subnet mask to 255.255.255.0 if the displayed mask differs.

Still stuck? Help me check why PC-B still shows its old IPv4 address.

Test connectivity in both directions

A successful ping proves that the corrected addressing works across the switch. Testing from both PCs confirms that each host can reach the other.

  • Return to PC-A in the Logical workspace.
  • Select the Desktop tab.
  • Select Command Prompt.

Before you run this test, do you expect PC-A to reach PC-B now? Keep your answer in mind.

  • Test connectivity from PC-A to PC-B by running this command:
ping 192.168.1.11

What does this command test?

The ping command sends ICMP echo requests to PC-B.

An echo reply proves IP-level connectivity between the hosts.

You should see four replies from 192.168.1.11. The summary should report 0% loss.

No Replies from PC-B?

  • Confirm that PC-B still shows 192.168.1.11 in IP Configuration.
  • Confirm that both PCs use 255.255.255.0 as the subnet mask.
  • Confirm that both PC-to-switch links remain green.

Need another pair of eyes? Help me diagnose why PC-A cannot ping PC-B after the address repair.

  • Return to PC-B in the Logical workspace.
  • Select the Desktop tab.
  • Select Command Prompt.

If the addressing is correct in both directions, what do you expect PC-B's test to show? Hold that prediction for the result.

  • Test connectivity from PC-B to PC-A by running this command:
ping 192.168.1.10

Why Test the Reverse Direction?

This test proves that PC-B can reach PC-A at 192.168.1.10.

Successful replies confirm two-way connectivity across the LAN.

You should see successful replies from 192.168.1.10.

That's the repair confirmed: both virtual PCs can now exchange echo replies across the switch.

Save the working LAN

A Packet Tracer Activity File stores your complete topology for later use. Saving now turns your successful test into a reusable lab.

  • Select File in Cisco Packet Tracer.
  • Select Save As….
  • Choose a local Windows folder that you can find again.
  • Enter first-wired-lan.pkt as the project name.
  • Confirm that Packet Tracer Activity File (*.pkt) remains selected as the file type.
  • Select Save.

Before you check the folder, which filename do you expect to find? Keep that name in mind.

  • Press the Windows key to open Search.
  • Type File Explorer in the search field.
  • Press Enter.
  • Open the folder you selected in the Save As window.

You should see first-wired-lan.pkt in that folder. This confirms that your functioning two-host LAN is saved locally.

Can't Find the Saved File?

  • Return to Cisco Packet Tracer.
  • Select File.
  • Select Save As… to check the current folder.

Still missing the file? Help me locate first-wired-lan.pkt on Windows.

Your LAN now carries traffic in both directions. The first-wired-lan.pkt file preserves that proof for your next demonstration.

Secret mission

Secret Mission: Add a Third Host

Your two-host LAN already passes traffic. Extend it with PC-C on a free switch port. Give the new host a unique address. Prove two-way connectivity while preserving your original file.

Clean Up Your Resources

Clean Up Your Resources

Your Cisco Packet Tracer lab runs entirely on your Windows computer with no usage-based charges. You can keep it ready, close it for now, or remove its local resources.

Resources you used:

  • A local Cisco Packet Tracer installation.
  • The first-wired-lan.pkt file containing your original two-PC LAN.
  • The first-wired-lan-three-hosts.pkt file containing your expanded three-PC LAN.

Your free Cisco Networking Academy account remains available in every cleanup option.

Keep everything running

No action needed. Choose this option if you want your simulator and saved topologies ready for more networking practice.

  • Leave Cisco Packet Tracer installed on your Windows computer.
  • Keep first-wired-lan.pkt in its known local folder.
  • Keep first-wired-lan-three-hosts.pkt in its known local folder.

Both LAN topologies remain ready to reopen without creating ongoing charges.

Pause - I'll come back to this later

Close the running simulator while keeping both saved topologies. The virtual LAN incurs no running charges while Cisco Packet Tracer is closed.

  • Close the Cisco Packet Tracer window.
  • Keep first-wired-lan.pkt in the known local Windows folder.
  • Keep first-wired-lan-three-hosts.pkt in the known local Windows folder.

Your saved links and static IPv4 settings remain stored inside the .pkt files for your return.

Delete - I don't want to use this again

Remove both saved topologies plus the local simulator if you want to start fresh. This cleanup only affects resources on your Windows computer.

Your free Cisco Networking Academy account stays available after the local cleanup.

Delete the saved Packet Tracer files:

  • Close Cisco Packet Tracer before removing the saved files.
  • Use the Windows file browser to return to the known local folder where you saved the topologies.
  • Delete first-wired-lan.pkt from that folder.
  • Delete first-wired-lan-three-hosts.pkt from that folder.
  • Confirm that neither filename appears in the folder.

Uninstall Cisco Packet Tracer:

  • Select Start on the Windows taskbar.
  • Select Settings.
  • Select Apps.
  • Select Installed apps.
  • Find Cisco Packet Tracer in the app list.
  • Select More beside Cisco Packet Tracer.
  • Select Uninstall.

You will see Windows start the app removal flow.

  • Complete the uninstall confirmation.
  • Return to Installed apps.
  • Confirm that Cisco Packet Tracer no longer appears in the app list.

That completes the local cleanup. Your Cisco Networking Academy account remains ready for future courses.

Nice Work!

Nice Work!

You did it! Your Cisco Packet Tracer lab now contains a working three-host wired LAN.

You've learned how to:

  • Built a two-host wired LAN through a 2960 switch. Used Ethernet cabling to connect each PC. Read green link lights as proof that the physical layer was working.
  • Configured static IPv4 addresses with a subnet mask. Used ipconfig /all to inspect each host's settings.
  • Diagnosed a failed ping caused by different /24 subnets. Repaired PC-B's address to place both hosts in the same subnet. Proved two-way connectivity with successful ping replies and 0% loss.
  • Completed the optional Secret Mission by extending the LAN with PC-C. Assigned the unique address 192.168.1.12/24. Proved connectivity to PC-A in both directions. Saved the expanded topology as first-wired-lan-three-hosts.pkt.

Ready to quiz yourself?