Before I was the detective, I was the building inspector. Before I walked into other people's server rooms and told them what was wrong with their infrastructure, I ran cable through my own house and learned what failure sounded like by listening to blinking lights in the dark.
The first LAN was 10BASE2. Thin Ethernet. Coax through the bedrooms, BNC T-connectors at every machine, and a 50-ohm terminator at either end telling the signal where the world stopped. It looked like plumbing and failed like a séance. This would have been the mid-nineties, before switches were cheap enough to throw at a home network, before Cat5 was something you bought at a retail store. ThinNet ran on a shared bus — one long coaxial segment with every device tapped in along its length. No switch. No router. No intelligence. Just a wire and a set of rules: listen before you talk, back off if someone else is talking, and pray to God nobody unplugs a terminator.
The bus ran through the bedrooms. Each room had a machine — the computers we used, the machines we were building, the projects that needed network access. The servers lived in the kitchen closet. Not a server room. Not a rack. A kitchen closet with the shelves rearranged to hold hardware, power strips bolted to the wall, cable routed through a hole drilled in the drywall. The domain name I'd register later — the one that still hosts my sites thirty years on — was named for that closet. Not as nostalgia. As a statement of origin.
The problem started slowly. Connections that used to be reliable started dropping packets. Not enough to kill anything outright — just enough to make things feel wrong. A file transfer that used to finish in seconds now stalled and resumed and stalled again. A ping across the segment that should have come back in under a millisecond was spiking to fifty, a hundred, then timing out entirely before snapping back to normal.
Intermittent. The most dangerous word in diagnostics. Not broken. Not working. Intermittent. The kind of problem that makes you doubt your instruments, your memory, and eventually your sanity, because every time you sit down to look at it, it's either happening and you can't isolate it or it's stopped and you can't reproduce it.
A shared bus has no tolerance for ambiguity. Every device is on the same wire. Every signal travels the full length of the segment. And the terminators at each end are the only things keeping those signals from bouncing back like echoes in a hallway, colliding with new transmissions, corrupting everything they touch. The bus works because the terminators absorb the signal at the boundary. When a terminator fails, the boundary fails, and the ghosts come back.
I checked the cables. I checked the connectors. I reseated every BNC T-connector on the segment. The problem would improve for a day, maybe two, then creep back. Packet loss climbing slowly, like a fever that breaks and returns.
It was the terminator cap. The one at the end of the line — the 50-ohm resistor that tells the signal this is the boundary, don't reflect back. When a terminator degrades, the signal bounces. Not cleanly, not all at once, but in partial reflections that corrupt the data frames passing through. The bus still carries traffic. The machines still talk. But the data is getting damaged in transit by its own echoes, and the error rate climbs so slowly that by the time you notice, you've been blaming everything else on the segment for weeks.
I swapped the terminator. The segment stabilized. Packet loss dropped to zero. The file transfers snapped back to speed. A fifty-cent component had been slowly poisoning a network that ran through every room in the house, and the fix was pulling it off the BNC connector and pushing on a new one.
Every job has a Jimmy. The mistake is thinking that tells you what kind.
The second failure came years later, after the ThinNet was gone and the house had moved to switched Ethernet — a proper hub, Cat5 to every room, the kitchen closet upgraded with better hardware and more drives and the kind of quiet hum that means everything is working.
Except one morning, it wasn't. The network was slow — not intermittent this time, but uniformly, persistently, miserably slow. Every machine on the LAN was crawling. And the switch was screaming about it.
I don't mean metaphorically. The activity lights on the switch — the little green LEDs that blink when data passes through a port — were solid. Not blinking. Solid. Every port lit up like a Christmas tree, traffic hammering through the switch fabric so fast that the individual blinks had merged into a continuous glow.
That's a broadcast storm. Something on the network was flooding every port with traffic — not targeted traffic, not useful traffic, just raw noise, frames being blasted into the switch faster than the switch could process them, filling every buffer, choking every port, drowning every legitimate packet in a sea of garbage.
Jimmy was a network card. A NIC in one of the machines had failed — not failed cleanly, not failed silently, but failed in the worst way a network interface can fail: it had started transmitting garbage at line speed. No pause. No protocol. No collision detection, no backoff, no waiting for its turn. Just raw electrical noise being pumped into the switch as fast as the hardware could generate it, and the switch had no choice but to forward it everywhere because that's what switches do with frames they can't make sense of.
I found it the way you find a broadcast storm on a small network: I pulled cables. One at a time. Watching the switch lights after each one. Pull a cable, check the LEDs. Still solid. Pull another. Still solid. Pull another — and the lights dropped to a normal blink pattern. The noise stopped. I looked at the cable in my hand, traced it to the machine, and pulled the NIC.
The network came back the moment the card left the slot.
When it breaks, everything breaks. Not elegantly. Not with useful error messages. The lights go solid or the bus goes haunted and you're down on your knees pulling cables because failures at this level don't announce themselves — they just stop the conversation and leave you listening to noise.
I learned that in a kitchen closet. Servers on shelves, cables through walls, a fifty-cent terminator that nearly killed a ThinNet segment and a five-dollar NIC that tried to drown a switch. The stakes were low. Nobody's enterprise was down. Nobody's quarterly numbers were at risk. It was just my house, my network, my family wondering why the internet was slow again and me crouched behind a switch in the closet pulling cables one at a time, watching the lights, learning to read the language of a layer that doesn't speak in words.
Every diagnostic skill I've ever used in a production environment — the instinct to watch the indicators, the patience to isolate by elimination, the knowledge that the simplest component can be the most destructive — I learned it there. In the closet. On my knees. Pulling cables until the noise stopped.
Case closed.