Zoom stuck on “Connecting…” with a meeting already in progress is genuinely stressful. The good news is that this specific scenario — connecting to a meeting that others can already join — almost always means the problem is local, because Zoom’s servers are obviously working. Check three things immediately: the Zoom status page at status.zoom.us (takes 10 seconds), your internet connection (open a website in the browser), and whether Zoom has hung background processes (Task Manager → end all Zoom processes → reopen). If any of those three identifies the problem, you’re done within 60 seconds. For the bigger picture, our Complete Guide to Fixing Windows, Browser, and Software Errors pulls everything together.
If all three check out and Zoom still won’t connect, work through the fixes below. They’re ordered by how commonly each cause appears.
Fix 1: Force Quit and Full Restart
Clicking X on the Zoom window leaves Zoom running in the system tray. When a previous Zoom session ended in an error or crash, those background processes stay in a failed state and block new connections from establishing — Zoom thinks it’s already trying to connect through a broken session.
The proper close: Task Manager (Ctrl + Shift + Esc) → find every Zoom-related process (Zoom, CptHost, ZoomMTGMgr) → End task on each. Also check the system tray for a Zoom icon → right-click → Quit. Wait 15 seconds, then reopen Zoom and try joining again.
While Zoom is completely closed, do a quick router restart if you have 90 seconds to spare. It clears NAT session tables that sometimes hold stale connection tracking entries — particularly relevant if the last Zoom session ended abnormally.
Fix 2: The Firewall and Antivirus Check
After a Windows Update that resets firewall rules, or after installing new security software, Zoom’s network traffic gets blocked. The symptom — hanging at “Connecting…” — is identical to a server problem, which makes this easy to overlook.
Quick test: temporarily disable Windows Defender Firewall (Settings → Privacy and Security → Windows Security → Firewall and network protection → click your active network type → toggle Microsoft Defender Firewall to Off). Try Zoom immediately. If it connects, the firewall was blocking it. Re-enable the firewall right after the test.
Permanent fix: search “Allow an app through Windows Firewall” in Start → Change settings → find Zoom Video Communications → tick both Private and Public. If Zoom isn’t listed: Allow another app → browse to C:Users[YourName]AppDataRoamingZoombinZoom.exe → Add.
For third-party antivirus: look for a “trusted applications” or “application exceptions” section and add Zoom. Some antivirus products also have a separate “firewall” component from the antivirus scanning — check both.
Fix 3: Switch to TCP Mode
Zoom uses UDP by default for audio and video — it’s faster and lower latency, but many corporate networks, school networks, hotel Wi-Fi, and some ISPs actively block UDP-based conferencing traffic. Switching Zoom to TCP causes it to use port 443 (standard HTTPS traffic) instead, which almost no network blocks.
Zoom app → click profile picture → Settings → look for “Use TCP connection for meetings” or a Network tab → enable it. Try connecting to the meeting again. If this fixes it, the network you’re on blocks Zoom’s UDP traffic. TCP is the permanent solution for that network.
This is especially worth trying if Zoom works fine at home but consistently fails to connect at work, school, or hotels.
Fix 4: VPN Is Probably the Culprit
VPNs and Zoom have a complicated relationship. A VPN routes Zoom’s traffic through a VPN server that may be geographically distant from both you and the Zoom data center, adding latency and often triggering Zoom’s connection timeout before the handshake completes. Some VPN configurations also block UDP entirely, causing the same problem as a corporate firewall.
Try disconnecting the VPN and connecting to Zoom without it. If Zoom connects immediately without the VPN, the VPN is the cause. Options:
- Use a VPN server in the same country to reduce routing distance
- Enable split tunneling in the VPN settings and add Zoom to the exclusion list (traffic goes directly to the internet, bypassing the VPN)
- Switch TCP mode on in Zoom — this often resolves VPN-related connection failures even when leaving the VPN connected
Fix 5: Update or Clean Reinstall Zoom
An outdated Zoom client fails to connect when meetings use security or protocol requirements that the older client doesn’t support. Zoom updates frequently and the client enforces minimum version requirements.
In Zoom: profile picture → Check for Updates. If Zoom can’t reach the update server (because it’s not connecting), download the latest installer from zoom.us/download directly and run it — it updates the existing installation.
For a clean reinstall when updating doesn’t resolve the issue: uninstall Zoom via Settings → Apps, then manually delete C:Users[YourName]AppDataRoamingZoom to remove all cached data, then reinstall from zoom.us/download. This eliminates corrupted configuration files that survive standard uninstallation.
Fix 6: Join from the Browser Right Now
If the meeting is happening and you need to be in it immediately: click the Zoom meeting link from your email or calendar. On the page that opens in your browser, find “Join from your browser” (usually a small text link below the “Open Zoom” button). Grant microphone and camera permissions. You’re in within 30 seconds, with full audio, video, and screen sharing — while you troubleshoot the desktop app afterward.
The browser client (Chrome or Edge) has slightly reduced features compared to the desktop app (some advanced host controls and virtual backgrounds require the app) but is fully functional for standard meeting participation.
Zoom Port Requirements for IT Conversations
If Zoom not connecting happens specifically on a corporate network and you need to talk to IT about it, the specific ports Zoom needs are:
- TCP 443 — Fallback for signalling and connections
- TCP 8801–8802 — Zoom’s primary TCP media ports
- UDP 8801–8802 — Zoom’s primary UDP media ports (often the ones blocked)
- UDP 3478 and 3479 — STUN/TURN for NAT traversal
Zoom publishes its full IP range list on the Zoom support site. IT teams can create firewall rules that allow Zoom traffic specifically without opening broad UDP port ranges to the internet — this is the right long-term corporate fix rather than running Zoom in TCP mode indefinitely.
DNS and Hosts File Checks
Some content filtering systems block Zoom’s domains by modifying the Windows hosts file or configuring DNS to return failures for Zoom lookups. On managed corporate machines or machines with parental control software, this causes Zoom to fail to connect in a way that looks identical to a network issue.
Quick DNS check: open Command Prompt and type nslookup zoom.us. If this returns an error, NXDOMAIN, or an unexpected IP address, DNS filtering is blocking Zoom’s domain. On a work machine, this requires IT to whitelist Zoom’s domains. On a personal machine, check whether parental control software or a DNS filter (like OpenDNS with a content policy) is blocking conferencing platforms.
Our guide on Zoom audio not working covers the microphone and speaker issues that become apparent once the connection is established — a separate problem from the connection failure itself. For the network stability issues that cause Zoom to connect but then drop, our Wi-Fi disconnecting guide covers the underlying adapter and router causes. Zoom’s official support documentation includes a network connectivity test tool that checks whether your specific network can reach all Zoom servers on the required ports — worth running before calling IT if you’re not sure which ports are blocked.
Zoom on Work-Issued vs Personal Devices
The behaviour of Zoom differs meaningfully depending on whether the machine is organisation-managed. On a corporate laptop, Zoom may be deployed with admin-configured settings that override user preferences — including connection protocols, server regions, and which features are available. If you’ve been told to use a specific Zoom configuration by IT and the problem started after a policy change, the fix is almost certainly on the IT side rather than the device side.
Check whether Zoom is managed: Zoom Settings → General → look for any greyed-out options or “Set by administrator” labels. If you see these, certain settings (including the TCP mode toggle) may not be user-configurable. Reporting the connection failure to IT with the specific error details — including output from the Zoom connection test — gives them what they need to investigate on their end.
Zoom Connection Test Tool
Zoom has a built-in network test that’s worth running when you’re not sure which layer of the network is causing the problem. Before joining a meeting, click “Test Zoom” when signing in, or navigate to zoom.us/test in a browser. This test checks whether Zoom’s servers are reachable, which protocols are working, and the quality of the connection including latency and packet loss. The test generates a report that shows specifically which Zoom data centers are reachable and which are blocked, which is directly actionable for both personal troubleshooting and IT conversations.
The test also surfaces audio and video device issues — confirming the camera and microphone are working before joining a meeting prevents the scenario of getting connected but then discovering audio problems mid-meeting.
Proxy Configuration Interfering with Zoom
If a work proxy or personal proxy is configured in Windows, Zoom may route its traffic through the proxy — and if the proxy isn’t configured to allow Zoom’s specific ports and protocols, or if the proxy credentials are stale, Zoom fails to connect. Zoom attempts to use the system proxy settings automatically.
Check proxy settings: Settings → Network and internet → Proxy. If “Use a proxy server” is on with an address configured, try temporarily disabling it and testing Zoom. If Zoom connects without the proxy, either configure the proxy to pass Zoom traffic, or add Zoom to the proxy bypass list. In the “Don’t use the proxy server” field, you can add *.zoom.us to route Zoom traffic directly without the proxy while other traffic continues using it.
IPv6 and NAT Issues
Some network configurations have issues with IPv6 that affect Zoom’s connection negotiation. Zoom supports both IPv4 and IPv6, but certain router configurations route IPv6 traffic incorrectly or have broken IPv6 connectivity that causes Zoom to attempt IPv6 connections that time out before falling back to IPv4. The result is a delayed or failed connection.
Test: in Windows adapter properties for your network connection, uncheck “Internet Protocol Version 6 (TCP/IPv6)” temporarily. Try Zoom again. If it connects faster or more reliably, IPv6 routing on the network is the issue. You can either leave IPv6 disabled on that adapter (it rarely affects everyday browsing since most sites accept both), or check the router’s IPv6 configuration for misconfiguration — common on routers where IPv6 was partially set up and abandoned.
When Zoom Connects but Immediately Drops
This is a different problem from not connecting at all, but worth covering since the symptoms look similar initially. If Zoom connects, you see the meeting room briefly, and then it drops you with “Poor connection” or a network error — the connection established but something is causing it to fail:
- Run a sustained ping test (
ping 8.8.8.8 -tin Command Prompt for 60+ seconds) and watch for packet loss - Check whether other high-bandwidth activities (downloads, video streaming, cloud backups) are happening simultaneously and consuming bandwidth
- Switch from Wi-Fi to a wired Ethernet connection if possible — Zoom is sensitive to wireless packet loss in a way that ordinary web browsing isn’t
- Lower Zoom’s video quality: Zoom Settings → Video → turn off HD video and enable “Original ratio” — this reduces bandwidth requirements significantly and often stabilises connections that are borderline
The distinction matters because “connects then drops” is a bandwidth or stability problem, while “never connects” is a firewall, proxy, or server reachability problem. They require different approaches even though they both appear as “Zoom not working.”
One more scenario worth addressing: Zoom that worked yesterday and stopped today with no obvious change. This usually means one of three things happened overnight — Windows Update ran and changed firewall rules or replaced the Zoom audio driver, Zoom itself auto-updated and introduced a bug in the new version (check zoom.us/download for a known issues page on the current release), or your network configuration changed (router firmware update from the ISP is a common silent change that occasionally breaks specific port configurations). Checking the Windows Update history and Zoom’s version history narrows down which of these three changed, which tells you whether the fix is Windows-side (roll back the update), Zoom-side (reinstall the previous version), or network-side (contact the ISP or check router settings).
For users who rely heavily on Zoom for work, having the browser fallback set up in advance is worth the two minutes. Bookmark zoom.us/join in Chrome or Edge, test it once successfully, and you’ll know exactly what to do the next time the desktop app refuses to cooperate. The browser client isn’t a perfect substitute but it handles 95% of everyday meeting needs without any of the desktop app’s dependencies on local drivers, firewalls, and installation state. You might also run into Google Drive Not Syncing.
