Getting Started | Motion Detection | Troubleshooting
« Back to Support
Problem : You are receiving the "No Sources Found" error message
There are two potential causes for the No Sources Found error:
- The login and password on iCam and the iCamSource do not match. (Please note that they are both case sensitive.)
- The iCamSource on your computer is unable to communicate with the iCam Broker Server.
When you click the Start button on the iCamSource, you should see your webcam's preview video in the iCamSource Preferences window. If not, then there is an issue with your iCamSource setup (see iCamSource Troubleshooting
After clicking the Start button you should also see the words "Connecting ..." or "Connected to Server" in the title of the iCamSource Preferences window. If you see "Connecting ..." then the iCamSource is unable to communicate with the iCam Broker Server, and is either being blocked by firewall or security software on your computer or your network. If you see "Connected to Server" then the iCamSource is able to communicate with the iCam Broker Server, and most likely the iCam Login and Password combination entered into iCam does not match the one entered into the iCamSource.
If you are able to connect when you are at home but you receive the No Sources Found message when you are away, make sure that your computer isn't configured to go into Sleep or Hibernate mode after a period of inactivity. If your computer is asleep, the iCamSource will not be actively running, and you will not be able to connect.
Problem: Unable to connect when iCam is connected to the same local WiFi network as the iCamSource
If you are seeing the "Broker Connection Error" in iCam and your iCamSource has the words "Connecting ..." in the title bar after clicking the Start button then your local network is most likely blocking outgoing UDP communication to the Internet.
If you are seeing the "Source Connection Error" in iCam then there is either some firewall or security software running on your computer that is blocking the incoming connection from iCam to the iCamSource or you have multiple routers on your network that are each creating their own separate sub-networks that are unable to communicate with one another. If you have multiple routers on your network make sure that your iOS (iPhone, iPod touch, or iPad) or Android device running iCam and the computer running the iCamSource are connected to the same one.
Problem: Unable to connect when iCam is NOT connected to the same local WiFi network as the iCamSource
If you are seeing the "Source Connection Error" or "Broker Connection Error" when your iOS (iPhone, iPod touch, or iPad) or Android device is connecting via EDGE/3G/4G/LTE or a different WiFi network than the computer running the iCamSource then the issue is most likely that both the iCam and iCamSource networks are using a complex form of port translation, resulting in one of the few cases where iCam does not "just work" out of the box.
The solution is to configure the iCamSource network's router so that it will be able to accept the iCam connections.
If your router supports UPnP or NAT-PMP (and the option is enabled) you can try checking the Auto-Config Router
checkbox in the iCamSource to automatically configure your router. When you click the Start button, a status message should appear next to the Auto-Config Router checkbox. If the status message contains:
- Success then your router has been configured correctly and you should be able to connect from outside of your local WiFi network. If you are not able to connect and you are now also unable to connect via local WiFi when the Auto-Config Router checkbox is checked then there is most likely firewall or security software running on your computer that is blocking the incoming connections to the iCamSource.
- Error then either your router does not have UPnP or NAT-PMP enabled or the iCamSource was unable to configure it. The next step is to configure your router manually, as explained in this Support Forum Post.
- Dual NAT then you have multiple routers on your network that are each creating their own separate, nested sub-networks. This can make connecting from outside of your local network virtually impossible. The solution is to put the router(s) not connected directly to the modem into "bridge" mode so that they are extending the main router's network instead of creating their own. (It is important to note that some cable and DSL modems do also act as routers. Connecting an additional router to a combination modem/router device can also result in a Dual NAT situation.)
- NAT-PMP May Not Be Enabled then NAT-PMP is likely not enabled in your Apple AirPort Express, AirPort Extreme, or Time Capsule. To enable NAT-PMP in your router, open the AirPort Utility application, select your router, click Manual Setup, and check the "Enable NAT Port Mapping Protocol" checkbox under the Internet > NAT tab.
On the more recent version of the AirPort Utility application the "Enable NAT Port Mapping Protocol" checkbox can be found by clicking the "Network Options..." button at the bottom of the "Network" tab.
- UPnP May Not Be Enabled then UPnP is either not enabled or is not properly implemented by your router. Please refer to your router's user manual for instructions on how to enable UPnP. If you do not have your router's user manual available you can likely find the appropriate information on your router's manufacturer website.
If your router does NOT
support UPnP or NAT-PMP (or the above Auto-Config Router
checkbox solution did not work) then the next step is to un-check the Auto-Config Router checkbox and proceed to forward UDP ports 12000-12100 in your router to the computer running the iCamSource. The step-by-step port forwarding instructions can be found in this Support Forum Post
Stateful Packet Inspection (SPI) Firewalls
If you have checked the Auto-Config Router checkbox and received a Success
status message or have manually forwarded a range of ports in your router to the computer running the iCamSource but are still unable to connect from outside of your local network then your router may have a Stateful Packet Inspection (SPI) Firewall enabled that is blocking iCam.
: In computing, a stateful firewall (any firewall that performs stateful packet inspection (SPI) or stateful inspection) is a firewall that keeps track of the state of network connections (such as TCP streams, UDP communication) traveling across it. The firewall is programmed to distinguish legitimate packets for different types of connections. Only packets matching a known active connection will be allowed by the firewall; others will be rejected.
If your router's firewall is not programmed to recognize iCam as a legitimate connection type then it may be blocking it. Try disabling your router's firewall to see if iCam is then able to connect from outside of your local network.
Problem : Unable to find the iCamSource Preferences window or access or quit the application once it is running.
The iCamSource runs with an icon in the menu bar (Mac OS X) or system tray (Windows) near the clock. If you click on the iCamSource icon, you should be able to then show the iCamSource Preferences window as well as quit the application.
|Mac OS X||Windows|
Problem : Video preview is not appearing in the iCamSource Preferences window when clicking the Start button.
If you are using a USB / FireWire / Built-In
- Make sure you have all of the latest operating system updates and webcam drivers (if applicable) installed.
- Make sure that you are plugging the webcam directly into the computer and not into a USB hub or extension cable.
- Make sure that no other application is already using the webcam.
- Try rebooting your computer as well as unplugging and re-plugging in your webcam.
- Try using different USB ports on your computer, as well as unplugging any other non-essential USB devices.
- If you are trying to connect to more than one USB / FireWire / Built-In webcam at a time your computer's USB bus may not be able to power the cameras simultaneously. Try running other webcam applications to see if your computer can handle multiple webcams being activated at the same time.
If you are using an Ethernet / Wi-Fi
- Make sure that you are using the full MJPEG or JPEG URL from the Getting Started section, and not just the camera's IP address. Make sure that the URL includes the "http://" at the beginning.