Zoom: Error Code 104102 Fix – Causes & Solutions

Zoom Error Code 104102 usually appears when the Zoom app cannot create a stable connection between your device and Zoom’s servers. In plain terms, Zoom is installed, the meeting link may be correct, and your internet may look normal in a browser, yet the Zoom connection path is being blocked, interrupted, inspected, delayed, or misrouted.

Quick Fix Steps

1. Close Zoom completely, then open it again and rejoin the meeting.
2. Switch from Wi-Fi to Ethernet, or test a mobile hotspot for one meeting attempt.
3. Turn off VPN or private relay tools for a short test.
4. Check whether security software is filtering Zoom traffic; do not leave protection off permanently.
5. Flush DNS on Windows with ipconfig /flushdns, then restart Zoom.
6. Update Zoom from the desktop app menu or install the current version from the official Download Center.
7. On school, office, hotel, hospital, or public Wi-Fi, ask the network admin to allow Zoom’s required domains, ports, and return traffic.

Jump to a Repair Section

What Zoom Error Code 104102 Means

Error 104102 does not usually mean that the meeting ID is wrong. It points to the network route between Zoom and your device. The Zoom desktop app must reach Zoom services, complete secure traffic checks, and keep media traffic flowing during the meeting.

That route can break at several places: local Wi-Fi, router DNS, corporate proxy, SSL inspection, endpoint security software, VPN tunnel, blocked UDP ports, or a temporary ISP path issue. On managed devices, even a small policy change can affect Zoom while other websites still open normally.

The error is closely related to the wider Zoom connection-error family. Zoom’s official error-code table groups 104101, 104102, 104103, 104104, 104105, 104106, 104110, 104111, 104112, 104113, 104114, 104115, 104116, 104117, and 104118 with connectivity problems involving Zoom servers. That pattern matters because the same fixes often repair more than one code in this range.

The Main Symptom Pattern

• Zoom stays on Connecting and then fails.
• The meeting starts loading, then drops before audio or video joins.
• Browser pages work, but Zoom meetings do not connect.
• The same meeting works on mobile data but not on the current Wi-Fi.
• The error appears more often on office, school, public, or filtered networks.

Why Zoom Error Code 104102 Happens

The cause is usually one layer deeper than “bad internet.” A speed test may look fine because it checks ordinary web traffic, while Zoom also needs meeting media traffic, secure signaling, domain access, certificate validation, and return connections.

Common causes of Zoom Error Code 104102 and the repair path that usually fits each one.

Cause Area	What Usually Happens	Most Useful Check
Firewall or proxy	Zoom cannot reach required domains, IP ranges, or ports.	Test hotspot; ask admin to allow Zoom traffic.
Antivirus or endpoint security	Security software inspects, delays, or blocks Zoom connections.	Pause only for a short test, then add a safe exception if needed.
VPN	Zoom traffic routes through a slow or restricted tunnel.	Disconnect VPN and retry the same meeting.
DNS cache	The device keeps an old or failed name-resolution result.	Flush DNS and restart the Zoom app.
Router or Wi-Fi isolation	The network blocks device-to-service or local communication patterns.	Restart router, use Ethernet, or test another network.
Old Zoom app files	Client files, cached settings, or update state become inconsistent.	Update first; reinstall only when needed.
Zoom service status	The issue affects a wider service area, not only one device.	Check the official Zoom Service Status page.

Best Repair Order for Error Code 104102

Use a fixed order. Random changes make this error harder to diagnose. Start with the lowest-risk checks, then move toward admin-level firewall rules and app reinstall steps.

1. Confirm Whether the Issue Is Network-Specific

1. Disconnect from the current Wi-Fi.
2. Connect to a mobile hotspot or a different trusted network.
3. Open Zoom and join a test meeting or the same meeting link.
4. If it connects, return to the original network and continue with firewall, proxy, router, or DNS checks.

