IT Troubleshooting & Diagnosis
Hardware, software, or networking — reproducible tests, clear hypotheses, and a written trail of what was checked and what was ruled out.
networkbound.net is the independent IT practice of Connor Anderson — a carrier-grade NOC technician turned solo IT pro. I troubleshoot slow connections, intermittent outages, ugly networks and the kind of hard calls most help desks escalate past. Methodical investigation, real root-cause fixes, documented and done.
If something's broken, flaky, or nobody else can figure it out — that's the work. From a single workstation that won't behave to a multi-site network throwing ghosts, I investigate, isolate, and resolve.
Hardware, software, or networking — reproducible tests, clear hypotheses, and a written trail of what was checked and what was ruled out.
Slow connections, random drops, intermittent outages. Packet captures, path analysis and carrier-side investigation until the root cause is found.
Infrastructure assessments, upgrade planning, and ongoing support for offices that have outgrown the founder's laptop but don't need a big MSP.
Setup, maintenance, migrations, recovery. Windows Server, Linux, Proxmox — bringing failed systems back online and keeping healthy ones healthy.
Own your stack — mail, NAS, monitoring, cameras, dashboards. Deployed on your hardware, hardened, and documented for whoever comes next.
Zabbix, SNMP, syslog aggregation. Visibility into every switch, server and circuit — so the next outage is detected in minutes, not the next morning.
Office-wide endpoint refreshes and thin client deployments — imaged, configured, labeled, and installed without burning your whole week.
Bad patch cables, noisy closets, Wi-Fi dead zones, channel chaos. Hands-on cleanup, proper labeling, RF surveys and switch hygiene.
I talk to your carrier in their language. Packet captures, OSS ticket IDs, splice reports — whatever gets your ISP to stop blaming the router.
Retainer-based coverage for businesses without internal IT. A direct line to someone who already knows your network when things go sideways.
Start with the humans. What broke, when, what changed? Pull logs, captures, configs — and get the failure to happen on demand whenever possible. Assumptions get written down so they can be tested.
Narrow it layer by layer. L1 cabling to L7 application, carrier edge to endpoint. I don't stop at the first thing that makes the alarm quiet — I stop when the chain of causation holds up under questioning.
Implement the fix, validate under load, and leave behind diagrams, runbooks and alerting so the same problem doesn't own your afternoon six months from now.
Years inside a carrier NOC, working telecom infrastructure daily. That operational discipline — runbooks, captures, escalation — carried over to every job I do now.
No guessing. No "have you tried turning it off and on again" as a theory of causation. I dig until the failure mechanism is understood and documented.
Cisco, Juniper, Nokia, UniFi — not just lab exposure. Production environments running real traffic, where "reload and see" isn't an option.
Not just help desk. Deep technical triage — the calls that would normally get kicked to tier-3, or get stuck forever bouncing between vendors blaming each other.
You email me. I answer. The person on the keyboard is the same one who took the call. No junior tech dispatched, no offshore handoff.
Optical fiber, DWDM, MPLS, carrier peering — I can work problems most IT shops literally can't touch. If your ISP is the culprit, I'll prove it.
SSH, VPN, screen share. For most troubleshooting and monitoring work, I don't need to be in the room — and you don't need to pay a drive charge.
Cabling, rack work, hardware swaps, wireless surveys, new office standups. On-site when the problem can't be seen through a terminal.
Fixed-scope engagements — infrastructure assessments, self-hosted rollouts, monitoring deployments, migrations. Clear deliverables, clear price.
Describe what's broken, when it started, what you've already tried, and what "fixed" looks like. I'll reply within one business day with a scoped plan — remote triage, on-site visit, or a written project quote.
[email protected] →