AP Networking 2.4: Media Server Setup and the AI Audit

A media server stores files on one device and streams them to every other device on your local network: fast, free of internet data use, and still working when the ISP goes down. Setup takes six steps, and because this is exactly the job people hand to an AI assistant, this guide also teaches the four-check audit that grades any AI suggestion: accept, correct, or reject.

This is Topic 2.4 of AP Networking Unit 2. The lab network from 2.1 through 2.3 is documented and upgraded; now it gets its first shared service. Two skills land together: configuring a real media server, and grading AI network advice against evidence instead of faith. Both show up on the exam and in any real IT job.

• What is a media server?
• Why stream locally instead of from the cloud?
• Choosing the host device
• Static IP vs DHCP reservation
• The six-step setup runbook
• The AI audit: four checks
• Accept, correct, or reject: three worked audits
• Practice: AI Audit
• Key terms
• Frequently asked questions

What is a media server?

A media server is a LAN device that stores files centrally and streams them to the other devices on the network. One copy of the movie library, game installers, or class tutorial videos lives on the server; every laptop, console, and TV in the building plays from it. One build covers all three uses: local file storage, gaming, and video streaming. None of it requires the internet, because clients and server share the same local network.

In the Unit 2 scenario, the lab team sets one up so project files and tutorial videos live in one place. The deliverable is not just a working server but a runbook: a setup procedure an absent teammate could rebuild the server from, without asking a question.

Why stream locally instead of from the cloud?

Local streaming keeps every packet on the LAN, which changes three things.

Property	Local media server	Internet streaming service
Speed	LAN speeds, no buffering contest with the neighborhood	Limited by your internet plan
Data usage	Zero internet data used	Every stream counts against a cap
ISP outage	Keeps playing; the stream never leaves the building	Dead until service returns
Reach	Home or lab only, unless deliberately and securely exposed	Anywhere with internet

The last row is the honest trade-off: the library is only reachable on your own network. Remote access is possible, but it is a deliberate decision with security work attached, never a default. An AI assistant that casually opens your server to the internet has made that call for you; the audit below exists to catch it.

Choosing the host device

The host is the machine the library lives on. The choice is three requirements read together:

• Always on. A server that sleeps or leaves the room takes the library with it. A laptop that goes home at 3 pm fails.
• Wired. The server carries every stream at once, so it gets the most reliable link in the building: Ethernet to the switch or router, not Wi-Fi airtime shared with the clients.
• Enough storage. Size the drive for the library plus growth. A 32 GB tablet is not a media server.

In the lab, the wired desktop that stays on all day with a 2 TB drive wins. Clients can be anything, wireless included; only the server side needs the guaranteed link.

Static IP vs DHCP reservation

Clients find the server by its IP address, so that address must never change. DHCP (from 2.3) leases addresses from a pool, and a lease can change after a reboot: the server works all week, the router restarts, it returns at a new address, and every client's saved connection breaks. Two fixes exist:

• Static IP: configure the address on the server itself, outside the DHCP pool. The lab uses 192.168.1.20, safely below its pool of 192.168.1.100-199.
• DHCP reservation: the router always leases the same address to the server's MAC. The server stays on automatic settings; the router does the remembering.

The six-step setup runbook

The whole build, in dependency order. Each step needs the one before it, which is why the runbook is numbered, not a checklist to wander through.

1. Choose the host. Always on, wired, enough storage. Confirm all three against the documentation, not from memory.
2. Fix the address. A static IP outside the DHCP pool, or a DHCP reservation for the host's MAC on the router.
3. Install the server software. Enable the sharing protocols clients will use to browse and stream the library.
4. Set permissions. Create accounts and limit access to intended users. Shared with the team does not mean open to everyone.
5. Verify from a client. On a different device, browse to the server and stream a test file. Until a real client plays a real file, the server is installed, not configured.
6. Document it. Record the host, address, accounts, and settings in the shared network map. The runbook test: a teammate can rebuild everything from what you wrote.

Step 6 is the collaboration skill this topic grades. Networks are maintained by teams; a configuration living in one head fails exactly when that head is out sick.

The AI audit: four checks

An AI assistant will happily draft this entire build in seconds, confident and detailed. Some of it will be right; the audit finds out which part. Run every AI-generated design, configuration, or troubleshooting suggestion through four checks before anyone acts on it:

