When an office network becomes unstable, replacing the router is often the first reaction. But the same visible symptom can come from the internet provider, router, switch, access point, cabling, DHCP settings or one problematic device. Start by narrowing the failure boundary.
Define the failure scope before restarting equipment
Ask who is affected and how. If every device loses access at the same time, look at the internet connection, modem or gateway first. If only one room or group of desks fails, inspect the local switch, cabling or access point. If only one laptop fails, the endpoint is more likely than the whole network.
Also separate “no internet” from “no network.” A computer may still reach a printer or NAS while external websites fail. That points toward the internet edge or DNS rather than the entire office LAN.
Check the internet edge
Record the status lights and management-page information on the provider modem or optical network terminal. If possible, compare the failure time with provider notices. Avoid repeatedly factory-resetting provider equipment; that can erase settings and make the outage harder to diagnose.
If the provider link is stable but users still lose access, check whether the router remains reachable from inside the office. A router that stops responding locally has a different problem from a working router whose upstream connection has failed.
Router, DHCP and IP address problems
The router often provides the default gateway, DHCP addresses, DNS forwarding, firewall rules and sometimes Wi-Fi. Common issues include overloaded consumer hardware, expired DHCP pools, duplicate IP addresses, incorrect DNS settings, loops created by accidental cabling and firmware problems.
On an affected computer, record the assigned IP address, default gateway and DNS servers. An address beginning with 169.254 usually means the device did not receive a normal DHCP lease. If the gateway is reachable but domain names fail, test DNS before replacing the router.
Switch and cabling issues
A switch problem may affect one group of ports, a specific floor or all devices connected behind that switch. Look for unstable link lights, damaged cables, loose patch-panel connections, power problems, overheated equipment and loops between ports.
Do not move many cables at once without labeling them. Change one connection at a time and record the result. In a managed network, review port errors, negotiated speed, VLAN assignments and spanning-tree events.
Wi-Fi coverage and interference
Strong signal does not always mean good performance. Too many devices on one access point, congested channels, poor access-point placement, thick walls, automatic roaming behavior and interference can all cause slow or unstable service.
Compare a wired test with a Wi-Fi test at the same time. If wired service is stable, focus on access points and radio conditions. If both fail together, the problem is probably elsewhere.
What to record before requesting support
- Which users, rooms and device types are affected.
- Whether wired and wireless devices fail together.
- Whether local printers or NAS devices remain reachable.
- The exact failure times and frequency.
- Any recent cabling, equipment, provider or office-layout changes.
- Photos of equipment labels and status lights.
These details turn a vague “the network is unstable” complaint into a testable problem and reduce unnecessary equipment replacement.
Need help with this issue?
Email a short description, your location, and any screenshots or error messages. We will help identify the most sensible next step.