Author Topic: iCam stops working after ~1 Hour  (Read 3213 times)

Simo

  • Newbie
  • *
  • Posts: 5
    • View Profile
iCam stops working after ~1 Hour
« on: November 11, 2010, 06:23:59 PM »
Hi,

Is anybody else having the issue, where iCam (Windows XP) just stops working after a while?

It works fine, then all of a sudden the iPhone app / online just stops working. It's running two USB cameras.

Any Ideas?

OUAnthony

  • Hero Member
  • *****
  • Posts: 801
    • View Profile
Re: iCam stops working after ~1 Hour
« Reply #1 on: November 11, 2010, 08:15:07 PM »
Is the program crashing? I had issues with my icamsource crashing in Windows before I had set up port forwarding. Do you have auto port configuration enabled? If not, have you configured manual port forwarding? If you haven't done either of those, you might try that first. for auto port forwarding, you also need to have uPNP enabled on the router. Of course, your issue might not have anything to do with this...but it was the issue when my icamsource was crashing. Once I set up port forwarding, it stopped crashing. In fact, I can't remember the last time the program crashed.

Stefan

  • Administrator
  • Hero Member
  • *****
  • Posts: 2358
    • View Profile
Re: iCam stops working after ~1 Hour
« Reply #2 on: November 11, 2010, 08:54:26 PM »
When things "stop working" what error messages do you see in iCam or the iCamSource?

Simo

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: iCam stops working after ~1 Hour
« Reply #3 on: November 11, 2010, 11:27:01 PM »
The Source seems to work fine, the iPhone/Web will say No sources found.

Stefan

  • Administrator
  • Hero Member
  • *****
  • Posts: 2358
    • View Profile
Re: iCam stops working after ~1 Hour
« Reply #4 on: November 12, 2010, 12:56:36 PM »
Is your computer possibly going to sleep after a period of inactivity or losing its internet connection?

Simo

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: iCam stops working after ~1 Hour
« Reply #5 on: November 12, 2010, 11:46:38 PM »
Hmm don't think so. It's a really weird issue that came about on the last BETA I was using but seems to have remained....

Ill keep a close eye on it and see if I can work out what triggers it.