Client and Server Configuration

📘 Lesson Notes: Expanded Explanation

🔹 What is Client-Server?

The client-server model is a distributed computing architecture where a server (a powerful

computer or software) provides centralized services or resources, and clients (user devices like
PCs, laptops, or smartphones) request and consume those services. This model is fundamental
to many modern systems, from local file sharing to global Internet services.

 Server: A dedicated system (hardware or software) that hosts resources or services,

such as:
o File Server: Stores and shares files (e.g., a school server hosting lesson plans).
o Web Server: Delivers web pages (e.g., Apache or Nginx for websites like x.com).
o Database Server: Manages databases (e.g., MySQL for storing user data).
o Email Server: Handles email services (e.g., Microsoft Exchange). Servers are
typically robust, with high processing power, storage, and uptime to handle
multiple client requests simultaneously.
 Client: Any device or application that requests services from the server. Examples:
o A student’s laptop accessing shared files in a school lab.
o A smartphone browser requesting a webpage from a web server.
o A game console connecting to a multiplayer game server.
 Real-World Example: In a school lab, the teacher’s PC acts as a file server, hosting
shared resources (e.g., worksheets) that student PCs (clients) access. On the Internet,
when you visit x.com, your browser (client) requests content from xAI’s web server.
 Contrast with Peer-to-Peer (P2P): Unlike P2P networks (where devices share resources
directly, e.g., BitTorrent), client-server networks centralize control, making them more
structured but dependent on the server.

Connection to Types of Networks:

 The client-server model is commonly used in LANs (e.g., school or office networks) and
WANs (e.g., Internet services like cloud storage).
 A WLAN might use client-server for WiFi-based file sharing.
 A VPN could secure client-server communication over a WAN (e.g., remote access to a
company server).

🔹 Advantages (Detailed)
  Centralized Management: Servers consolidate resources, user accounts, and
permissions. For example, an IT admin can manage all user access from one server,
reducing complexity compared to managing each client individually.
 Easier Backup and Updates: Data is stored centrally, simplifying backups (e.g., nightly
server backups vs. backing up every client). Software updates are applied once on the
server, not on each client.
 Enhanced Security: Servers can enforce:
o Authentication: Require usernames/passwords to access resources.
o Encryption: Protect data in transit (e.g., HTTPS for web servers).
o Access Controls: Limit who can read/write files or access services. This is more
secure than P2P, where security is decentralized and harder to enforce.
 Scalability: Servers can handle many clients simultaneously (e.g., a web server serving
thousands of users). Adding clients is easier than reconfiguring a P2P network.

🔹 Disadvantages (Detailed)

 Cost: Servers require dedicated hardware (e.g., high-capacity PCs or specialized server
machines) and software licenses (e.g., Windows Server). Maintenance, power, and
cooling add to costs.
 Single Point of Failure: If the server goes down (e.g., hardware failure, power outage, or
malware), all clients lose access to services. For example, if a school’s file server crashes,
students can’t access shared files.
 Complexity: Setting up a server involves configuring hardware, software, and network
settings (e.g., IP addresses, firewalls, sharing permissions). This requires technical
expertise, unlike simpler P2P setups.
 Scalability Limits: While servers handle many clients, extremely high demand (e.g.,
millions of users hitting a web server) requires advanced infrastructure (e.g., load
balancers, server clusters), increasing complexity and cost.

Connection to Types of Networks:

 The cost and complexity align with LAN setups requiring dedicated devices (e.g.,
switches, routers) from the prior lesson.
 The single point of failure relates to topologies like Star, where a central device (here,
the server) is critical.

🔹 Key Devices in Client-Server (from Prior Lesson)

 Switch: Connects clients and servers in a LAN, forwarding data packets (used in Activity
2).
 Router: Links the LAN to external networks (e.g., Internet) or routes traffic between
clients and servers.
 NIC (Network Interface Card): Enables clients and servers to connect to the network
(wired or wireless).
  Firewall: Protects the server by filtering unauthorized access (e.g., blocking untrusted
IPs).
 Access Point: Supports wireless clients in a WLAN client-server setup.

📝 Worksheet: Detailed Answers and Guidance

Activity 1: Identify Roles

Students identify devices in their environment (lab or home) and classify them as servers or
clients, noting the services provided or used.

Expanded Worksheet Table (example):

Device Role (Server/Client) Service Provided/Used

Teacher’s PC Server Hosts shared folders, distributes Internet access
Student PC 1 Client Accesses shared files, browses Internet via server
Student PC 2 Client Accesses shared files, browses Internet via server
Network Printer Client Sends print jobs to a print server or teacher’s PC
Smartphone Client Accesses WiFi and server-hosted apps (e.g., cloud)
Home NAS Device Server Stores and shares media files for home devices

