This article contains troubleshooting information

ERROR#702: Port not mapped

Source-Connect | Version 4 | All Operating Systems

Description

When users try to start a session in Source-Connect 4, they receive an error message saying the ports are not mapped.

Reason

The port test for Source-Connect has failed after enabling custom network settings - most commonly because you have not configured port forwarding rules on your router. It might also be caused by firewalls, anti-viruses, anti-malware, or "protection" application blocking Source-Connect's access to the ports. 

Actions

If you have an active firewall (on Windows or Mac), an anti-virus (Kaspersky, Avast, etc), or other protection software (McAfee, Norton, Malwarebytes, etc), make sure to check the settings for port mapping. Most of these applications have specific settings for ports.

If you have McAfee, you can also:

1. Go to Network Devices.
2. Select Source-Connect loader.
3. Scroll down to the bottom and click "Edit".
4. Allow all ports through for Source-Connect.

Alternatively, add a Windows firewall rule to allow Source-Connect through, and do the same for every "protection" software.

If all of the above fails, uninstalling "protection" software fixes the issue.

We also have a general, step-by-step port forwarding guide that you can refer to if you are trying to do your own port forwarding.

If you continue to receive the warning on Source-Connect, contact our support team.