Error Code 104125 appears when Zoom Workplace cannot complete a network connection to Zoom services. The most reliable fix is to identify what blocks the connection path—then remove that single blocker.
If you want a fast win, follow the sections in order. Each step is designed to confirm a specific cause of connection failure without guessing, while keeping changes minimal and reversible.
Table of Contents
What Error Code 104125 Means
Zoom groups 104125 with several “cannot reach Zoom servers” connectivity codes. When this happens, the app is working, your account is fine, and the missing piece is the network route between your device and Zoom’s services. [✅Source-1]
Common Signs include “connecting” loops, “can’t connect to our service,” sign-in that never completes, or joining a meeting that fails before audio/video loads. These patterns point to blocked connectivity, not a camera or microphone issue.
Fastest Checks to Confirm the Cause
- Open a browser and visit zoom.us. If the page fails to load, the issue is broader than the Zoom app. If it loads, keep going.
- Switch networks for one test: try a mobile hotspot or another Wi-Fi. If Zoom works there, your original network is filtering or blocking traffic.
- Turn off VPN and any proxy app for a moment. If the error disappears, the VPN/proxy path needs allow-listing or a different exit location.
- Restart your router/modem and your device. This sounds simple, yet it resets stale routes and DNS caches without changing permanent settings.
- Verify date/time is correct. A clock that is far off can cause certificate checks to fail, which looks like a connectivity problem.
If Zoom works on hotspot but fails on your main network, focus on firewall, proxy, SSL inspection, DNS, or guest Wi-Fi restrictions. That is where 104125 most often lives.
Network Path Fixes: Firewall, Proxy, and DNS
This section targets network blocks. Apply the smallest change that matches your environment, then re-test Zoom before moving on. A short loop of “change → test” beats changing five things at once.
Allow Required Ports and Domains
On filtered networks, Zoom may need specific outbound ports. Many environments already allow TCP 443 but block the additional media ports, leading to connectivity failures before a meeting fully initializes. [✅Source-2]
| What To Allow (Outbound) | Where It Usually Breaks | Practical Fix |
|---|---|---|
| TCP 443 plus Zoom meeting media TCP ports (commonly 8801–8802) | Corporate firewalls that allow web browsing but restrict real-time media | Ask IT to allow Zoom meeting traffic on the documented ports for Meetings/Webinars |
| UDP 3478–3479 and common Zoom media UDP range (often 8801–8810) | Networks that block UDP entirely or apply strict QoS rules | Allow UDP for Zoom or test with UDP opened for your device/VLAN |
| zoom.us and related subdomains | Proxy or “web security” tools that do TLS/SSL inspection | Allow-list Zoom domains and exclude them from SSL inspection if your policy permits |
Proxy and SSL Inspection
Zoom can auto-detect proxy settings, yet some networks require authentication or rewrite certificates. When that chain breaks, 104125 can appear even though other apps work. If you use a proxy, ensure credentials are valid and the proxy is not silently blocking real-time connections.
Important: If you are on a managed network, avoid making permanent firewall changes on your own. Share the exact port and domain requirements with your administrator so the network policy stays consistent.
DNS and Captive Portal Checks
- If you are on hotel, airport, or guest Wi-Fi, open a browser and complete any captive portal login first. Zoom may fail until the network grants full access.
- Try switching DNS to a trusted provider (device or router level) if your current DNS is slow or filtered. After changing, reboot the device to refresh name resolution.
- If Zoom works in a browser but not in the app, focus on proxy rules and security gateway policies rather than DNS.
Zoom App Fixes: Update and Reinstall
Once the network path is reasonable, fix the local app layer. A clean app state often resolves 104125 when the root cause is a stale component, cached proxy configuration, or an older build behaving differently on your network.
Update Zoom Workplace
- Open Zoom Workplace and sign in.
- Select your profile picture.
- Choose Check for Updates.
- If an update is available, install it, then restart the app before testing again.
Zoom documents this update path and also notes that some MSI-managed installs remove the update button, in which case your IT team handles updates. [✅Source-3]
Reinstall for a Clean State
If updating does not help, a fresh reinstall clears local app components and resets many settings that can interfere with connectivity. Start with the standard uninstall method, then install again from the official Download Center.
Tip: If your issue began right after a network change (new router, new firewall policy, new VPN), reinstalling is still worth doing, because it removes cached proxy and routing assumptions that can keep failing after the environment changes.
Zoom provides platform-specific uninstall and reinstall steps (Windows, macOS, Linux, mobile), including a deeper removal tool for cases that require a full cleanup. [✅Source-4]
Admin-Level Network Fixes When You Have Access
These steps are helpful when you manage your device or network. They reduce hidden problems that show up as Zoom connectivity errors, especially after switching Wi-Fi, VPN profiles, or DNS.
Windows Commands
- Flush DNS:
ipconfig /flushdns - Renew IP:
ipconfig /releasethenipconfig /renew - Reset Winsock (then reboot):
netsh winsock reset
After the reboot, test Zoom sign-in first, then try joining a meeting. If it works, you confirmed a local stack or DNS issue.
macOS and Linux Commands
- macOS DNS cache (common approach):
sudo dscacheutil -flushcachethen restart Wi-Fi - systemd-resolved systems:
sudo resolvectl flush-caches - Network restart: disable/enable the adapter, then test zoom.us in a browser
On macOS and Linux, the fastest signal is whether the browser can reliably reach Zoom web endpoints after the reset.
If You Are on a Managed Network: if disabling a security agent or changing proxy settings is restricted, do not force it. Instead, collect evidence (next section) and ask your administrator to adjust policy for Zoom domains and ports.
Use the Zoom Network Connectivity Tool
Zoom includes a built-in Network Connectivity Tool that tests the route to Zoom services and highlights proxy detection, traceroute results, and basic service reachability. It is one of the fastest ways to stop guessing.
How to Open It: On Windows, press Ctrl + Alt + Shift + D. On macOS, press Cmd + Option + Shift + D. Then run the Smart Test and review results for Network Information, MTR, and Service Status.
- Open the tool and run Network Test.
- Check whether a proxy is detected. If a proxy appears unexpectedly, your network may be forcing one.
- Review MTR/traceroute for timeouts near the final hops. Repeated failures there often indicate firewall filtering.
- If the tool offers exporting logs, export them for IT or support when needed.
Zoom documents the tool’s shortcuts, tests, and what it reports (including service connectivity and traceroute). [✅Source-5]
Check Zoom Service Status
Sometimes your network is fine and Zoom is in a maintenance window or incident. If multiple networks fail at the same time, check Zoom’s service status page before changing local settings. [✅Source-6]
Simple Rule: if Zoom fails on your Wi-Fi, your hotspot, and a second device, pause local troubleshooting and verify service status. It prevents unnecessary changes and saves time.
What to Share With IT or Support
- Exact error text and the 104125 code
- Your location context (home, office, guest Wi-Fi) and whether a VPN is used
- Whether it works on a hotspot or another network
- Zoom app version and operating system version
- Time of occurrence and whether others are affected on the same network
- Results from the Network Connectivity Tool (exported logs if available)
FAQ
Does Error Code 104125 mean my Zoom account is blocked?
No. 104125 is a connectivity code. In practice, it points to a route problem between your device and Zoom services, such as firewall filtering, proxy rules, VPN exit behavior, or a captive portal. An account issue typically presents different prompts, like sign-in warnings or account-specific notices.
Why does Zoom work in a browser but not in the desktop app?
This pattern often indicates app-specific network handling is being filtered. Browsers may be allowed while non-browser traffic is inspected or routed differently. Focus on proxy/SSL inspection rules, allow-listing Zoom domains, and ensuring required outbound ports are permitted for real-time media.
What is the quickest way to confirm it is my network?
Use a mobile hotspot test. If Zoom works on hotspot and fails on your primary network, you confirmed the issue is network policy or routing. If it fails everywhere, check service status and then use the Network Connectivity Tool to collect evidence.
Do I need to open ports on my home router?
Usually not. Most home routers allow the needed outbound traffic by default. If you run a custom firewall, strict DNS filtering, or a privacy/VPN gateway, that can change things. In that case, allow-list Zoom domains and ensure outbound ports for meetings are not blocked, then retest.
Can security software cause 104125?
It can. Some endpoint security suites intercept network traffic and apply filtering that breaks secure connections. A short test with the security web filter paused (if your policy allows) can confirm this. If confirmed, add a safe allow rule for Zoom rather than leaving protection disabled.