Build a reliable work-from-home connection
Improve calls and remote access, separate work and home faults, and prepare a realistic fallback before an important meeting.
Start with the free diagnostic steps. Affiliate links appear only where a product category could address the problem identified in this guide.
Key takeaways
- Test the actual workspace and use Ethernet for the primary work device where practical.
- Check upload, latency and stability—not only download speed.
- Agree fallback and security rules with the employer before an outage.
Define what reliable means for the job
A video call needs consistent upload, download and latency. A remote desktop is sensitive to delay and loss. Large media work may need sustained transfer capacity, while ordinary email may tolerate a brief slowdown. List the critical applications, expected call quality and employer requirements before deciding that the connection needs an upgrade.
Run tests from the desk during the hours when problems occur. Record whether the device uses Wi-Fi, Ethernet, a corporate VPN or a cloud security agent. A healthy general speed test does not prove that a particular employer service or VPN route is healthy, so compare with colleagues and the service’s official status where appropriate.
Stabilise the primary workspace
Ethernet is the best control and often the best permanent link for a fixed work computer. If Wi-Fi is necessary, put the access point where the workspace receives a strong path rather than hiding the router near the floor. Test beside the router and at the desk on the same device to establish whether coverage is the main difference.
Use a headset and local microphone settings to separate audio-device trouble from the network. Close unnecessary video streams and pause personal cloud backups during critical calls. Do not disable employer security software to improve a test; ask the helpdesk to interpret the result with the required controls present.
Protect work data and accounts
Use the employer-approved device, VPN and collaboration tools. Keep the operating system, browser and applications updated, lock the screen away from the desk and use multi-factor authentication. Do not bypass managed settings, install unknown “network optimiser” software or forward router ports to a work computer.
A home network is not automatically trusted. Sensitive services should use authenticated encrypted connections, and company policy may require a VPN even at home. Put unknown or unmaintained smart devices on a guest or separated network if the router supports it and the employer recommends that arrangement.
Plan a fallback before it is needed
A phone hotspot can bridge a short fixed-line outage, but only if indoor mobile coverage, data allowance, device policy and tethering support are adequate. Test it briefly before an important event without consuming excessive data. Keep a charger available and know how to join the meeting by phone audio if video is impossible.
A fallback must not bypass organisational security. Some employers prohibit work on personal devices or unapproved networks. Ask what to do before an outage and keep the helpdesk number, meeting dial-in details and essential documents available through approved offline methods.
Diagnose calls that freeze or sound poor
Check whether the problem affects every participant or only you. Compare another call service, run a latency test and note simultaneous uploads. If the problem disappears on Ethernet, focus on Wi-Fi. If it occurs only with the corporate VPN, provide the helpdesk with time, VPN region and error details rather than changing the tunnel configuration yourself.
One-way audio may be an application, permission, headset or firewall issue instead of bandwidth. Test the microphone locally and use the platform’s official diagnostics. For recurring problems, a short timeline that separates call, VPN, device and general-internet behaviour is more useful than one speed screenshot.
Escalate to the right organisation
Contact the employer helpdesk for managed-device, account, VPN and application faults. Contact the broadband provider when evidence shows a persistent connection problem across personal and work services, especially over Ethernet. Use the application provider’s status and support when only that service is affected.
Keep timestamps, error messages and the comparison conditions, but remove confidential names or document details before sharing with a broadband provider. Clear ownership prevents each party from seeing only a vague report and sending the user in a circle.
Recommended next checks
Compare results beside the router, in the problem location and over Ethernet where possible. Repeat under the same conditions rather than relying on one run. LumaProbe’s browser measurements describe the complete path to its server, so use them to narrow the fault—not as a substitute for a provider line diagnostic.
Relevant equipment categories
Only consider equipment after the checks above identify a matching coverage, cabling, port or adapter problem. These are category searches, not paid rankings or claims that every product shown is suitable.
As an Amazon Associate, LumaProbe earns from qualifying purchases. Read the full affiliate disclosure.
Sources and further reading
- NCSC: advice for end users
- NCSC: do not trust any network, including your own
- LumaProbe test methodology
External guidance can change. Sources and links were checked on 19 July 2026.
More help
Browse all internet and Wi-Fi guides, read how LumaProbe tests connections, or report a correction through LumaContact.