Search results

It's a shame they don'y have telnet on these. They used to have it, but switched it off on later firmware, then removed the daemon. Would be a good way to reboot it and possibly check for memory leaks. I've checked mine and port 23 is shut when I scan it. Sending it a signal to gracefully...

Phil, that barcode above the serial number is giving away the serial number.

Can you test continuity to the pins via what’s left attached to the socket?

I found some suggestion that turning off UPnP might help (on the NVR). It’s not under Network, NAT on mine.

Can you set the FTP server to force passive FTP? Or try another one that lets you. How do you end up setting a static route and changing the default gateway? Can you eliminate some of this for troubleshooting purposes?

That certainly explains it, thanks. It feels like we had most activity below version 1 then around 1.1 changed to version 2, and now we’ve hit 2.2.x and gone to v3. It seems an odd release numbering scheme. The nightly builds have now gone to v4, so we’ll see that in due course.

It’s not accurate to say it hasn’t been updated in three years. What about all those Weatherwax releases? They have been supporting HEVC using x265 for quite a while too.

The full reset won’t affect the firmware. It’s just wiping the configuration, not the whole device.

The files from that camera go up numerically. I can’t speak for your other cameras. I’d look at concatenating them using FFMPEG.

It's a bit off calling it a private codec. They issued a document in Dec 2016 and they stated it was compatible with HEVC standards. I'll accept, as I've said before, that's a bit of a movable feast but it ought to be broadly compatible. Do you have a small sample file that you can share...

I gave up crimping after some poor experiences and much prefer IDC punch down over crimping. It allows you to run bare cables almost point to point (drilling smaller holes than for plugs) and then use some bought patch leads to finish the job. Small patch panel near the NVR and network switch...

Can you take the lid back off and check inside. I presume it’ll have the usual cables and plugs, maybe some ribbon cables. Make sure nothing has come adrift and that power is getting to the components. Might be worth temporarily disconnecting the HD, just as a troubleshooting measure.

What are the signs of life? Do you have any LEDs or fan noise?

It’s impossible to say.

I’d have thought IP clash, ORBI network shutting the port or problem within the NVR would cover the possibilities. If the discovery tool can’t find the NVR at the time, then the NVR has no connection to the network. You might get away with a partial reset, or even a reset then restore the old...

Simplest option would be to connect to a working NVR. Other than, it would depend on the file system the particular manufacturer used.

Can you reset the NVR and set it up afresh? It might eliminate a bug in there. When you can't reach it, have you tried pinging the address of the NVR? What does your network set up look like? Do you manually allocate all the IPs?

Mine is a TP Link. I’d expect Netgear or any of the bigger brands to be fine. Maybe your wifi is not so good. I use separate devices for that too, as the stuff built into routers isn’t always great. I use Apple Airport and they are fine. Added a Ubiquiti UniFi, but setting up is a bit more work.

Run them all through a decent gigabit switch instead of the router.

Good to hear you can play them. I don't get the motion lines on mine, so maybe your NVR has an option mine lacks. Hopefully someone else has a suggestion.