Instead, I asked a simple question: can these actually do something?

What followed was a weekend that taught me more about how networks actually work than any course had — mostly because things kept breaking, and I had no choice but to figure out why.

What you'll take away from this

• What a NAS is and why it's useful

• How WDS wireless bridging works

• What DHCP does (and breaks when doubled)

• How to build a simple home network setup

• Firewall + network profile basics

• Why hands-on is better than reading

The Idea: Turn the Dead PC into a NAS

My first thought was to turn the router into a Wi-Fi extender. Except I didn't have an Ethernet cable long enough to reach where I needed it. So I shifted focus to the old desktop instead, and landed on a much better idea.

📦 What is a NAS?

A NAS (Network Attached Storage) is a device on your home network that stores files and lets every device - laptop, phone, tablet access them over Wi-Fi. Think of it as your own personal Google Drive, sitting in your house instead of someone else's data center. You own the hardware, you own the data.

As someone learning Data Engineering and ML, this was genuinely useful. Datasets, notebooks, and project files were scattered across my laptop and cloud storage. One centralized place reachable from any device? That was exactly the kind of boring-but-useful infrastructure worth building.

Setting up shared storage on the old PC was the easy part — a shared folder, a few permission tweaks, done in under an hour. The hard part was something I hadn't even thought about yet.

The Problem: No Cable, No Internet

The old PC was nowhere near my main router. Running a long Ethernet cable across the house wasn't happening. This is where the spare TP-Link, abandoned ten minutes earlier, got a second chance.

Digging through its settings, I found something I'd never touched: WDS (Wireless Distribution System)

📡 What is WDS?

WDS lets one router connect to another wirelessly and act as a bridge, relaying internet from the main router to any device plugged into it, with no cable needed between the two routers. It essentially turns a spare router into a wireless repeater with a LAN port on the other end.

The TP-Link was bridged to the main router wirelessly without any issues. The internet should have just flowed straight down to the old PC. It didn't.

The Real Problem: Two Routers, Two Bosses

Devices connected through the TP-Link had no internet. No clear error, nothing obviously wrong — just silence where a connection should be.

After an hour of digging, I found the culprit: both routers were running DHCP at the same time.

🧠 What is DHCP?

DHCP (Dynamic Host Configuration Protocol) is what hands out IP addresses to devices when they join a network — like a receptionist assigning desk numbers in an office. Every router runs DHCP by default. The problem? When two routers both run DHCP on the same network, they hand out addresses from different ranges, effectively splitting your devices into two separate networks that can't talk to each other.

What Was Happening

• Airtel router handing out IPs in one range (e.g., 192.168.1.x)

• TP-Link router handing out IPs in a completely different range

• Devices on TP-Link couldn't reach the internet — they were on the wrong network segment

• Old PC, laptop, and phone couldn't communicate with each other

The Fix

• Disabled DHCP on the TP-Link router entirely

• Let the Airtel router be the single source of IP assignment for the entire network

• All devices immediately landed on the same network segment

• Internet started flowing through the wireless bridge — NAS accessible from everywhere

💡 The Rule

One network, one DHCP server. When bridging routers, always disable DHCP on every secondary router. Your primary router should be the only one handing out IP addresses.

The Smaller Gremlins Along the Way

The DHCP fix got things working, but a few more things needed sorting before everything ran cleanly:

🛡️ Windows Firewall

Was silently blocking file-sharing traffic. Had to add rules to allow SMB through the firewall before the NAS was reachable from other devices.

🌐 Network Profiles

Windows treats "Public" networks very restrictively — network discovery is disabled by default. Setting the network to "Private" unlocked device visibility instantly.

🔀 Browser Proxy

A leftover proxy setting on one device was rerouting traffic incorrectly. Cleared it and that device's connectivity immediately came back.

🔍 Debugging Method

Stopped guessing, started diagnosing, checking one layer at a time.

Physical → network → OS settings → application.

This order saves hours.

Up Next — Part 2

The NAS was step one. Once storage was solid, I wanted more: turn this old PC into a real server running Linux, hosting actual applications, accessible securely from anywhere in the world, not just my home network.

That meant Ubuntu Server, Docker, Nextcloud, PostgreSQL, Redis, and Tailscale. And, as you'd expect by now, a fresh batch of things that broke in ways I genuinely didn't see coming.