Is that supposed to be necessary if UPnP is being used? Both instances of iCamSource are saying that it successfully opened up two different ports. One opens port 12000 and the other opens port 12001. The thread you linked to also seems to imply that you should be able to view everything without configuring port forwarding if you're on the same wifi network as everything else and that EXTERNAL connections wouldn't work. In my case, neither works.
A quick overview of my setup... I have two instances of iCamSource running on two different machines. One is running on a Mac mini with the latest OS X Yosemite running on it. The other is running on a Dell laptop running Windows 7. The Mac mini is responsible for connecting to a network IP camera with MJPEG while the Dell laptop is responsible for its own integrated webcam and microphone. I have both configured to use the same username and password. Both instances of iCamSource are also configured to "Auto configure router" and both indicate that this part of the process was successful. The Mac mini says it is connected through port 12000 while the Dell laptop says it connected through port 12001. However, in the iCam app on my iOS devices, only the network camera from the Mac mini appears. No matter what I try, the camera from the Dell laptop never appears in iCam and I'm literally at my wits end. I swear this had worked before but I haven't been running multiple cameras in awhile now.
I completely uninstalled iCamSource (or so I thought anyway) from the Dell laptop and reinstalled it but my username and password were still in there so I'm thinking there were still some settings left over. I'm starting to think maybe the update I performed to iCamSoure is what borked it... and it wouldn't be the first time. I swear I run into issues like this every single time I try and do an update to the Windows version of iCamSource.
Does anybody have any suggestions? I don't understand why it would say that it's "connected" if it really isn't.
Let me start off by saying that iCam was the best $5 I've ever spent on an app and one of the few that I truly use on a daily basis!
I just wanted to drop a note and make you guys aware of an issue I've discovered after recently upgrading my router. Previously, I had been using a Linksys WRT54GL (802.11g) router and I was running the third-party DD-WRT v24 firmware. With this router, I had been using the "Auto config router" option in iCamSource and everything worked fine and dandy. A couple of months ago, I decided it was finally time to upgrade from 802.11g to 802.11n and I ended up getting a Linksys E3200. Everything seems to be great with the router... except the "Auto config router" option in iCamSource no longer worked. After doing some debugging of my own, it appears as though the method iCamSource uses to open up the ports via UPnP does not work with the Linksys E3200 -- even with the latest Linksys firmware. The strange thing is that other things do seem to work with UPnP, specifically my Xbox 360. I found a tool called "UPnP Port Tester" that I was able to use to connect to my router and see what UPnP ports/services were open on the router and while I see the Xbox360 listed, nothing ever shows up from iCamSource.
This isn't a huge inconvenience as I've simply stopped using the "Auto config router" option and manually port forwarded ports 12000 to 12100 and everything is working properly again but I just wanted to bring it to your attention. Have a great day!
iPhone 4 here in Middletown, CT and my AT&T 3G IP begins with 166. My router is a Linksys WRT54GL running a newer build of DD-WRT with UPnP enabled and I have the "Auto config router" option checked. No issues here.
It seems like anytime I choose to upgrade my version of iCamSource, I almost inevitably end up having issues. Most of the time, it seems like the upgrade doesn't really upgrade the existing installation -- it installs it alongside the existing installation. I'm not positive, but I think this may be a result of possibly choosing different options when the installer asks you if you want to install it for "Everyone" (the default option) or "Just Me." Shouldn't the installer be able to detect if iCamSource is already installed and know which option was originally chosen and just follow this setting?
In any case, I almost always have to completely uninstall iCamSource, run the registry cleaner file to remove all traces of it, and then install the new version (and setup my network camera again). If I don't, I end up having issues such as iCamSource eating up an excessive amount of memory and becoming unresponsive. I'm not sure why, but it definitely seems to be an issue related to the registry settings since cleaning out all the keys is guaranteed to fix it 100% of the time. If anybody else has any other suggestions about the upgrade process or thinks I'm doing something wrong, please let me know.
Also, to the SKJM webmasters: Would it be possible to post release notes about what was added, changed or fixed when a new version of iCamSource is released? That way people can make an informed decision as to whether or not they event want to attempt the upgrade. I see that 2.2.3 is out now and I'm currently running 2.2.2 but am not sure if I event want to bother upgrading.
I un-installed the version I was running before (2.1 I believe) and then ran the registry editor file you provided to get rid of all iCamSource registry keys and then re-installed the latest version (2.1.1). It's now up and running again! Like you said, I had to re-enter all the information for the camera(s) but at least I'm actually able to start the program again. And yes, to answer your previous question, I had restarted several times so it looks like the root of this problem was a registry key issue. I just hope it doesn't happen again... if it does, I'll be sure to let everybody know in this thread.
I'm having this exact same issue. I uninstalled the previous version I had (1.4.2.5 BETA, I believe) which would crash sporadically and installed the new 2.1 version. It appeared to run fine at first but then crashed sometime within the next 12 hours after installing it (not exactly sure when). Since then, every single time I try and start iCamSource it crashes immediately and I get the "iCamSource.exe has stopped working" message. This is on Windows Vista 64-bit edition on my Dell Inspiron XPS laptop.
I've tried all the aforementioned suggestions, including running the DeleteAS.reg registry file, installing the Visual Studio Redistributable package (and rebooting afterward) and I have the .NET Framework 3.5 SP1 installed which appears to be the latest version. I really hope this issue gets resolved soon... the last several versions of iCamSource have been far less than stellar.
EDIT: Also, in case it matters, the ONLY camera I have configured to run in iCamSource right now is the wireless AirLink747W (recommended by this very forum) over an MJPEG URL.
Wish I had checked back sooner to see your message... I was there again last Friday evening and attempted it again but was greeted with the same result. I let it sit there and spin the loading animation for awhile and eventually I got back the message "Unable to connect to one or more camera sources returned by the camera object broker" or something to that effect. I may actually be there again tonight around 8pm EST or so and will give it another try then. I can say for sure that their network is not "restrictive" at all and also has UPnP enabled so I'm not exactly sure what would be blocking it from their side. I will send you a PM with their DDNS name that I use to remotely connect so you will know what IP address the connection attempt (if it makes it through) is using and hopefully see if the issue can be diganosed.
EDIT: I also forgot to mention that their router has also been reset in between connection attempts, so that should've eliminated the possibility that their router just "glitched" and needed to be rebooted.
Thanks for the response. The only real difference is that my parents have Comcast cable while I have AT&T Uverse Internet with the type of gateway device you described. However, I have a Linksys WRT54GL in DMZ mode on it and that is also performing DHCP services. I also have my parents using a WRT54GL and both are running DD-WRT v24 (build 13604) firmware. Neither locations have any other sort of connectivity issue. Again, if the gateway device on my end was somehow the issue I'm not sure why it works over 3G. I'll have to try it again the next time I'm down there.
I'm not getting any error messages but I've discovered what may be a potential bug in either iCam or iCamSource. First, a little background information...
I set up the wifi network at my parents' house as well as my own. For convenience sake, both of these networks have the exact same wireless settings: Same SSID, same encryption type and key, same IP address range, etc. This allows my dad to jump on the wifi network at our house with his iPhone without having to join the network as it already recognizes the network name and encryption settings. The same is true for when I visit their house with my own iPhone.
However, I've noticed that when I use iCam from their house, it never makes a connection. The "loading" animation just sits there and spins constantly and I never get the webcam images up on the screen. If I turn off wifi on my iPhone and try over 3G, it works fine. Turn wifi back on and it doesn't work again. This leads me to believe that either iCam or iCamSource thinks I'm on the same local network that the cameras are on and is looking on my parents' network for the cameras... I'm not sure if it's doing this based off of the SSID, the IP address range, or what it is doing but if this is the case, I think a better solution would be to have it do an "external IP address check" before attempting to connect. If the external IP addresses don't match, then it's safe to assume that it needs to connect over the internet instead of over the local network.
Can anybody else confirm this behavior? I have the latest iCam update as well as the latest iCamSource... I think. I will double check when I get home from work tonight.
Jay, do any of the cameras you just mentioned have an "image flip" option in their settings? I only ask because I had been planning on purchasing a couple of the Linksys WVC80N cameras but am now re-considering as I've discovered that Linksys apparently did not include the option to flip the image vertically in its firmware. This is a feature I'd really like to have as I will most likely be mounting several cameras from the ceiling and not having the ability to flip the image would make it pretty unusable.
Or, I guess another question would be, are there any plans to support a "flip image" option in iCamSource at some point in the near future?
Show Posts