This one test separates device-side problems from network-side problems. Very useful, this step. Many people skip it and reinstall Zoom too early.

2. Restart the Right Things in the Right Order

1. Quit Zoom completely, including the tray icon on Windows or the menu-bar process on macOS.
2. Restart the router if you are on a home network.
3. Restart the computer.
4. Open Zoom again before opening many browser tabs or meeting tools.

A router restart clears temporary NAT table problems. A computer restart reloads local network services. It is basic, yes, but for connection-state errors it still works often enough to do early.

3. Check the Official Zoom Service Status

If Error Code 104102 appears on more than one device and more than one network, check Zoom Service Status before changing system settings. Zoom’s support page points users to the official status site for current service status and maintenance periods. [✅Source-2]

If the status page shows an active issue for meetings, webinars, login, or regional services, local troubleshooting may not repair the problem until service health returns. In that case, the best practical move is to try another connection method, wait for the incident update, or use the meeting host’s backup joining option.

Fix Firewall and Proxy Problems

Firewall and proxy filtering is the most common serious cause of Zoom Error Code 104102 on managed networks. This includes office firewalls, school filters, hotel networks, public Wi-Fi portals, DNS filters, SSL inspection tools, endpoint protection suites, and router-level security settings.

What to Allow for Zoom Meetings

Zoom documents outbound firewall rules for Zoom traffic. For Zoom Meetings and Webinars, the official table includes TCP 443, 8801, 8802 and UDP 3478, 3479, 8801-8810 for all Zoom clients, along with Zoom IP ranges and domain rules. Zoom also notes that proxy support uses HTTPS/SSL proxy servers through port 443 and recommends allowing zoom.us and *.zoom.us from proxy or SSL inspection. [✅Source-3]

For Home Users

• Disable VPN for one test meeting.
• Restart the router and test Zoom again.
• Turn off router “advanced security,” “web shield,” or “safe browsing” filters only long enough to test.
• Try Ethernet instead of Wi-Fi if the device supports it.
• Check whether parental-control or DNS-filtering apps are blocking Zoom domains.

For Office or School Networks

Do not keep changing your personal device if the issue only happens on a controlled network. Send the admin a short, precise note:

Zoom meetings fail with Error Code 104102 on this network. Please check outbound firewall and proxy rules for Zoom Meetings, including Zoom domains, SSL inspection bypass for Zoom where required, TCP 443/8801/8802, UDP 3478/3479/8801-8810, and return traffic.

Simple wording saves time. It points the network team to the actual connection path, not to camera, microphone, or meeting-password settings.

Do Not Leave Security Software Off

Temporarily pausing antivirus can help confirm whether security filtering is involved. Keep it short. If Zoom works only when protection is paused, turn protection back on and create an allowed-app rule for Zoom Workplace or ask the security vendor/admin for the correct exception.

Fix DNS and Windows Network Stack Issues

DNS problems can make Zoom fail even when other sites open. The device may keep a stale answer for a Zoom-related domain, or a previous failed lookup may remain in cache. On Windows, Microsoft documents ipconfig /flushdns as the command that flushes and resets the DNS client resolver cache. [✅Source-4]

Windows DNS Reset Steps

1. Right-click Start.
2. Open Terminal (Admin) or Command Prompt (Admin).
3. Run: ipconfig /flushdns
4. Close Zoom fully.
5. Open Zoom again and retry the meeting.

If the problem started after VPN software, proxy software, network drivers, or security tools changed the connection layer, reset Winsock only after simpler DNS steps fail. Microsoft describes netsh winsock reset as a command that resets the Winsock catalog to a clean state to help resolve network problems caused by corrupted Winsock settings. [✅Source-5]

Windows Winsock Reset Steps

1. Open Command Prompt as Administrator.
2. Run: netsh winsock reset
3. Restart the computer.
4. Reconnect to the network.
5. Open Zoom and test again.

macOS Network Checks

