Available for Engagements · Spokane, WA

We find the problem.
We fix the problem.

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.

Response within 24h / Remote & on-site (Spokane) / No ticket queues
// 01 — services

Hands-on troubleshooting & support.

10 practice areas

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.

01

IT Troubleshooting & Diagnosis

Hardware, software, or networking — reproducible tests, clear hypotheses, and a written trail of what was checked and what was ruled out.

02

Network Fault Isolation

Slow connections, random drops, intermittent outages. Packet captures, path analysis and carrier-side investigation until the root cause is found.

03

Small Business IT Support

Infrastructure assessments, upgrade planning, and ongoing support for offices that have outgrown the founder's laptop but don't need a big MSP.

04

Server & Workstation Support

Setup, maintenance, migrations, recovery. Windows Server, Linux, Proxmox — bringing failed systems back online and keeping healthy ones healthy.

05

Self-Hosted Deployments

Own your stack — mail, NAS, monitoring, cameras, dashboards. Deployed on your hardware, hardened, and documented for whoever comes next.

06

Monitoring & Alerting

Zabbix, SNMP, syslog aggregation. Visibility into every switch, server and circuit — so the next outage is detected in minutes, not the next morning.

07

Thin Client & Endpoint Rollouts

Office-wide endpoint refreshes and thin client deployments — imaged, configured, labeled, and installed without burning your whole week.

08

Cabling, Switching & Wireless

Bad patch cables, noisy closets, Wi-Fi dead zones, channel chaos. Hands-on cleanup, proper labeling, RF surveys and switch hygiene.

09

Vendor & ISP Escalation

I talk to your carrier in their language. Packet captures, OSS ticket IDs, splice reports — whatever gets your ISP to stop blaming the router.

10

On-Call & Remote Support

Retainer-based coverage for businesses without internal IT. A direct line to someone who already knows your network when things go sideways.

// 02 — how i work

Investigate. Isolate. Resolve.

root cause, not symptom management
Step 01 · Investigate

Listen, gather, reproduce.

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.

  • Stakeholder interviews
  • Log & capture collection
  • Reproducible test cases
Step 02 · Isolate

Find the root cause.

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.

  • Top-down / bottom-up bisection
  • Packet capture & protocol analysis
  • Change correlation
Step 03 · Resolve

Fix it. Document it. Prevent it.

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.

  • Fix + validation plan
  • Runbook & topology handoff
  • Monitoring to catch recurrence
// 03 — why networkbound

Carrier-grade instincts. Solo-shop attention.

no ticket queue · no outsourcing
01

Real NOC background.

Years inside a carrier NOC, working telecom infrastructure daily. That operational discipline — runbooks, captures, escalation — carried over to every job I do now.

02

Methodical investigator.

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.

03

Enterprise gear, real production.

Cisco, Juniper, Nokia, UniFi — not just lab exposure. Production environments running real traffic, where "reload and see" isn't an option.

04

I handle the hard calls.

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.

05

Direct contact, always.

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.

06

Carrier-side fluency.

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.

// toolchain & technologies //
// 04 — engagements

How we can work together.

flexible scope · clear pricing
01 · remote

Remote Support

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.

  • Secure remote access
  • Hourly or retainer
  • Same-day triage
Worldwide · billed hourly
02 · on-site

On-Site (Spokane Area)

Cabling, rack work, hardware swaps, wireless surveys, new office standups. On-site when the problem can't be seen through a terminal.

  • Spokane & greater Inland NW
  • Half or full-day blocks
  • Written handoff included
Spokane, WA · mileage transparent
03 · project

Project-Based

Fixed-scope engagements — infrastructure assessments, self-hosted rollouts, monitoring deployments, migrations. Clear deliverables, clear price.

  • Scoped statement of work
  • Milestone billing
  • Documented handoff
Fixed price when possible
// 05 — contact

What are you dealing with?

Send me the symptoms. I'll take it from there.

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.

Response within 24 hours / Spokane, WA / Remote & on-site
// intake
Include:  1) what's broken  2) when it started  3) what changed recently  4) what you've already tried  5) who owns the gear (you, landlord, ISP). Screenshots, logs and error messages welcome — the more detail, the faster I can triage.