Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Jedi-77]

I have 2 DNR-202L setup at home and they seem to work fine and record video on motion detection. However, in some cases, the video seems incomplete. As an example, the event log tells me that the recorded video is 23:13.02 to 25:10:15... Thats about a good 2 min recording. But as I watch the recorded video, it will play about 50 seconds of it, then stop.  Then jump to the next recording which might be a few minutes later. It seems quite random, as some recordings will be complete, and others will not. Any idea what might be causing this?

For reference, both DNR-202L seem to do this and both are running Firmware 2.02 (however, I did notice this on older firmwares as well). And both are using Western Digital 2TB hard drives.

Thanks

[Jedi-77]

No one experienced this with the DNR-202L...

I'm now wondering if its a problem with the attached cameras. The cameras are 3 DCS-2330L. It just seems like I'm missing blocks of video that I can't play, even through it has been recorded by the DNR onto my hard drive...

[FurryNutz]

Have you tried DView Cam?
I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.

[Jedi-77]

Tried Dview Cam in what regard? To view files recorded on the DNR-202L? Can Dview Cam do that? and if so, how?

I don't want to use Dview Cam as a recording method as that entails leaving a computer constantly running. The whole point of the DNR is that it should do the job on its own.

[FurryNutz]

Did you contact D-Link support about this? 

[Jedi-77]

Not wanting to bring up an old post, but I have the exact same issue. I am running 4 DCS-2330L cameras on a DNR-202L with Firmware 2.02, and my recordings are fragmented. The first 30 or seconds of a recording will play fine, then the the video will stop even though the recording may be a few minutes in length. I have reinstalled Firmware 2.00, and the problem is now gone. So something strange about Firmware 2.02 and the DCS-2330L cameras.

[FurryNutz]

Was a factory reset performed and the DNR setup from scratch after updating to v2.02?

Not wanting to bring up an old post, but I have the exact same issue. I am running 4 DCS-2330L cameras on a DNR-202L with Firmware 2.02, and my recordings are fragmented. The first 30 or seconds of a recording will play fine, then the the video will stop even though the recording may be a few minutes in length. I have reinstalled Firmware 2.00, and the problem is now gone. So something strange about Firmware 2.02 and the DCS-2330L cameras.

[Jedi-77]

Yes it was. I upgraded the Firmware, then did a full factory reset and re-installed all the cameras. But the problem still remains. All of my DCS-2330L cameras will only play about 30-50 seconds of the 3 minute recording that is available. The only firmware version that will work is 2.00. Anything higher than that, and I can't view the entire recording. Of course the downside of not being able to use the newer firmware is the addition of new cameras with every firmware release. Also, as of a recent Windows 10 update, I can no longer play back my recordings through IE11. I have to use HDDViewer to be able to play the recordings. This seems to be a problem only with the DCS-2330L, as my other cameras (a DCS-5222L and DCS-4802E) work fine with Firmware version 2.04 in regards to playing back the entire recording. This is really annoying. If I had not been already so invested in the D-Link cameras and recorders, I would be looking elsewhere. Sick and tired of archaic software and devices that don't work properly.

Was a factory reset performed and the DNR setup from scratch after updating to v2.02?

Not wanting to bring up an old post, but I have the exact same issue. I am running 4 DCS-2330L cameras on a DNR-202L with Firmware 2.02, and my recordings are fragmented. The first 30 or seconds of a recording will play fine, then the the video will stop even though the recording may be a few minutes in length. I have reinstalled Firmware 2.00, and the problem is now gone. So something strange about Firmware 2.02 and the DCS-2330L cameras.

[FurryNutz]

Please contact your regional D-Link office and have them review this. I'll let them know as well.

[GreenBay42]

On your DCS-2330L cameras, do they all have the same video settings?  Under Audio/Video, in the video profile you are using, change the settings (ie try jpg vs h264, lower the bit rate, etc) and see if the recording issues remain. Seems like there is some quirk with newer firmware on the 2330L with the DNR-202L. I looked in the ticket system for both but did not see anyone else reporting this issue.

[Jedi-77]

Yes, they all have the same video settings. They are currently set to record in H.264 format. I haven't tried lowering the video quality, but then again, I shouldn't have to. The cameras and DNR-202L should work as designed without me having to compromise settings. Something in the DNR-202L firmware post version 2.00 has caused this issue, because version 2.00 works perfectly fine in regards to the recordings. It just sucks that it limits what cameras I can use as the newer firmware supports the newer cameras of which I have 2.

Also, scoured this forum for some time, and found other people having similar issues to me, with other camera models. Link to another similar story below.