• Turn Wi-Fi off and on again.
• Test a different network or hotspot.
• Disable VPN or private relay tools for a short test.
• Check System Settings > Network for proxy settings you did not intend to use.
• Restart the Mac after changing VPN, proxy, or DNS settings.

On macOS, Error 104102 often becomes clear after one comparison: the same Mac fails on the filtered Wi-Fi but joins normally on a hotspot. That points away from Zoom account settings and toward network filtering.

Check Bandwidth Without Chasing the Wrong Problem

Error Code 104102 is mainly a connection-establishment problem, not a video-quality warning. Still, weak bandwidth, packet loss, or unstable Wi-Fi can make the connection fail during join. Zoom’s system requirements list recommended bandwidth values such as 600 kbps up/down for high-quality 1:1 video, 1.2 Mbps up/down for 720p 1:1 HD video, and 3.8 Mbps/3.0 Mbps up/down for 1080p 1:1 HD video. Group 720p video is listed at 2.6 Mbps/1.8 Mbps up/down. [✅Source-6]

Those numbers help you judge whether the connection is suitable after Zoom connects. They do not replace firewall checks. A network can have 300 Mbps download speed and still block Zoom meeting traffic. Happens often on filtered networks.

Connection Quality Signs to Check

• High latency: pages open, but live meeting traffic feels delayed.
• Packet loss: audio cuts out, then the meeting disconnects.
• Wi-Fi roaming: laptops switch between access points and Zoom drops.
• Captive portal: hotel or campus Wi-Fi needs browser login before Zoom can connect.
• UDP blocking: Zoom may connect poorly or fail when real-time media ports are restricted.

Update or Reinstall Zoom Only After Network Checks

Updating Zoom is worth doing early. Reinstalling is useful later, after you test the network. Zoom says the app provides update notifications and lets users check updates from the desktop app by clicking the profile picture and choosing Check for Updates. Zoom also notes that MSI-installed desktop apps may have AutoUpdate disabled and may require IT help. [✅Source-7]

Update Zoom on Windows or macOS

1. Open the Zoom desktop app.
2. Sign in if needed.
3. Select your profile picture.
4. Choose Check for Updates.
5. Install the available update.
6. Restart Zoom and test the meeting again.

When Reinstalling Makes Sense

Reinstall Zoom if the app crashes before connecting, update fails, the issue appears only on one computer, or Zoom still fails after the same network works on another device. Zoom’s uninstall and reinstall instructions cover Windows, macOS, Linux, Android, iOS, and Zoom Rooms; the Windows path includes removing Zoom from Control Panel, while macOS includes uninstalling through the Zoom Workplace toolbar. [✅Source-8]

Network Admin Notes for Error Code 104102

For managed networks, the user-side fix may not be enough. The admin should inspect outbound TCP and UDP rules, DNS filtering, SSL inspection, web proxy authentication, endpoint protection logs, and return traffic behavior. The goal is not to open everything. The goal is to allow the documented Zoom traffic path.

Admin Checklist for the 104102 Error

• Allow Zoom domains used by Zoom Workplace, meetings, web access, and status pages.
• Review whether SSL inspection is breaking Zoom traffic.
• Check proxy authentication prompts that users may not see inside the app.
• Confirm outbound traffic and return traffic are both allowed.
• Check whether UDP media traffic is blocked or forced through a poor path.
• Compare one failing device with one working device on the same VLAN.
• Review endpoint security logs for Zoom process blocks.

For more Zoom troubleshooting pages and related error-code help, visit the Zoom error code repair section and compare the symptom pattern with nearby connection errors.

Mistakes That Keep Error 104102 Coming Back

Only Reinstalling Zoom

Reinstalling can repair app files, but it will not fix a blocked firewall path. If Zoom fails on one Wi-Fi network and works on a hotspot, the network path deserves attention first.

Leaving VPN On During Testing

A VPN can change DNS, routing, proxy handling, and packet flow. Test Zoom once with VPN off. If it works, use split tunneling or ask the VPN admin to allow Zoom traffic directly.

