First, determine the scope of the problem

A report that “the internet is slow” can describe several different failures. One computer may have a Wi-Fi issue, everyone may be affected by the internet provider, or a business application may be struggling while general web browsing works normally.

Ask three questions before changing anything: Who is affected? What exactly fails? When did it start? Record whether the problem occurs on wired devices, Wi-Fi devices, or both. Note any recent equipment changes or power interruptions.

Problem: Everything loses internet access

Check whether local systems still work. Can employees reach a local file server or printer? If local traffic works but external websites do not, investigate the internet service, modem, firewall WAN connection, and DNS resolution. Check the firewall or router status page if you have authorized access.

If the office uses a managed firewall, collect the current alerts and WAN status before restarting it. A reboot may temporarily restore service but erase the evidence needed to find a recurring fault. If the internet provider has an outage, changing your internal network settings will not fix it.

Problem: Only Wi-Fi devices disconnect

Compare a device on wired Ethernet with the same type of task on Wi-Fi. If wired service stays stable, investigate coverage, access-point power, client roaming, wireless interference, and congestion. Do not assume the internet connection is bad just because a wireless laptop lost access.

Check whether problems happen near one access point or in a particular room. Metal shelving, building construction, neighboring Wi-Fi networks, and crowded channels can affect performance. Move or reposition access points based on observed coverage rather than adding equipment at random.

Problem: One computer is much slower than the others

Test the computer near a known-working network connection. A damaged Ethernet cable, outdated network driver, overloaded system, VPN client, or weak wireless signal may explain the difference. Compare the same website or application from a second machine rather than relying on one speed-test result.

Check whether Windows shows a disconnected adapter or an unexpected connection speed. If the problem appeared after a change, document the version or setting and consider a controlled rollback. Avoid resetting network settings across the office without a specific reason.

Problem: Websites fail by name but not by network address

This can indicate a DNS problem. Domain Name System (DNS) turns names into addresses, and business networks may use internal DNS for servers and authentication. A working internet connection does not prove DNS is configured correctly.

Check the DNS servers assigned to the affected device and whether other systems use the same configuration. Do not simply change a domain-joined office computer to a public DNS server as a quick fix; that may break access to internal resources. Fix the underlying DHCP or DNS configuration instead.

Problem: The network printer disappears

First determine whether the printer itself is online. Look for a valid network connection and address. Check whether the issue affects everyone or only one person and whether the printer's IP address changed. An unmanaged printer with an address assigned unpredictably can become difficult for client computers to locate.

Keep printers on documented addresses or appropriately managed reservations, update drivers when needed, and limit access according to the business's security requirements. If print jobs are stuck, inspect the print queue rather than reinstalling every workstation.

Keep a small network record before the next outage

  • Internet provider name and support number.
  • Firewall, switch, and access-point models and management ownership.
  • Network diagram and a record of important device addresses.
  • Recent configuration changes and scheduled maintenance.
  • Clear directions for staff: what to check and when to report an issue.

When to bring in help

Repeated outages, failed equipment, unexplained DNS changes, security alerts, or issues affecting production systems are reasons to stop guessing and perform a deeper review. A technician should be able to explain the evidence that points to a cause, not just which device was rebooted.

Reliable networks are rarely about one expensive component. They depend on proper design, consistent documentation, monitored equipment, and a methodical approach when something breaks.