Office internet not working? Checks to make before calling support

1. Find out who and what is affected

Ask someone in the same room to open two unrelated websites. Try the same sites on your computer. A phone used for comparison should be on the same Wi-Fi network; mobile data could otherwise hide an office connection failure.

If only one business application fails, check its service status page or contact the application provider. Working web browsing with an unavailable ERP system does not, by itself, justify changing the office network. If you work remotely, record whether the problem happens only when the VPN is connected.

• One device: start with that computer and its connection.
• Several devices, one application: investigate the application and its access requirements.
• Several devices, several services: investigate the shared network and internet connection.

2. Compare Wi-Fi with a wired connection

If your computer supports Ethernet, use a known working network socket and turn off Wi-Fi for the comparison. Repeat the same task. Success over a cable points the next investigation towards the wireless part of the network; it does not yet identify a faulty component.

Repeat the wireless test at your normal desk and closer to the access point. Record the room, time and network name. A useful example is: “At 10:15, the video call broke up in the meeting room; at the same desk, the wired connection worked.” This gives support a reproducible starting point.

3. Use the computer’s built-in diagnostics

Save your work and capture the error message before changing anything. Windows has connection troubleshooting tools; macOS has Wireless Diagnostics. Keep a record of the symptoms and their timing before taking steps that change the current state.

A Windows network reset is a last resort and can require VPN software to be configured again. Ask your administrator before doing this on a managed device. Do not disable security protection simply to try to restore access.

4. For broken calls, look beyond download speed

A fast file download does not guarantee a clear internet call. Packet loss and variation in delay, known as jitter, also affect voice traffic. Tell support whether audio arrives late, disappears intermittently or can only be heard in one direction.

Record the test call time, device and connection type. Compare wired and wireless calls with the same person where possible. Note any large file uploads happening at the same time. This is an observation to investigate, not proof that those uploads caused the problem.

5. Give support a useful handover

If the whole office is affected, check your internet provider’s outage notices and observe the equipment status without changing its configuration. Arrange a shared router restart with the team first: it also interrupts other people’s work and calls. A factory reset is not a routine first troubleshooting step.

Use the checklist below to prepare a short support request. Leave out passwords, login codes and screenshots containing personal information. If an outside provider manages the network, let that provider coordinate configuration changes.

• When the issue began and how often it happens.
• The affected devices, rooms and applications.
• Results from the two-device and wired/wireless comparisons.
• Recent changes such as new equipment, a moved desk, updates or VPN software.
• What you have already tried and what happened afterwards.

6. Turn recurring faults into a practical plan

Keep one incident log for repeat problems. A pattern can help you choose the next useful test: another desk, a wired connection, an access point review or a provider investigation. Avoid buying replacement hardware based on a single poor test.

When setting up computers or moving offices, list the users, desks, printers, phones and business applications. Define an acceptance check for each workstation: sign-in, application access, printing and a call. This makes the expected result of the setup clear to both your team and the installer.