http://forums.dlink.com/index.php?topic=63428.0

[AllynHin]

Can I ride on this thread or should I start my own? I have the same problem. I have a DNR-202 with a DCS-5222LB camera and two DCS-2310L cameras. I have the two 2310 cameras set to record constantly, but when I view the playback, there are large gaps in the recordings. I tried viewing the playback in Chrome and IE. The gaps are the same. The cameras are set up the same. The hard drive is a 4T WD Elements with 63% free space. The whole point to having the DNR was so I wouldn't have to leave a computer on 24/7, so if that's the solution, I'll dump all the d-link devices and go with a brand with a reliable NVR. (Not a threat, just sayin'.) Is the solution to roll back to a previous version? and will my cameras be compatible if I do that?

DNR-202:
Agent Version: 2.2.0-b61
Current NVR Firmware Version: v2.05.07
Current NVR Device Pack: v2.17.02
Device Pack Date: Jan 07 2019

DCS-2310L:
Firmware Version: 1.08.03
Agent Version: 2.1.0-b04

DCS-2310L:
Firmware Version: 1.08.03
Agent Version: 2.1.0-b04

DCS-5222LB:
Firmware Version: 2.13.01
Hardware Version: B
Agent Version: 2.0.20-b31

Systems:
A:
Windows 10 x64
Chrome: Version 77.0.3865.90 (Official Build) (64-bit)
IE11: Version 11.356.18362.0

B:
Windows 10 x64
Chrome: Version 76.0.03809.132 (Official Build) (64-bit)
IE11: Version 11.356.18362.0

[FurryNutz]

Does the 5222 camera do the same thing or is it only just the 2310 cameras?
Does it happen with just one camera recording all the time while the other don't record?

Was a factory reset and setup from scratch of the DNR and all cameras performed since last FW update?

Whats the distance between the cameras and wifi router?
What is the Mfr and model# of the WiFi router?

I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.10 and .11  DHCP

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com

Set FPS or resolution values on the cameras to something less to test to see if gaps still occur.

Can I ride on this thread or should I start my own? I have the same problem. I have a DNR-202 with a DCS-5222LB camera and two DCS-2310L cameras. I have the two 2310 cameras set to record constantly, but when I view the playback, there are large gaps in the recordings. I tried viewing the playback in Chrome and IE. The gaps are the same. The cameras are set up the same. The hard drive is a 4T WD Elements with 63% free space. The whole point to having the DNR was so I wouldn't have to leave a computer on 24/7, so if that's the solution, I'll dump all the d-link devices and go with a brand with a reliable NVR. (Not a threat, just sayin'.) Is the solution to roll back to a previous version? and will my cameras be compatible if I do that?

DNR-202:
Agent Version: 2.2.0-b61
Current NVR Firmware Version: v2.05.07
Current NVR Device Pack: v2.17.02
Device Pack Date: Jan 07 2019

DCS-2310L:
Firmware Version: 1.08.03
Agent Version: 2.1.0-b04

DCS-2310L:
Firmware Version: 1.08.03
Agent Version: 2.1.0-b04

DCS-5222LB:
Firmware Version: 2.13.01
Hardware Version: B
Agent Version: 2.0.20-b31

Systems:
A:
Windows 10 x64
Chrome: Version 77.0.3865.90 (Official Build) (64-bit)
IE11: Version 11.356.18362.0

B:
Windows 10 x64
Chrome: Version 76.0.03809.132 (Official Build) (64-bit)
IE11: Version 11.356.18362.0

[AllynHin]

Does the 5222 camera do the same thing or is it only just the 2310 cameras?
The 5222 camera is set to record on motion. It rarely has motion in its view, so I can't say.

Does it happen with just one camera recording all the time while the other don't record?
Both 2310 cameras are set to record 24/7.

Was a factory reset and setup from scratch of the DNR and all cameras performed since last FW update?
Yes, for the PitA that was.

Whats the distance between the cameras and wifi router?
No WiFi. The cameras are PoE. The longest cable is 130 feet.

What is the Mfr and model# of the WiFi router?
The router is an AT&T Arris NVG589 with WiFi disabled.

I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.10 and .11  DHCP
I don't understand how that will test the cameras if the network can't see them. A static IP address is set on each camera.

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com
They are enabled.

Set FPS or resolution values on the cameras to something less to test to see if gaps still occur.
That's the first thing I tried. No difference.




[

[FurryNutz]

Please try setting the 5222 to record 24/7 and check the output files for it and let us know if it results in the same thing...