7
Two hours on a phantom network issue that turned out to be a cable tie
Spent a whole afternoon last Tuesday chasing a network dropout for a client's office in Denver. Every device would lose connection for exactly 30 seconds every hour or so. Checked the switch logs, ran ping tests, swapped out a patch cable, even updated the firmware on the router. After two hours I finally looked behind the desk and saw a cable tie cinched way too tight around the main Cat6 run. It was pinching the cable just enough to cause intermittent packet loss when the heat kicked on and the office settled. Felt like an idiot but also kind of pissed that something so dumb could chew up that much time. Has anyone else wasted a day on a fix that simple? What's your go to first thing you check now after getting burned?
2 comments
Log in to join the discussion
Log In2 Comments
jana1799d ago
My buddy Chris had a server in a small law office that would crash every Tuesday at 2pm. Three weeks of rebooting, swapping RAM, reimaging the drive. Finally found an admin assistant had a space heater plugged into the same power strip as the server. Kicked the breaker every Tuesday when she turned it on after lunch. @rowan593 your point about ties doing a job reminds me - that cable was probably fine for months until a vent or something shifted.
3