SMALL OFFICE / WIRED / WI-FI / VOICE
Build the evidence before
changing the network.
A dropped call, slow upload or unreachable server can start at the device, Wi-Fi, switch, firewall, DNS or internet circuit. Capture the path and isolate the failing layer before buying equipment or changing several settings at once.
Review one remote site — $295The assessment reviews evidence and recommends priorities. It is not emergency response or an implementation package.
Test the local gateway separately from the internet. A fast external speed test cannot prove that every internal path is healthy.
FIRST / DEFINE THE FAILURE
Turn “the network is slow” into
evidence someone can use.
Record when it starts and stops
Use exact times and time zone. Note whether the problem follows a schedule, a backup, a large upload, a shift change or an ISP event.
List affected and unaffected devices
Compare one wired device, one wireless device and a known-working device. State whether phones, payment terminals, printers, servers or only one application are affected.
Name the destination
Separate a local server or printer from a public website or cloud application. Record the hostname and service, but do not put passwords, private configurations or customer data in an inquiry.
Describe the business consequence
Say whether staff can work, calls drop, payments stop, files fail to save or performance is merely slower. Impact determines priority and the safest test window.
SECOND / MAP WHAT EXISTS
A useful diagram can fit
on one page.
ISP handoff, router and firewall
Record vendor, model, support status and who administers each device. Identify whether the ISP gateway also performs routing, Wi-Fi or firewall duties.
Switches and physical links
Map the uplinks, link speeds and devices connected to each switch. Unexpected 100 Mbps links, loops, errors or a single overloaded uplink can shape the whole office.
Access points and coverage
List access points, wired uplinks, SSIDs and the areas they serve. Compare signal and performance at the failing location with a known-good location.
Addressing, DNS and voice
Record which system provides DHCP and DNS, the intended subnets or VLANs, and how business phones connect. Duplicate address services and unintended DNS paths can create intermittent failures.
THIRD / ISOLATE BEFORE REPAIR
Change one layer,
then retest the same path.
Local before external
Check link state, the assigned address, default gateway and local gateway latency before testing DNS and internet reachability. Keep the same device and time window when comparing results.
Wired before wireless
If a wired client is healthy while Wi-Fi clients fail, focus on access points, channels, roaming, cabling and wireless policy. If both fail, move outward to switching, firewall and ISP evidence.
Name resolution separately
Test whether a destination fails by name but works by address. That distinguishes a likely DNS path from a broader connectivity failure without treating a temporary IP test as the repair.
Rollback before change
Export the current configuration, record the exact change and define how to restore it. Do not update firmware, replace hardware and rewrite policy in the same troubleshooting step.
DESIGN / KEEP THE OFFICE SUPPORTABLE
Separate by purpose and
document the required flows.
Keep devices and firmware current
CISA recommends current device and firmware inventories because visibility starts with knowing what is connected and supported.
Group devices by communication need
NIST describes security segmentation as grouping assets by communication and security requirements. Guest devices, payment systems, cameras and office computers should not be assumed to need the same access.
Protect management with MFA
CISA recommends MFA for remote access and privileged administration. Use named accounts, limit management exposure and remove access that no longer has an owner.
Back up and test the configuration
Store current configurations away from the device and record license, support and replacement information. A backup that has never been read or restored is not a recovery plan.
URBANBYTEZ / FIXED STARTING POINT
Know what the $295 assessment
does and does not buy.
A $295 USD technology assessment covers up to 90 minutes for one remote site or one workflow, followed by written priorities and a proposed next step. It can review the symptoms, current path, available evidence and the smallest useful next action. It does not include implementation, equipment, cabling, penetration testing or ongoing support. Any follow-on work is separately scoped and quoted before it begins.
Useful inputs include a redacted topology, device models, support status, exact symptom times, affected device groups and results from the same repeatable tests. Do not send passwords, private keys, full configuration exports, public-management links or customer data through the public form.
An inquiry is free. Payment terms and the complete assessment scope are available before checkout.
AUTHORITATIVE GUIDANCE
Further reading from
CISA and NIST.
CISA’s network visibility and hardening guidance covers device inventory, firmware, VLAN grouping and protected administration. CISA’s small-business MFA guidance calls for MFA on remote and privileged access. NIST CSWP 28 explains grouping assets by communication and security requirements.