Why does Zoom error code 104103 appear? This problem is one of the common ones, because many users complain about it, not knowing what to do. For this reason, we have prepared a special article where we will analyze its causes and solutions. We invite you to familiarize yourself with it.
This glitch in Zuma indicates that the program cannot connect to its remote servers, because there are problems with the Internet connection. The official website states that this may be due to the incorrect operation of the firewall, proxy server or antivirus.
If you have any programs installed on your computer that control the Internet connection, they should be disabled for a while. These can be antiviruses, VPNs to bypass various locks, remote access services, etc.
As an example, let’s take ESET NOD32, which often interferes with Zoom. Disable its protection will come out as follows:
- In the lower right corner, click on the upward arrow to open the Windows system tray.
- Now we right-click on the characteristic icon to bring up the context menu.
- From the proposed list, select the item “Pause protection” .
- And now we click on “Apply” .
In the case of other antivirus programs, the procedure is similar, so you won’t get confused.
We also recommend that you disable any VPN services or make sure they are working and configured correctly.
After that, launch Zoom and check if the error code 104103 appears again. Most likely, you will not see it again. In this case, add the program to the antivirus exceptions so that you do not have to suspend its protection every time, reducing the security of your computer.
If the proposed options did not help to solve the problem, we recommend contacting the project technical support service .
Several others are associated with error 104103: 104104, 104105, 104110, and so on. In all such cases, the reason is the same, and it is related to a problem with the Internet connection. Antivirus or other security software often conflicts with Zoom, preventing the user from communicating in video conferencing. To make sure of this, it makes sense to temporarily disable such protection, and then set the necessary exceptions. And then no more failures will appear. Well, as a last resort – contacting technical support.