#	Check	The question you ask
1	Match the documentation	Does it fit the real addresses, devices, and media in your map from 2.2 and 2.3? Advice naming a device you do not have describes someone else's network.
2	Internal consistency	Do the steps agree with each other and the stated goal, or does step two undo step one?
3	Cheapest-first	Does it start with the simple, low-cost action the evidence supports, or jump straight to replacing hardware?
4	Security risk	Does it open ports, disable encryption, or keep default credentials? A fix that works but weakens the network fails.

The audit ends in one of three verdicts, always justified with evidence: accept (passes all four checks), correct (right idea, fixable error), or reject (misdiagnosed, contradictory, or unsafe). In practice the most common verdict is correct: fluent AI drafts are usually one detail wrong, and the technician's job is knowing which.

Accept, correct, or reject: three worked audits

Accept. A desktop shows 169.254.44.9 and cannot reach anything. The AI says: "DHCP never answered, so the desktop self-assigned an address. Check the patch cable and the switch port before touching the router." It matches the 169.254 evidence from 2.2, stays consistent, starts with the cheapest suspects, and weakens nothing. Accept, and write down why.

Correct. The AI drafts: "Give the media server the static address 192.168.1.150." Static is exactly right, but the DHCP pool is 192.168.1.100-199, so .150 is the pool trap. Keep the plan, move the address outside the pool or convert it to a reservation. One detail fixed, the rest kept.

Reject. Goal: lab devices stream from the server. The AI suggests opening port 32400 on the router and disabling the server password "so logins never fail." Two checks fail at once: the LAN-only goal needs no internet exposure, and removing the password removes authentication. Reject, both reasons recorded. Notice: the suggestion would technically work, and it is still wrong.

Practice: AI Audit

Warm up with three sample questions, then work the case file: AI suggestions paired with evidence, and the verdict must survive both.

Three free sample questions

1. The AI assigns your server 192.168.1.150; your DHCP pool is 192.168.1.100-199. What is the verdict?

Show answer

Correct it: static is the right plan, but the address sits inside the DHCP pool and risks a conflict. Move it outside or set a reservation (EK 2.4.A.6, 2.4.B.3).

2. Which host should hold the library: a wired desktop that stays on with a 2 TB drive, or a laptop with the same drive that leaves every afternoon?

Show answer

The desktop. The host must be always on, wired, with enough storage; the laptop fails always-on (EK 2.4.B.2).

3. The ISP goes down for the evening. What happens to a stream from the local media server?

Show answer

It keeps playing. Local streams never leave the LAN, so an internet outage cannot touch them (EK 2.4.B.7).

Now the full case file, shuffled every run.

Key terms

Media server

A LAN device that stores files centrally and streams them to other devices.

Host

The machine the server runs on: always on, wired, sized for the library.

Static IP

An address configured on the device itself, placed outside the DHCP pool.

DHCP reservation

A router rule that always leases the same address to one MAC.

Sharing protocol

The language clients use to browse and stream from the server.

Permissions

Account-level rules controlling who can reach the library.

Runbook

A written procedure a teammate can follow start to finish without help.

AI audit

Four checks on any AI network suggestion: documentation match, consistency, cheapest-first, security risk. Ends in accept, correct, or reject.

Frequently asked questions

What does a media server do?

It stores files on one device and streams them to other devices on the same local network: movies, game libraries, or shared project files. Traffic stays on the LAN, so it is fast and uses no internet data.

Does a media server need the internet?

No. Server and clients talk over the LAN, so streaming works during an ISP outage. Internet only matters if you deliberately expose the library for remote access, a security decision, not a default.

What device should I use as the host?

One that is always on, wired, and has enough storage for the library. A desktop or small dedicated server fits; a laptop that leaves or a tablet with small storage does not.

Why does my media server keep disappearing from client devices?

Its IP address is probably changing with each DHCP lease or reboot. Give it a static address outside the DHCP pool or a DHCP reservation so clients always find it at the same address.

What is the difference between a static IP and a DHCP reservation?

Both give the server a permanent address. A static IP is set on the server itself, outside the DHCP pool; a reservation is set on the router, which always leases that address to the server's MAC.

Do I need to set permissions on a home media server?

Yes. Permissions decide which accounts reach the library. Even at home, shared does not mean public: guests on your Wi-Fi should not see every file you store.

Can I trust an AI assistant to configure my network?

Use it to draft, never to decide. Audit every suggestion: documentation match, consistency, cheapest-first, security risk. Then accept, correct, or reject it with a reason.

Why write a runbook instead of just setting the server up?

Networks are maintained by teams. A runbook lets a teammate rebuild the server when you are not there, and writing it exposes steps you did from memory but never verified.

AP is a trademark of the College Board, which was not involved in the production of, and does not endorse, this resource.