Guide G7 Networking & connectivity
Firewall, Wi-Fi, and VPN decisions need an owner - not just a working connection.
This guide is about physical connectivity: firewalls, business Wi-Fi, VPN, and site-to-site links. If you were looking for NexDefend's own directory of owned brands, that lives on the network page; this guide is about the equipment and ownership decision itself, not the NexDefend brand register.
G7 · Entry 01 Three different connectivity jobs
Name the job before naming the equipment.
Wi-Fi or a link is down now
A specific location, floor, or connection has stopped working. Bring the location, device, and when it last worked.
No one owns the firewall or Wi-Fi configuration
Guest access, VPN, and admin credentials have accumulated with no named owner or change record.
You are choosing new gear, an ISP, or an SD-WAN design
A new location, a contract renewal, or repeated failures point to a scoped connectivity project instead of a repair.
G7 · Entry 02 Decision matrix
Match the symptom to the right first route.
| Observed need | Best first route | Useful evidence | Boundary |
|---|---|---|---|
| Wi-Fi keeps dropping in part of the office | Support | Location, device, signal pattern, access-point model | Not a full network redesign |
| No one can say who has firewall admin access | Managed IT | Device inventory, admin list, last change date | Not a penetration test |
| You're opening a site or changing ISP | Scoped project | Site plan, bandwidth need, downtime tolerance | Not a same-day install |
| Guest and staff traffic share one flat network | Managed IT or a scoped project | Current SSID list, segmentation status | Not a compliance certification |
G7 · Entry 03 Prepare the brief
Bring these facts to a connectivity conversation.
- Number of sites, and whether they need to reach each other.
- Current ISP(s), contract terms, and any recent outage history.
- Firewall or router make, model, and who manages it today.
- Wi-Fi coverage complaints by location and time of day.
- Whether guest, staff, and device networks are separated.
- Any insurer or client requirement naming a network control.
G7 · Entry 04 What this covers
What this guide covers, and what it does not.
- In scope
- Separating a support ticket from an ownership gap or a scoped install/upgrade project, and the evidence each route should ask for.
- Out of scope
- ISP contract negotiation, physical cabling estimates, and specific firewall or access-point brand recommendations.
- Possible next decision
- A support ticket, ongoing network ownership, or a scoped connectivity project with its own start and end date.
G7 Next
Choose ownership or a project - not just a repair.
Compare the owned-brand doors built for ongoing network ownership. Call quality on VoIP systems often depends on this same network picture.