Small Office Network Setup: Preventing the Problems That Kill Productivity
The printer disappears on Monday morning. The POS system drops during a busy period. A new employee spends their first hour trying to find the shared drive. The router dies and nobody knows how it was configured.
These are predictable problems. They happen because the network was never properly documented, so every failure becomes a mystery.
Why small office networks break the way they do
In a home, a broken network is an inconvenience. In an office, it’s revenue.
The pattern is usually the same: devices are added without a plan, IPs are assigned randomly or left to DHCP, nobody documents anything, and the person who “knows how the network works” is either on holiday or has left the company.
When the printer gets a new IP from DHCP, nobody knows its old IP to compare against. When the router needs replacing, nobody has the DHCP reservations backed up. When a new employee starts, nobody can tell them where the file server actually lives.
The three things every small office network needs
1. Static IPs for shared resources
Any device that other people or systems depend on should have a stable address:
- Shared printers and scanners
- File server or NAS
- POS terminals and payment processors
- Security cameras and NVR
- VoIP phone system
- The router and any managed switches
DHCP reservations (set on the router, not the device) are the easiest way to do this. You assign the IP once, tied to the device’s MAC address, and it never changes — even if the device gets reset or replaced with the same MAC.
Employee laptops and phones can stay on DHCP. They don’t have dependents.
2. A simple addressing structure
Organise your address space by function. A workable structure for a small office:
| Range | Purpose |
|---|---|
| .1–.10 | Network infrastructure |
| .11–.30 | Servers and shared storage |
| .31–.60 | POS systems and critical business devices |
| .61–.100 | Shared office equipment (printers, etc.) |
| .101–.199 | DHCP pool (employee devices) |
| .200–.220 | Security cameras |
The specific ranges don’t matter. What matters is that they’re written down and consistent.
3. Written documentation
Three scenarios where documentation saves hours:
Monday morning printer failure. With documentation: check the printer’s assigned IP, ping it, confirm it’s online. Without documentation: 30 minutes of everyone reloading printer drivers and guessing.
New employee on their first day. With documentation: “File server is at 192.168.1.15, here’s the access path.” Without documentation: an hour of asking colleagues who aren’t sure either.
Router replacement. With documentation: restore DHCP reservations, reassign static devices, back online in under an hour. Without documentation: half a day of rebuilding configuration from scratch while the office is down.
What to document
For each device with a static IP, record:
- Device name and model
- MAC address (for DHCP reservations)
- Assigned IP
- What depends on it
- Any configuration notes
This doesn’t need to be elaborate. A shared spreadsheet works. An app like Netory works and gives you a structured, searchable inventory you can access from your phone when you’re on-site trying to diagnose something.
The guest network
Keep guest WiFi on a separate network that can’t see your business infrastructure. Customers browsing on your WiFi shouldn’t be able to see the file server or the POS system. Most modern routers have a guest network feature built in.
Starting today
If you haven’t documented your network yet, start with the critical devices — POS systems, file server, shared printers. Add everything else as you touch it.
The investment is an hour or two once. The return is every future problem taking minutes to resolve instead of hours.
Organise your office network in Netory — free for iOS and Android.