Three Months of Network Hell — Caused by a Camera System

The Symptoms

It started with intermittent complaints. "The internet feels slow." "Files take forever to open." "My VoIP calls keep dropping." The kind of vague, hard-to-pin-down issues that drive IT teams crazy because they happen randomly, can't be reliably reproduced, and disappear the moment you start investigating.

For three months, a professional services firm with about 50 users was plagued by network instability. Everything was blamed at one point or another: the internet service provider, the firewall, the switches, the wireless access points, individual workstations, and even the practice management software. Multiple vendors pointed fingers at each other. Tickets were opened and closed without resolution.

We were brought in to figure out what was actually happening.

The Investigation

We started where we always start: at the physical layer. Network troubleshooting follows a methodical process — you start at the bottom of the OSI model and work your way up. Before you blame software, you rule out hardware. Before you blame hardware, you rule out cabling.

The first thing we noticed was bandwidth utilization. The network's internal traffic was consistently saturated during business hours. Something on the network was consuming enormous amounts of bandwidth — far more than 50 users running typical office applications should generate.

We began systematically isolating network segments, monitoring traffic patterns on each switch port, and looking for the source of the congestion.

The Breakthrough

Three days into the investigation, we found it. The firm had recently installed a new camera security system. The vendor — a local company that primarily installed residential camera systems — had deployed a commercial-grade camera setup on the firm's production network. The cameras were streaming high-definition video across the same network that carried file sharing, email, VoIP, and internet traffic.

The system was massively under-specced for the environment. It was designed for a residential installation with 3-4 cameras, not a commercial deployment with 16 cameras streaming continuously. The bandwidth consumption was overwhelming the network infrastructure.

Here's what confirmed it: we disabled the uplink port on the switch that connected the camera system. The network problems stopped instantly. Three months of intermittent failures, vendor finger-pointing, and frustrated users — resolved by unplugging a single cable.

The Fix (and the Bonus Problem)

The camera vendor was confronted with the evidence and required to replace the entire system with hardware appropriate for a commercial environment on a dedicated VLAN — completely separated from the production network. The firm's leadership was understandably unhappy about three months of lost productivity.

But the story doesn't end there. During the camera system replacement, a cabling technician accidentally created a network loop — connecting both ends of the same cable to the same switch. This created a broadcast storm that brought the network down again, for entirely different reasons.

We identified the loop within minutes (at this point, we knew every cable in the building), removed it, and the network stabilized for good.

What This Means for Your Firm

This story illustrates several critical lessons:

1. Every device on your network affects your network. Camera systems, printers, personal devices, IoT gadgets — they all share bandwidth and can cause problems that look completely unrelated to their source.

2. Vendor accountability matters. The camera vendor was out of their depth in a commercial environment. They sold a residential solution for a commercial problem and cost the firm three months of degraded productivity. Always verify that vendors have experience in commercial environments before letting them touch your network.

3. Dedicated VLANs for non-essential systems. Camera systems, building management systems, and guest Wi-Fi should all be on separate network segments (VLANs) from your production environment. This prevents bandwidth competition and limits the blast radius of any issues.

4. Systematic troubleshooting works. Three months of guessing didn't solve this problem. Three days of methodical, layer-by-layer investigation did.

If your firm is experiencing intermittent network issues that no one can explain, there's always a cause. It just takes the right approach to find it.

Experiencing unexplained network issues? [Contact us for an assessment](#assessment) — we'll find what everyone else missed.