Guidance:

 Device Examples: Encourage students to list all networked devices (e.g., PCs, printers,
smart TVs, gaming consoles). Even a router can act as a server for DHCP or DNS services.
 Role Determination: A device is a server if it hosts resources (e.g., files, Internet,
printing). It’s a client if it consumes resources. Some devices (e.g., a PC) can be both in
different contexts (e.g., hosting files as a server, browsing the web as a client).
 Challenges: Students may confuse roles (e.g., assuming a powerful PC is always a
server). Clarify that role depends on function, not just hardware.
 Connection to Prior Lesson: Relate to PAN (e.g., smartphone as a client), LAN (e.g., lab
PCs), or WAN (e.g., accessing cloud servers).

Activity 2: Basic LAN Setup

Students configure a client-server LAN with static IPs and a shared folder.

Detailed Steps:

1. Connect Devices:
o Use Ethernet cables to connect the server PC and two client PCs to a switch or
router’s LAN ports. For a WLAN, connect all devices to the same WiFi SSID.
 o Verify physical connections (e.g., link lights on the switch or router).
o Topology: This forms a Star topology (as in the prior lesson’s Activity 2), with the
switch/router as the central hub.
2. Choose Server:
o Select a PC with sufficient resources (e.g., storage for shared files, processing
power). In a lab, this is often the teacher’s PC.
o Ensure the server OS supports file sharing (e.g., Windows 10/11, Linux with
Samba).
3. Assign Static IPs:
o Server:
 IP: 192.168.1.1
 Subnet Mask: 255.255.255.0
 Gateway: (Optional) If connecting to the Internet, set to the router’s IP
(e.g., 192.168.1.254).
o Client 1:
 IP: 192.168.1.2
 Subnet Mask: 255.255.255.0
 Gateway: 192.168.1.1 (server’s IP, or router’s IP if Internet-enabled).
o Client 2:
 IP: 192.168.1.3
 Subnet Mask: 255.255.255.0
 Gateway: 192.168.1.1.
o Configuration:
 Windows: Network Settings > Ethernet/WiFi > Change adapter options >
Right-click connection > Properties > IPv4 > Manual > Enter IP details.
 Linux: Edit /etc/network/interfaces or use nmcli con mod to set static IPs.
o Verify IPs with ipconfig (Windows) or ip addr (Linux).
4. Create a Shared Folder on the Server:
o Create a folder (e.g., C:\SharedFolder on Windows or /home/shared on Linux).
o Windows:
 Right-click folder > Properties > Sharing > Share > Add “Everyone” or
specific users (e.g., “LabUsers”).
 Set permissions (read-only or read/write).
 Note the share path (e.g., \\192.168.1.1\SharedFolder).
o Linux (Samba):
 Install Samba (sudo apt install samba).
 Edit /etc/samba/smb.conf to add:

text

[SharedFolder]
path = /home/shared
writable = yes
 browsable = yes
guest ok = yes

 Restart Samba (sudo systemctl restart smbd).

o Disable firewall temporarily (or allow port 445 for SMB) to test sharing.
5. Connect Clients to the Server:
o On each client, open File Explorer (Windows) or Files (Linux).
o Enter \\192.168.1.1\SharedFolder (Windows) or
smb://192.168.1.1/SharedFolder (Linux) in the address bar.
o If prompted, enter credentials (if set on the server) or use guest access.

Guidance:

 Troubleshooting:
o Ping Test: From a client, run ping 192.168.1.1 to confirm server connectivity. If it
fails, check cables, IPs, or firewalls.
o Firewall: Windows Firewall may block file sharing (open Control Panel >
Windows Defender Firewall > Allow an app > File and Printer Sharing).
o Permissions: If clients can’t access the folder, ensure “Everyone” or specific
users have read/write access.
 Challenges: Students may mistype IPs or share paths. Emphasize exact syntax (e.g.,
double backslashes in Windows).
 Connection to Prior Lesson: This mirrors Activity 3 (LAN setup) but adds file sharing,
reinforcing Star topology and IP configuration.

Activity 3: Test the Configuration

Students test the client-server setup by accessing, uploading, and viewing files.

Detailed Steps:

1. Client Connects to Server:

o On Client 1 (192.168.1.2), open \\192.168.1.1\SharedFolder.
o Verify the folder opens and is accessible.
2. Client Uploads File:
o On Client 1, create a text file (e.g., test.txt) with content (e.g., “Hello from Client
1”).
o Copy or save it to the shared folder.
3. Other Client Views File:
o On Client 2 (192.168.1.3), open \\192.168.1.1\SharedFolder.
o Check if test.txt is visible and can be opened/edited.

Expanded Worksheet Table (sample, actual results vary):

 Test Action Result (✔/✘) Notes
