Week 11 · Lesson 2

Server Software Overview

A server becomes useful only when software gives it a job. This lesson surveys the software families you will meet on the exam — web, file, database, name, and mail servers — and then separates the two ways of running many servers on one machine: virtual machines and containers.

CCNA 200-301 Servers & Virtualisation Verified 2026-10-11
Part 1

What “server software” means

Two layers of software run on server hardware, and confusing them is a common mistake. The first is the operating system — Windows Server or a Linux distribution — which manages the hardware and provides the platform. The second is the service (also called a daemon), the program that actually answers clients: a web server, a database, a name server. Lesson 3 is about the operating system; this lesson is about the services.

Definition — service. A service (daemon) is a long-running program that listens on a network port and responds to client requests. The operating system starts it, and it keeps running in the background with no user logged in.

This is why a server is headless and always-on: the useful work is done by background services, not by a person sitting at the console.

Platform or service? · select a package

Part 2

Web server software

A web server speaks HTTP and HTTPS (ports 80 and 443) and returns web pages or API responses. The three packages you must know:

SoftwarePlatformCharacter
Apache HTTP ServerWindows, Linux, macOSOpen source, hugely configurable via modules; the classic choice
NginxWindows, Linux, macOSOpen source, event-driven; strong at high concurrency and as a reverse proxy
Microsoft IISWindows ServerMicrosoft’s built-in web server; integrates with Active Directory and .NET
Market reality check. Exact figures move every year, but the pattern is stable: Apache and Nginx together run the large majority of public websites, with Nginx especially common on the busiest, highest-traffic sites because of its performance under load. IIS is a clear third but dominates Windows-centric corporate estates. Do not claim any one is “the” web server; all three are in production everywhere.
Exam tip. If a question pairs a web server with a platform, the expected answer for a Windows-only stack is IIS; for an open-source stack it is Apache or Nginx. Nginx is event-driven, so it handles many simultaneous connections on modest hardware.
Part 3

File and print services

A file server shares folders so clients can read and write files as if the storage were local. Windows and Linux use different protocols for this.

Protocol and port explorer · choose a service

Exam tip. SMB = TCP 445 (Windows). NFS = TCP 2049 (Linux). If a question pairs a protocol with a platform, remember SMB/CIFS is Microsoft-oriented and NFS is Unix/Linux-oriented. Print sharing on Windows rides on the same SMB service.
Part 4

Database servers and infrastructure services

A database server stores structured data and answers queries from applications. The three names to know, with their default ports:

DatabaseTypeDefault port
MySQL / MariaDBOpen source, very widely used by web apps3306
PostgreSQLOpen source, feature-rich, standards-compliant5432
Microsoft SQL ServerCommercial, Windows-centric1433

Databases are usually kept on the internal network and never exposed directly to the Internet, because they hold the most valuable data and answer only trusted application servers.

The infrastructure services from Week 9 are also just server software. Know the common packages:

ServicePort(s)Common software
DNS53 (UDP/TCP)BIND (Linux/Unix); Microsoft DNS (Windows Server)
DHCP67 (server), 68 (client), UDPISC DHCP / Kea (Linux); Microsoft DHCP (Windows Server)
Email25 (SMTP), 110 (POP3), 143 (IMAP)Postfix, Sendmail (Linux); Microsoft Exchange (Windows)
Exam tip. Port numbers are the examinable part. DNS 53, DHCP 67/68, SMTP 25, POP3 110, IMAP 143, SMB 445, NFS 2049, HTTPS 443, SSH 22, RDP 3389, LDAP 389, Kerberos 88, MySQL 3306. Almost every server-software question reduces to remembering the right number for the right job.
Part 5

Virtualisation and containers

Instead of buying one physical server per service, organisations run many virtual machines (VMs) on one physical host. The software layer that makes this possible is the hypervisor, sometimes called the virtual machine monitor. It allocates the host’s CPUs, memory, storage, and network to each VM and keeps them isolated.

