Ok, bear with me here.
All today (appeared since 4.2.6.6 installed) I've been getting lost signal all day on all six cameras. I've spent the evening testing, ensured BI had the latest version, turned watchdog off on all cameras, all was good on that end.
Checked all my cables with a proper cable tester, upgraded the firmware on my PoE router, reset to factory settings, no change. Router log says that the port state is changing from up to down, which is different from when the cable is unplugged, something is forcing a restart on the cameras. The log was full of these, each camera restarting every three minutes.
Disabled the BI service, closed BI, waited two hours and zero additional disconnects of the cameras in the logs.
I've just gone and checked again and there's been a 4.2.6.7 release in the last couple of hours. I've checked the 'what's new' and no mention of any updates/hotfixes, so I assume the update was rushed out to fix this issue. Given that 4.2.6.6 has only been out a few days, some people might not even catch this, just a friendly heads up as I spent about four hours this evening trying to fix the issue.
All today (appeared since 4.2.6.6 installed) I've been getting lost signal all day on all six cameras. I've spent the evening testing, ensured BI had the latest version, turned watchdog off on all cameras, all was good on that end.
Checked all my cables with a proper cable tester, upgraded the firmware on my PoE router, reset to factory settings, no change. Router log says that the port state is changing from up to down, which is different from when the cable is unplugged, something is forcing a restart on the cameras. The log was full of these, each camera restarting every three minutes.
Disabled the BI service, closed BI, waited two hours and zero additional disconnects of the cameras in the logs.
I've just gone and checked again and there's been a 4.2.6.7 release in the last couple of hours. I've checked the 'what's new' and no mention of any updates/hotfixes, so I assume the update was rushed out to fix this issue. Given that 4.2.6.6 has only been out a few days, some people might not even catch this, just a friendly heads up as I spent about four hours this evening trying to fix the issue.