Assuming Browser Access Means Zoom Access

A browser opening websites proves only basic web access. Zoom meetings also rely on real-time media traffic, app connections, certificate validation, and meeting-service routing.

Ignoring Captive Portals

Public Wi-Fi may say “connected” before the login page is completed. Open a browser and visit a normal website first. Accept the Wi-Fi portal terms if prompted, then open Zoom.

Advanced Checks When Nothing Else Works

If the common fixes do not clear Zoom Error Code 104102, look for deeper mismatches between the device, the network, and Zoom’s secure connection process.

Check Date and Time

Wrong system time can break secure connections because certificates depend on valid date and time checks. Enable automatic date, time, and time zone settings, then restart Zoom.

Try the Browser Version

If the desktop app fails, try joining from a supported browser. If the browser works but the app fails, focus on the Zoom app, endpoint security, local firewall rules, or cached app settings. If both fail, focus on network access.

Create a New Local User Test

On Windows or macOS, a damaged user profile can affect app settings, proxy entries, certificates, or local permissions. Create a temporary local user profile and test Zoom there. If it works, the original profile may have a local configuration problem.

Check Multiple Meetings

Try a Zoom test meeting and a different meeting link. If only one meeting fails, the host’s settings, waiting room, authentication requirement, or account restrictions may be involved. If every meeting fails, the connection layer is the stronger suspect.

When to Contact an Admin, ISP, or Zoom Support

• Contact your network admin if the error appears only on office, school, hotel, or filtered Wi-Fi.
• Contact your ISP if multiple devices fail on your home connection but work on mobile data.
• Contact Zoom Support if the issue follows your account across several networks and devices.
• Contact device support if Wi-Fi, DNS, or Winsock problems affect other live apps too.

Prepare useful details before asking for help: device model, operating system, Zoom version, network type, VPN status, antivirus name, whether a hotspot works, and the exact error code. Clean notes shorten the repair path.

Common Questions About Zoom Error Code 104102

What does Zoom Error Code 104102 mean?

It means Zoom cannot complete the connection between your device and Zoom’s servers. The cause is usually firewall filtering, proxy settings, antivirus interference, VPN routing, DNS cache, ISP routing, or a temporary service issue.

Is Error Code 104102 caused by a wrong meeting link?

Usually no. A wrong or expired meeting link tends to create a different access problem. Error 104102 points more toward the connection path between the Zoom app and Zoom services.

Why does Zoom fail when my internet works?

Web browsing and Zoom meetings do not use the exact same traffic pattern. A network can allow websites while blocking or inspecting Zoom app traffic, UDP media ports, proxy authentication, or certificate validation paths.

Should I disable my antivirus to fix Zoom Error 104102?

Only for a short test. If Zoom works while protection is paused, turn protection back on and add a proper Zoom exception or ask your network/security admin for help. Do not leave protection disabled.

Does reinstalling Zoom fix Error Code 104102?

It can help if the local Zoom app is damaged or outdated. It will not fix a blocked firewall, proxy, VPN, DNS, or ISP routing problem. Test another network before relying on reinstalling.

What ports are related to Zoom Meetings?

Zoom’s official firewall documentation lists TCP 443, 8801, 8802 and UDP 3478, 3479, 8801-8810 for Zoom Meetings and Webinars, along with Zoom IP ranges and domain rules. Managed networks should follow the current official Zoom firewall page.

Why does Zoom work on mobile data but not Wi-Fi?

That usually means the Wi-Fi network, router, proxy, DNS filter, firewall, or ISP route is the issue. The Zoom app and account are less likely to be the root cause when the same device works on a hotspot.

Can DNS cause Zoom Error Code 104102?

Yes. Stale or failed DNS cache entries can stop the device from resolving Zoom services correctly. On Windows, flushing DNS with ipconfig /flushdns is a practical repair step.