03-07-2007 03:27 PM
03-08-2007 02:10 AM
03-10-2007 07:15 AM
03-10-2007 10:39 AM
03-11-2007 05:21 AM
Hmm well I presume you have camera working as wireless and not connected by ethernet cable to the router? If so then it might be worth changing from Sololink to DynDNS as per instructions from page 1 onwards of this thread as this service provider seems more reliable especially as you mentioned your IP address changes frequently. Make sure you also download DNS updater software too.
Unfortunately, the downloadable DNS updater software resides on the PC not the camera so will only update the IP address when it changes if the PC is left powered up although there is an option to run it as a service on the PC so you don't have to be logged in to Windows when you go away.
The Linksys camera resident software does suggest it will check IP address independent of the PC being on every 4 hours (by default) with the chosen DDNS host site but mine keeps reporting it's failed to update for some reason so I have a few probs myself although I can still access camera locally and remotely. This is obviously a tricky area so I'd welcome other peoples tips on this as well.
03-11-2007 09:40 AM
Yes, it is set up as a wireless camera. Having the DNS updater reside on a PC sort of defeats the purpose of having an Internet camera, it would seem to me. In my situation where I want to do unattended monitoring, probably would not work. Besides if a PC must be running than a simple, much cheaper USB camera would work just as well.
The Linksys WVC54GC camera clearly states on the box "Built-in stand-alone web server, no PC necessary." In my mind that means I should not have to have a PC running so the camera can function as an Internet accessable device. The DNS updates appears to reside in the camera. At least, any adjustment to the setting are done after logging into the camera.
One other issue and this may be related, the camera will not send an email on motion detection. The error is:
03/10/2007 19:15:59 SMTP: Error during the connection or timeout.
03/10/2007 19:12:49 Alert: Triggered.
This may be due to a router setting or port issue as Outlook can send email ok. Has anyone else had this problem?
03-11-2007 03:52 PM
03-11-2007 06:34 PM
03-12-2007 02:03 AM