Objective 2.3: Summarize services provided by networked hosts

Cert: CompTIA A+ Core 1 (220-1201) V15 Domain: 2.0 Networking Weight: ~23% of Core 1 Depth: Summarize. Identify common server roles, internet appliances, legacy systems, and IoT devices and what each does.

What this objective tests

You should know what each common server role does, which network appliances handle which infrastructure functions, what legacy systems still live in industrial environments (SCADA), and how IoT devices fit into modern networks.

Key facts

Server roles:

• DNS server. Resolves hostnames to IP addresses. Without DNS, you have to type IPs manually for everything.
• DHCP server. Hands out IP addresses, subnet masks, gateways, and DNS server settings to clients on the network.
• Fileshare server. Hosts shared folders accessed by SMB (Windows), NFS (Unix/Linux), or AFP (older Mac).
• Print server. Manages networked printers, print queues, and shared printer access for multiple users.
• Mail server. Sends and receives email (SMTP), and hosts mailboxes for retrieval (IMAP, POP3, Exchange).
• Syslog server. Receives, stores, and indexes log messages from network devices and other servers. Foundation for monitoring and security investigation.
• Web server. Hosts websites and web applications. Common examples: IIS (Windows), Apache, Nginx (Linux).
• AAA server (Authentication, Authorization, Accounting). Centralized identity for network access. Examples: RADIUS for Wi-Fi and VPN logins, TACACS+ for network device administration.
• Database server. Hosts relational or other databases. Examples: SQL Server, MySQL, PostgreSQL, Oracle.
• NTP server (Network Time Protocol). Synchronizes clocks across the network. Critical for log correlation, Kerberos authentication, and certificate validity.

Internet appliances:

• Spam gateway. Inspects inbound email, filters spam and phishing, sandboxes attachments. Common products: Proofpoint, Mimecast, Microsoft Defender for O365.
• UTM (Unified Threat Management). All-in-one security appliance combining firewall, intrusion prevention, antivirus, web filtering, VPN, and sometimes more.
• Load balancer. Distributes incoming traffic across multiple servers to balance load and add redundancy. Operates at Layer 4 (transport) or Layer 7 (application).
• Proxy server. Acts as an intermediary between clients and the internet. Common uses: web filtering (block categories), caching, anonymity, security inspection.

Legacy/embedded systems:

• SCADA (Supervisory Control and Data Acquisition). Industrial control systems used in manufacturing, utilities, oil and gas, water treatment, and similar environments. Often runs on older operating systems and proprietary protocols. Air-gapping or strong network segmentation is the standard security approach because the systems themselves cannot be easily patched.

IoT devices:

• Internet of Things devices: smart thermostats, security cameras, smart locks, voice assistants, industrial sensors, networked appliances, fleet trackers, and many more.
• Often have constrained hardware, intermittent updates, and weak default security.
• Should be isolated on a separate VLAN or network segment from corporate workstations and servers.

Common gotchas

• DNS as the silent dependency. Almost everything else depends on DNS working. When DNS breaks, the symptoms look like "the internet is down" but the actual network is fine.
• DHCP scope exhaustion. A small DHCP scope on a network with many devices runs out of addresses. Clients then either fall back to APIPA addresses or fail to connect.
• NTP drift breaks authentication. Kerberos requires clocks within 5 minutes. NTP drift on a server can break logins until the time syncs again.
• Open spam gateway misconfiguration. A misconfigured mail gateway can either let too much spam through or accidentally block legitimate senders. Always test thoroughly.
• UTM single-point-of-failure. All-in-one security appliances are convenient but if the UTM fails, everything it protects also stops.
• SCADA security blind spots. Industrial systems often run unpatched Windows XP or proprietary firmware. Treat the SCADA network as untrusted and segment aggressively.
• IoT on the main VLAN. Cheap IoT devices with known security issues should never share a network with sensitive systems. Isolate them.

Real-world context

For a typical SMB network, the on-prem infrastructure usually includes:

• Active Directory domain controllers (which combine DNS, DHCP, AAA, and authentication).
• A file server (Windows or NAS).
• A print server (built into Windows AD or a print management product).
• Sometimes a small SQL Server for line-of-business applications.
• A UTM or firewall at the edge.
• Cloud services replace many of the rest (mail in Microsoft 365, web in cloud hosting, etc.).

For Claire (the SMB persona) running an office of 10-30 employees, the most common services Revtek manages on her behalf:

• DNS and DHCP (usually built into the router or AD controller).
• File sharing (Windows file server or a managed NAS).
• Email (Microsoft 365 hosted).
• Backup (cloud or on-prem with offsite replication).
• Network security (firewall + endpoint EDR).

Sources

• [CompTIA A+ 220-1201 Exam Objectives Version 4.0, Section 2.3](../../../../../../30-RevyTechJourney/CompTIA%20A%2B%20220-1201%20Exam%20Objectives%20%284.0%29.pdf)
• [Wikipedia: Domain Name System](https://en.wikipedia.org/wiki/Domain_Name_System)
• [Wikipedia: Dynamic Host Configuration Protocol](https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol)
• [Wikipedia: Unified threat management](https://en.wikipedia.org/wiki/Unified_threat_management)
• [Wikipedia: Load balancing (computing)](https://en.wikipedia.org/wiki/Load_balancing_(computing))
• [Wikipedia: SCADA](https://en.wikipedia.org/wiki/SCADA)
• [Wikipedia: Internet of things](https://en.wikipedia.org/wiki/Internet_of_things)
• [Microsoft Learn: Active Directory Domain Services overview](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/get-started/virtual-dc/active-directory-domain-services-overview)