Gathering evidence for a network problem
Narrow down a business network problem with quick self-checks and recorded errors, and leave changes to shared equipment and security settings to IT.

When a service stops working, record the pattern before changing settings. A useful report can help IT distinguish a device problem, a local connection issue and a failure in the service you’re trying to reach.
Start with checks you’re allowed to do on your own device. Don’t reboot shared network equipment or disable security controls as a general troubleshooting step.
Describe the failure precisely
Record the service, time, error message and action that failed. Say whether it never works, fails intermittently or became slow after a particular change.
Ask who else is affected. If it’s only you, the cause is most likely your device or its connection. If the whole office has lost the internet, the shared connection or the provider is the more likely place to look.
If you’re allowed to, try the same task on another device, such as a phone on the same Wi-Fi. If that works, the problem is most likely your device. A successful test narrows the problem down, but the rest of the network could still have a fault.
Include whether you’re on Wi-Fi, a cable or the company VPN. Keep passwords, tokens and customer information out of screenshots.
Check the immediate connection
Look for an unplugged cable, a disconnected dock or a device showing the wrong Wi-Fi network. Reconnect an ordinary workstation cable only where you know what it serves.
If power or status lights look unusual on shared equipment, record that for IT. Avoid moving labelled network connections or power supplies that may serve phones, access controls or another work area.
A normal light tells you something about the device or link. It doesn’t mean a cloud application will work.
Try the quick fixes on your own device
Microsoft’s Wi-Fi troubleshooting steps start with checks anyone can do on a Windows computer:
- Check that Airplane mode is off and Wi-Fi is on, under Settings > Network & internet.
- Restart the computer. Closing the lid or locking the screen isn’t the same thing.
- If your desk has a network cable or a dock you normally use, try the task with it plugged in. If the cable works and Wi-Fi doesn’t, tell IT the problem looks wireless.
Note what you tried and what happened, so IT doesn’t repeat it.
Check the Wi-Fi signal
Look at the bars on the Wi-Fi icon in the taskbar. If there are only one or two, move closer to the wireless access point, with fewer walls in between, and try again.
Apple’s guide to wireless interference lists common sources: microwave ovens, cordless phones, wireless video cameras, fluorescent lights and power cables. It also notes that plaster, concrete and especially metal block the signal far more than wood or glass. Wi-Fi and Bluetooth share the 2.4 GHz band, so it can get crowded. If the office offers a 5 GHz network, IT can tell you whether to use it.
Patterns help here. “Only in the back meeting room” or “only around lunch, near the kitchen” points IT in a useful direction. If the whole office is slow on Wi-Fi, the slow office Wi-Fi guide covers what your provider should look at.
Separate reachability from application access
IT may compare name resolution, connection establishment and the application’s response. A sign-in or permission error can look like a network problem to the person trying to work.
Ask IT which diagnostic tests they want you to run. Microsoft’s tracert documentation describes tracing a route, including cases where routers don’t reply. Missing replies don’t always mean a link has failed.
Likewise, a successful ping doesn’t verify the application’s port, sign-in or data transfer. Keep the destination and results together so IT can interpret them in context.
Record configuration without improvising a fix
IT may ask for the assigned address, gateway, DNS servers or VPN status. On Windows, select Search on the taskbar, type command prompt and open it. Type ipconfig and press Enter. Find the section for your Wi-Fi or Ethernet adapter and look at the IPv4 Address line.
If that address starts with 169.254, Microsoft’s guide explains that Windows couldn’t get an address from the router. It’s a useful clue for IT, so copy the whole output into your support request.
Send these details through your usual support channel. Don’t replace DNS settings with a public resolver or assign a guessed address to see whether it works.
These settings may be part of security filtering or required routing. A workaround can hide the original problem or bypass a business control.
Look for a repeatable performance pattern
Record where and when slowdowns occur, what applications are affected and whether a cable performs differently from Wi-Fi. Note large transfers or scheduled work without assuming they’re the cause.
Speed tests are samples of a particular route and time. Share the result and conditions with IT. One number won’t tell you what’s wrong.
Check for a provider outage
If everyone has lost the internet, check your internet provider’s service status page or outage line from a phone on mobile data. If the provider reports an outage in your area, note the time and any reference number and pass them to IT. It saves everyone testing equipment that’s working.
Restarting the modem and router is sometimes the next step, but only for the person who looks after that equipment and only once IT has agreed. Warn colleagues first, since phones or access controls may run through the same equipment. Microsoft’s order is: unplug the router, then the modem. Wait at least 30 seconds. Plug the modem back in and wait for its lights to stop blinking, then plug in the router and give both a few minutes to start.
Make the handoff actionable
Send the observations, recent changes and checks already tried. Explain the business effect and any time-sensitive work that needs an alternative.
Have IT coordinate changes to shared equipment, firmware or security policies, with rollback and a verification task. After the fix, repeat the original failing workflow and confirm with affected users. Record what changed so an intermittent problem can be followed up.


