Sample Server With Access Point In Cisco Packet Tracer

In this guide, we will walk through creating a sample server with an access point in Cisco Packet Tracer, showing how to build a small wired‑wireless network, assign IP addresses, enable basic services, and verify connectivity. The lab is ideal for students who want to see how a server can provide DHCP, HTTP, or DNS support while an access point (AP) extends the network to wireless clients. By following the steps below, you’ll gain hands‑on experience with IP addressing, VLAN‑like segmentation (using separate subnets), and wireless configuration—all within the safe, drag‑and‑drop environment of Packet Tracer Nothing fancy..

Short version: it depends. Long version — keep reading.

Overview of the Lab Scenario

The topology consists of four main parts:

1. A server PC that will act as a DHCP server and host a simple web page.
2. A Cisco wireless access point (Linksys‑style) that provides Wi‑Fi to laptops and smartphones.
3. Two wired end‑devices (PCs) connected to the server via a switch to represent LAN clients.
4. Two wireless end‑devices (a laptop and a smartphone) that associate with the AP.

All devices reside in the same IP subnet (e.And , 192. That's why 168. 0/24) so that communication between wired and wireless hosts is seamless. 10.g.The server supplies IP addresses dynamically, and the AP bridges the wireless traffic to the wired LAN Easy to understand, harder to ignore..

Required Devices and Components

Make sure you have the latest version of Packet Tracer installed; the wireless AP model appears under End Devices → Wireless.

Step‑by‑Step Configuration

Placing the Devices

1. Drag a Switch to the center of the workspace.
2. Place the Server PC left of the switch and connect its FastEthernet0/0 port to any switch port using a copper straight‑through cable.
3. Add two LAN PCs on the right side of the switch; connect each to a free switch port.
4. Position the Access Point above the switch. Connect its Ethernet0 port to another switch port with a straight‑through cable.
5. Place the Wireless Laptop and Wireless Smartphone anywhere in the workspace; they will connect wirelessly to the AP (no cables needed).

Your logical layout should resemble a star topology with the switch at the hub, the server and AP as leaf nodes, and the end‑devices attached accordingly No workaround needed..

Configuring the Server PC

1. Click the Server PC → Desktop tab → IP Configuration Not complicated — just consistent..

2. Set a static IP address: 192.168.10.1, subnet mask 255.255.255.0, default gateway 192.168.10.1 (the server itself will act as gateway for DHCP clients).

3. deal with to the Services tab.

   • Enable DHCP:
     • Pool Name: LAN_Pool
     • Default Gateway: 192.168.10.1
     • DNS Server: 192.168.10.1 (we’ll also enable DNS on the server)
     • Starting IP: 192.168.10.10
     • Maximum Users: 50
   • Enable HTTP:
     • Under the HTTP service, click Edit and create a simple HTML file (e.g., index.html) with the text <h1>Welcome to the Sample Server</h1>. Save it.
   • (Optional) Enable DNS if you want the server to resolve names; set the same IP as the DNS server.

4. Click Apply and then Close. The server now hands out addresses from .10 upward and serves a basic web page on port 80 No workaround needed..

Setting Up the Access Point

1. Click the Access Point → GUI tab (or Config depending on PT version).
2. In the Wireless section:
   • SSID: SampleLab_WiFi
   • Security: Choose WPA2-PSK and set a passphrase, e.g., Cisco123!.
   • Channel: 6 (or leave on auto).
3. In the Interfaces tab, ensure Ethernet0 is enabled and set to DHCP Client (it will obtain an address from the server).
4. Go to the DHCP tab (if the AP has a built‑in DHCP server) and disable it—we rely on the server’s DHCP to avoid address conflicts.
5. Click Save and then Close.

The AP will now obtain an IP address (e.In real terms, g. , 192.

168.10.11) from the server’s DHCP pool and will appear in the server’s DHCP bindings table.

Connecting the Wireless Clients

1. Click the Wireless Laptop → Desktop tab → IP Configuration and set it to obtain an address via DHCP.
2. Open the Wireless tab, scan for available SS

Connecting the Wireless Clients

1. Click the Wireless Laptop → Desktop tab → IP Configuration and choose “Obtain an IP address automatically” (DHCP). The laptop should receive an IP lease from the server’s DHCP pool, typically something like 192.168.10.x And that's really what it comes down to..

2. Switch to the Wireless tab again. The AP will broadcast its SSID (SampleLab_WiFi). On any supported device – here the laptop – open the Wi‑Fi settings and select this network. The laptop will complete authentication in under a few seconds and display a connected status bar with an IP address such as 192.168.10.42 And that's really what it comes down to..

3. Verify that the client can reach the server’s services. Open a browser (or run ping 192.168.10.1 from the command line) and confirm that the gateway responds quickly. A successful ping to the DHCP server proves that the routing table is correctly installed on both the server and the AP Less friction, more output..

4. Repeat the process for the Wireless Smartphone:

   • Click the phone’s icon on the left‑hand list and go to its Desktop page. Set the IP configuration to “Automatic”.
   • Return to the Wireless tab, locate the SSID that appears, and join it. The phone should acquire an address within the same 192.168.10.0/24 range (e.g., 192.168.10.57).
   • From either the phone or the laptop, ping the server (ping 192.168.10.1) to double‑check that the DHCP scope is functional across all devices.

5. Once both mobile endpoints are online, perform a quick functional test by opening a web page on one of them. The server’s home page (http://samplelab.com) should load without error, confirming that the HTTP service is reachable over the wired link to the AP and then to the wireless clients.

Verifying the Full Star Topology

• Server ↔ Switch: Confirm that the Server PC obtains a DHCP lease (its own IP, e.g., 192.168.10.1) and that it is able to forward traffic to the Access Point and the other LAN PCs. A ping from the server to the AP (ping 192.168.10.20) should succeed.
• Switch ↔ AP: Ensure the AP’s Ethernet0 interface is advertising the IP obtained from the DHCP reservation (often 192.168.10.20). Run arp -a on a laptop to see that the AP’s MAC address appears in the ARP table.
• AP ↔ Wireless Devices: Check that each wireless client shows a valid association with the AP’s SSID in their OS details. The AP’s DHCP bindations table should list each device with a unique lease, preventing IP overlap.

If any hop fails, inspect the corresponding log entries on the server (e.Plus, g. , /var/log/syslog or the Windows Event Viewer for the DHCP service) and on the AP (status LEDs, wpsctl output) to identify whether the issue lies in the DHCP scope, firewall rules, or physical cabling.

Conclusion

By arranging the equipment in a classic star layout—server and access point centered around the core switch, with the two LAN PCs and the wireless devices radiating outward—the network achieves reliable connectivity while keeping management straightforward. The server acts as the DHCP authority, providing stable IP addressing for every host, while the Access Point supplies secure wireless coverage for laptops and smartphones. After completing the configuration steps outlined above, all components report successful communication, demonstrating that the lab environment is operational and ready for further experimentation or real‑world use. This setup serves as a solid foundation for additional projects such as VPN tunnels, scripted automation, or scaling the infrastructure with more devices.