Services of Networked Hosts: Server Roles, Internet Appliances, SCADA, and IoT
Unit 2: Networking Fundamentals. Lesson 9 of 41 in APlus Academy Core 1.
Servers are named for the service they provide. The exam describes a need and asks which server or appliance fulfills it, or names a server and asks what it does.
Core server roles
- DNS server: turns names into addresses. Every client needs one; a wrong DNS setting breaks "the internet" while pings to addresses still work.
- DHCP server: hands out IP addresses, masks, gateways, and DNS servers for a lease period. Usually the router at home, a Windows or Linux server at work.
- File server (fileshare): shared folders over SMB (Windows) or NFS (Unix), with permissions.
- Print server: manages shared printers, their queues, and drivers so clients do not each hold a direct connection.
- Mail server: sends with SMTP and lets clients read with IMAP or POP3; often hosted in the cloud now.
- Web server: serves pages over HTTP and HTTPS; internal web apps run on one too.
- Syslog server: collects log messages from switches, routers, firewalls, and servers in one place, so a problem can be traced across devices.
- AAA server (authentication, authorization, and accounting): authentication is who are you, authorization is what may you do, and accounting is what did you do. RADIUS and TACACS+ are the protocols; enterprise Wi-Fi and VPNs check credentials against one.
- Database server: stores structured data for applications (SQL).
- NTP server: time. Authentication and certificates fail when clocks drift, so every device syncs to one.
Internet appliances
- Spam gateway: filters inbound mail for spam, phishing, and malware before it reaches the mail server.
- UTM (unified threat management): a firewall, intrusion detection and prevention, antivirus, content filtering, and VPN in one appliance; common in small and mid-size businesses.
- Load balancer: spreads client requests across several identical servers so one failure or one busy server does not take the service down.
- Proxy server: fetches web content on behalf of clients. It caches popular pages, enforces content filtering, logs who went where, and hides internal addresses. Browsers may need the proxy address configured.
Legacy and embedded systems
SCADA and other industrial control systems run factories, water plants, and building controls. They are often old, cannot be patched, and were never meant to be on the internet. Keep them on their own isolated network segment and never plug a random laptop into one.
Internet of Things
Smart thermostats, cameras, door locks, speakers, light bulbs, and appliances are all small computers with radios. They ship with default passwords, rarely get updates, and are a favorite entry point for attackers. Put them on a separate VLAN or guest network, change the passwords, and update the firmware.
Services of Networked Hosts: Server Roles, Internet Appliances, SCADA, and IoT, explained slowly
Servers are named after the favor they do
A server is any computer that answers requests, and its role is simply the request it answers. Rather than memorize a list, connect each role to the moment a user would notice it missing. That is how the exam frames it: "users report X; which server is down?"
What breaks when each server fails
server what it provides what users see when it fails DNS names to addresses "the internet is down" but IP pings work DHCP addresses by lease 169.254 addresses; new devices cannot connect file shared folders (SMB, NFS) mapped drives disappear; "network path not found" print shared queues and drivers jobs stuck; printers vanish from the list mail SMTP out; IMAP or POP3 in no send or receive web HTTP and HTTPS pages site unreachable; internal apps down syslog central log collection nothing visible to users; blind admins AAA RADIUS or TACACS+ authentication Wi-Fi and VPN logins fail for everyone database SQL data for applications apps open but show errors or no data NTP time logins and certificates fail as clocks drift
Notice that DNS and DHCP failures look like network failures, and AAA and NTP failures look like password failures. Reading the symptom correctly is the skill.
Appliances at the edge
appliance job where spam gateway filters inbound mail before the mail server in front of the mail server UTM firewall + IDS/IPS + antivirus + content filter + VPN at the internet edge, small and mid-size offices load balancer spreads requests across several identical servers in front of web or application servers proxy fetches web content for clients; caches, filters, logs between users and the internet
A load balancer gives availability and scale: three web servers behind one address, and one can fail unnoticed. A proxy gives control: the school blocks gaming sites, the company logs browsing, and popular pages load from the cache. A UTM gives a small business enterprise-style security in one box that one person can manage.
Worked example: the Monday morning outage
On Monday, Wi-Fi users cannot sign in, but wired PCs work. Wireless uses enterprise authentication against a RADIUS server (AAA). The wired PCs signed in with cached credentials. The AAA server is the suspect, or its clock is wrong (NTP), since certificate checks are time-sensitive. Pull the logs from syslog to confirm.
Worked example: which appliance
A company's public website slows to a crawl during promotions and goes down when a server reboots. The answer is a load balancer with two or more web servers behind it. If instead the complaint were "employees waste bandwidth on video sites," the answer would be a proxy with content filtering. If it were "we get phishing mail every day," a spam gateway.
The fragile ones
SCADA (supervisory control and data acquisition) and other industrial control systems drive pumps, conveyors, HVAC, and power equipment. They often run operating systems that stopped receiving updates a decade ago, and a reboot can halt a production line. The rules: keep them on an isolated network segment, allow only the specific connections they need, never let them see the internet, and never run a scan or plug in an unknown laptop without the operators' agreement.
IoT devices are the opposite problem: cheap, numerous, and internet-facing by design. Smart TVs, thermostats, cameras, doorbells, and speakers ship with default passwords and weak firmware. Change the passwords, update the firmware, and put them on a separate VLAN or the guest network so a compromised camera cannot see the file server.
How the exam asks it
- "Which server translates hostnames to IP addresses?" DNS.
- "Which protocol family does an AAA server use?" RADIUS or TACACS+.
- "Which appliance distributes client requests among multiple servers?" A load balancer.
- "Which device caches web pages and filters content for a network's users?" A proxy server.
- "Which appliance combines firewall, IPS, antivirus, and content filtering?" A UTM.
- "How should a legacy SCADA system be connected?" On an isolated network segment.
- "What is the first security step for a new smart thermostat?" Change the default credentials and update the firmware; place it on a separate network.
What to memorize
- The server table: DNS, DHCP, file, print, mail, web, syslog, AAA, database, NTP, and each failure symptom.
- Spam gateway, UTM, load balancer, proxy: what each does and where it sits.
- SCADA and legacy: isolate. IoT: change defaults, patch, segregate.