Client connects to server ✔ Client 1 accessed \192.168.1.1\SharedFolder
Client uploads file ✔ Uploaded test.txt with “Hello from Client 1”
Other client views file ✔ Client 2 opened test.txt, content visible

Troubleshooting:

 Connection Fails: Check IP (ping 192.168.1.1), firewall (port 445), or share path syntax.
 Upload Fails: Verify folder permissions allow write access for clients.
 File Not Visible: Ensure the file was saved correctly and Client 2 is accessing the same
share.
 Notes Field: Encourage students to record specific errors (e.g., “Error: Network path not
found” or “Permission denied”).

Guidance:

 Test both read and write access (e.g., edit the file from Client 2).
 If using Linux, ensure Samba is configured correctly and clients support SMB (e.g., install
cifs-utils).
 Discuss real-world parallels (e.g., Google Drive uses a client-server model for file
sharing).

Connection to Prior Lesson: This activity builds on Activity 3 (ping tests) and Activity 4 (wired vs.
wireless) by testing network functionality and applying it to file sharing in a LAN.

Connections to Types of Networks Lesson

 Network Types: The client-server setup is typically a LAN (lab network) but can extend
to WANs (e.g., accessing a cloud server like Dropbox). A VPN could secure remote client-
server connections.
 Topologies: The setup uses a Star topology (clients connect to a switch/router, as in the
prior lesson’s Activity 2).
 Devices: Reinforce the roles of switches (connecting devices), routers (linking to
external networks), and NICs (enabling connectivity).
 Security: Link to Activity 5 (Security Awareness). A server’s shared folder should use
strong passwords or access controls to prevent unauthorized access, aligning with WiFi
security practices like WPA2/WPA3.

Additional Guidance for Implementation

  Tools Needed:
o 3 PCs (1 server, 2 clients) with Windows or Linux (Samba for Linux).
o A switch or router (Ethernet or WiFi).
o Ethernet cables (if wired) or a WiFi network.
o Optional: Internet access to discuss WAN parallels.
 Time Estimate:
o Lesson: 20-30 minutes (including Q&A on real-world examples).
o Activity 1: 10-15 minutes.
o Activity 2: 30-45 minutes (setup and troubleshooting).
o Activity 3: 15-20 minutes.
 Safety/Security:
o Avoid sharing sensitive files in the shared folder.
o Use guest accounts or test credentials to prevent exposing real user accounts.
o Re-enable firewalls after testing to secure the network.
 Challenges and Solutions:
o IP Conflicts: Ensure no other devices use 192.168.1.1-3. Disable DHCP on the
router if assigning static IPs.
o OS Differences: Windows file sharing is straightforward, but Linux requires
Samba setup. Provide step-by-step Samba instructions if needed.
o Student Errors: Common mistakes include wrong IP addresses, disabled sharing,
or firewall blocks. Guide students to check settings systematically.
 Extensions for Advanced Learners:
o Server Software: Explore dedicated server OS (e.g., Windows Server, Ubuntu
Server) or advanced services like web servers (Apache) or databases (MySQL).
o Security: Implement user authentication for the shared folder (e.g., create user
accounts on the server).
o Cloud Analogy: Discuss how cloud services (e.g., AWS, Google Drive) use client-
server models on a WAN scale.
o Performance Testing: Measure file transfer speeds between clients and server,
comparing wired vs. wireless (links to prior lesson’s Activity 4).

Sample Assessment Rubric

To align with the Types of Networks rubric, here’s a tailored version for this worksheet:

Needs Improvement
Criteria Excellent (5) Good (3)
(1)
Correctly identifies Identifies most
Understanding Incorrect or missing
devices and roles with devices/roles, minor
Client-Server Roles roles/services.
clear services listed. errors in services.
LAN Setup All devices connected, IPs Partial setup (e.g., IPs No connectivity or
correct, folder shared correct but sharing major setup errors.
 Needs Improvement
Criteria Excellent (5) Good (3)
(1)
successfully. fails).
All tests (connect, upload,
Testing Some tests successful, Tests fail or
view) successful with
Configuration limited notes. incomplete notes.
detailed notes.
Clear, accurate tables and Minor errors in tables or Missing or unclear
Documentation
notes, no errors. incomplete notes. documentation.

Guidance for Educators:

 Use the rubric to assess both theoretical understanding (Activity 1) and practical skills
(Activities 2-3).
 Provide feedback on specific errors (e.g., “Check firewall settings for file sharing”).
 Reward detailed notes in Activity 3 for troubleshooting insights.

Real-World Applications

 School/Office: File servers for shared documents, print servers for centralized printing.
 Internet: Web servers (e.g., for x.com), email servers, or streaming servers (e.g., Netflix).
 Cloud Computing: Services like Google Drive or Dropbox use client-server models for file
storage and access.
 Gaming: Multiplayer games use servers to host game worlds, with consoles/PCs as
clients.