Definition — hypervisor. A hypervisor creates and runs virtual machines by sharing one physical computer’s resources among them, while keeping each VM isolated and unaware it is virtual.

Hypervisors come in two canonical types, and the distinction is a standard exam question.

Type 1 — bare-metalType 2 — hosted
Runs onDirectly on the hardware, with no host OS underneathOn top of a conventional host operating system
PerformanceHigher; less overheadLower; the host OS adds overhead
Typical useData centres, production serversDesktops, testing and development
ExamplesVMware ESXi, Microsoft Hyper-V, KVM, XenOracle VirtualBox, VMware Workstation
Exam tip. The single deciding factor is what sits underneath. Type 1 = directly on hardware (bare-metal); Type 2 = on top of an OS (hosted). ESXi, Hyper-V and KVM are Type 1; VirtualBox and VMware Workstation are Type 2. People accidentally memorise the product names by sound, so always ask “is there a host OS?”

Containers

Containers are a lighter alternative to virtual machines. Instead of virtualising the hardware and running a whole guest operating system per workload, a container isolates a single application in its own user space while sharing the host’s operating-system kernel. Because there is no second OS to boot, containers start in seconds and use far less memory, which is why they pack more workloads onto one host than VMs can. The trade-off is weaker isolation: containers share the kernel, so a kernel flaw affects them all, and they can only run images built for the host’s OS family. Docker is the best-known container platform. A useful one-line contrast: a VM virtualises the hardware; a container virtualises the operating system.

Virtual machine or container? · select one

Part 6

Binding an IP address and a port

A service reaches clients through a specific socket: the pair of an IP address and a port number. When a service starts, it binds to a local IP and port and then listens for incoming connections. A web server, for example, binds to its host address on port 443 and accepts HTTPS connections; a database binds to an internal address on 3306.

Binding has two important consequences. First, two services cannot bind to the same IP and port — if the port is already in use, the second service fails to start. Second, the bind address controls who can reach the service. Binding to 127.0.0.1 (localhost) means only that machine can connect; binding to a real interface address, or to all addresses, exposes it to the network. This is a security decision as much as a configuration one.

Who can reach it? · choose the bind address
Server service bound to 0.0.0.0:443 listening Switch / router Local console Client on the same LAN Client on the internet

# List listening sockets and the process that owns each one (Linux)
ss -tlnp

# Bind a service to a specific address and port (conceptual)
listen 10.0.0.5:443

The layered stack

The figure below shows how the pieces stack. Starting at the bottom: physical hardware, then the hypervisor, then each virtual machine with its own operating system, and finally the services that bind to ports and face the network. Read it upwards — each layer depends on the one beneath it.

Physical hardware: CPUs, ECC RAM, RAID storage, NICs Type 1 hypervisor (bare-metal) — ESXi / Hyper-V / KVM VM 1 + guest OS Web server VM 2 + guest OS Database server VM 3 + guest OS DNS / DHCP Port 443 (HTTPS) Port 3306 (MySQL) Port 53 (DNS) Each service binds an IP:port and listens for clients. Services run inside guest operating systems, which the hypervisor runs on the hardware.
The virtualisation stack. One physical host runs a Type 1 hypervisor, which runs several virtual machines; each VM runs its own operating system and one or more services that bind to ports and face the network.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Microsoft. [MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3 (SMB over TCP 445). learn.microsoft.com/openspecs.
  2. Shepler, S., et al. RFC 7530: Network File System (NFS) Version 4 Protocol (TCP port 2049). rfc-editor.org/rfc/rfc7530.
  3. The Apache Software Foundation. Apache HTTP Server documentation. httpd.apache.org.
  4. Nginx. Nginx documentation. nginx.org.
  5. Microsoft. IIS documentation. learn.microsoft.com/iis.
  6. Docker. What is a container?. docs.docker.com.
  7. VMware. Understanding hypervisors. vmware.com.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.