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.
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.
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.
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:
| Software | Platform | Character |
|---|---|---|
| Apache HTTP Server | Windows, Linux, macOS | Open source, hugely configurable via modules; the classic choice |
| Nginx | Windows, Linux, macOS | Open source, event-driven; strong at high concurrency and as a reverse proxy |
| Microsoft IIS | Windows Server | Microsoft’s built-in web server; integrates with Active Directory and .NET |
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.
- SMB / CIFS (Windows lineage). Server Message Block is the protocol behind Windows file and printer sharing. Modern SMB 2 and SMB 3 run directly over TCP port 445. Older SMB ran over NetBIOS (ports 137–139), which is legacy but still seen. CIFS is the older name for the same family.
- NFS (Linux / Unix lineage). Network File System is the Unix world’s file-sharing protocol. NFSv4 uses TCP port 2049; older NFSv3 also relies on the portmapper on port 111.
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:
| Database | Type | Default port |
|---|---|---|
| MySQL / MariaDB | Open source, very widely used by web apps | 3306 |
| PostgreSQL | Open source, feature-rich, standards-compliant | 5432 |
| Microsoft SQL Server | Commercial, Windows-centric | 1433 |
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:
| Service | Port(s) | Common software |
|---|---|---|
| DNS | 53 (UDP/TCP) | BIND (Linux/Unix); Microsoft DNS (Windows Server) |
| DHCP | 67 (server), 68 (client), UDP | ISC DHCP / Kea (Linux); Microsoft DHCP (Windows Server) |
| 25 (SMTP), 110 (POP3), 143 (IMAP) | Postfix, Sendmail (Linux); Microsoft Exchange (Windows) |
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.
Hypervisors come in two canonical types, and the distinction is a standard exam question.
| Type 1 — bare-metal | Type 2 — hosted | |
|---|---|---|
| Runs on | Directly on the hardware, with no host OS underneath | On top of a conventional host operating system |
| Performance | Higher; less overhead | Lower; the host OS adds overhead |
| Typical use | Data centres, production servers | Desktops, testing and development |
| Examples | VMware ESXi, Microsoft Hyper-V, KVM, Xen | Oracle VirtualBox, VMware Workstation |
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.
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.
# 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.
Review
Check what you have learned with these review questions.
Sources & references
- Microsoft. [MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3 (SMB over TCP 445). learn.microsoft.com/openspecs.
- Shepler, S., et al. RFC 7530: Network File System (NFS) Version 4 Protocol (TCP port 2049). rfc-editor.org/rfc/rfc7530.
- The Apache Software Foundation. Apache HTTP Server documentation. httpd.apache.org.
- Nginx. Nginx documentation. nginx.org.
- Microsoft. IIS documentation. learn.microsoft.com/iis.
- Docker. What is a container?. docs.docker.com.
- VMware. Understanding hypervisors. vmware.com.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.