A slow or dropping network connection can bring an office to a standstill. Here are 6 practical tips for troubleshooting common business network issues.
Network problems are among the most disruptive IT issues a business can face. Unlike a single broken application, a network outage or degradation affects every user and every system simultaneously. Knowing how to diagnose the problem quickly — and when to escalate — saves time and reduces the frustration that comes with sitting on hold with your ISP while your team is idle.
Tip 1: Isolate Whether It Is Your Network or the Internet
The first question to answer in any connectivity complaint is: is the problem affecting internal network connectivity, internet access, or both?
Test internet access: Open a browser and try loading multiple websites. If all fail, the issue is likely with your internet connection or modem/router. If some load slowly and others fail, the issue may be with specific DNS resolution or external services.
Test internal connectivity: Can staff access shared drives, internal applications, and printers? If internal resources are accessible but internet is not, the problem is between your router and your ISP — not your internal network.
This distinction immediately narrows the diagnosis and determines whether you need to contact your ISP or focus on your internal equipment.
Tip 2: Reboot the Right Equipment in the Right Order
The most common fix for connectivity problems remains rebooting networking equipment. But order matters:
- Modem/NBN device: Power off, wait 30 seconds, power on. Wait for all lights to stabilise (usually 2-3 minutes).
- Router/firewall: Power off, wait 30 seconds, power on after the modem is fully back online.
- Managed switches: Reboot after the router is stable.
- Access points: Last in the sequence, after switches are online.
Rebooting in the wrong order — particularly bringing the router online before the modem has a stable connection — often results in a partial restoration that appears to fix the problem but leaves intermittent issues.
Tip 3: Check for a Specific Device or Location Pattern
If some users are affected but not others, the problem is almost certainly not your internet connection. Look for a pattern:
- All users on one floor/area: Check the switch and cabling for that segment
- Wireless users only, wired users fine: Wireless infrastructure (access points or wireless controller) issue
- Specific users regardless of location: Could be device-specific (DNS settings, network adapter, IP conflict)
- All users simultaneously: Core infrastructure or internet connection
Identifying the pattern before calling your IT support saves time and helps your technician prepare the right tools before attending.
Tip 4: Check for IP Address Conflicts
An IP address conflict — where two devices have been assigned the same IP address — causes intermittent connectivity drops for one or both affected devices. This often presents as a device that works fine and then suddenly loses connectivity, regains it, and repeats.
Windows will typically show a notification about an IP conflict. You can also identify conflicts through your router’s DHCP lease table — look for the same IP assigned to two different MAC addresses.
The fix is usually to release and renew the IP address on the affected device (ipconfig /release followed by ipconfig /renew in Command Prompt on Windows), or to ensure your DHCP scope has sufficient addresses for your environment.
Tip 5: Run a Speed Test and Compare to Your Plan
Before calling your ISP to report a slow internet connection, run a speed test from a wired device (not Wi-Fi) directly connected to your router. Use a reputable tool like fast.com or speedtest.net and test multiple times.
Note the results and compare them to what you are paying for. If you are on a 100/20 Mbps NBN plan and getting 5/2 Mbps from a wired connection, you have data to support an ISP fault report. If you are getting near-plan speeds but staff are complaining about slowness, the bottleneck may be elsewhere — network congestion, a specific application, or wireless performance.
Tip 6: Know When to Escalate
Self-troubleshooting has a natural ceiling. Escalate to your IT provider when:
- The reboot cycle has been attempted without resolution
- You have identified a pattern but cannot identify the cause
- The issue has persisted for more than 30 minutes
- You suspect a hardware failure (switch, router, firewall)
- You are seeing unusual traffic or behaviour that might indicate a security incident
When escalating, provide your IT provider with: what has changed recently (new devices, new software, recent changes to network equipment), when the problem started, what you have already tried, and the pattern of who is affected.
This information allows a skilled technician to diagnose remotely in many cases, or to arrive on-site prepared with the right equipment.
Proactive Network Management
Reactive troubleshooting is always more expensive than proactive monitoring. A quality managed IT provider monitors your network infrastructure continuously — detecting failing equipment, bandwidth saturation, and configuration issues before they cause outages.
CX IT Services includes proactive network monitoring in our managed IT service for all Melbourne clients. Contact us to discuss how we can reduce network downtime at your business.
