Hmmm that is not good ::)
I will report it and make sure it gets resolved as soon as possible.
There are multiple support tickets out so hopefully there will be a quick fix.
extreme bad programming here to cause this bug. when will it be fixed? and where will download link be posted. the bug is in the hdd windows program and NOT in the 202l firmware. proved by sniffing the web traffic and the web interface viewer is correct.
my images show that the hdd software is where the bug is. the hdd software is requesting the year 1-2004 when it should be asking for 1-2020
please run wireshark and see for yourself.
lets hope fix is asap and will you post the fix here? so that we can be notified.
Has this been resolved yet? I had an incident earlier this morning where something was stolen from the front of my property. I went to view my videos on HDD Viewer only to find I cant select 2020 as a year to view my files!! This needs to be resolved immediately, c'mon D-Link!
Engineers have notified the vendors and hope to have this fixed shortly.
Well, I can confirm that the problem is not with the DNR-202L device. The problem is with the HDD Viewer Software.
As a temporary solution, I have manually changed all the dates on all my DNR-202L devices to 2019. This enables me to view the recordings in HDD Viewer, even though the dates are off by one day since we are in 2020. But better than nothing at this stage.
I'm still hoping for a speedy solution to this by D-Link as this is ridiculous that we are expected to use dated software with such a silly bug. However, I am already pricing up another system by either Swann or Reolink to replace this non-supported D-Link system if a solution is not found in regards to an update and proper working HDD Viewer software.
my images show that the hdd software is where the bug is. the hdd software is requesting the year 1-2004 when it should be asking for 1-2020
please run wireshark and see for yourself.
lets hope fix is asap and will you post the fix here? so that we can be notified.
D-Link is the Mfr, They and other router Mfrs use 3rd party vendors for code packages that D-Link complies and puts in FW or SW. Same with HW. Router mfrs use different chip sets in there routers. Up to vendors and D-Link to make it work on HW platforms. D-Link used to do there own QoS code. Now It 3rd party I believe among other things. ::) I wish router Mfrs would no rely on this as much as they have. :-\
what is the reply from dlink dev group for this simple 5 minute fix?
Why are they fixing the DNR-202L firmware, if the issue is with HDD Viewer software?
did you get date for the 202l fix? can you provide the dlink team contact info for us to escalate?
I sure hope someone on social media doesn't expose this bug to the world for it looks bad for dlink to be taking so long to solve such a simple fix while users are totally dead in water.
New DNR-202L_REVA Firmware v2.5.8_Beta works perfectly. Thank you!
New DNR-202L_REVA Firmware v2.5.8_Beta works perfectly. Thank you!
Update from Professor: I am using the DCS-932LB Cameras (4 of them). As I wrote earlier no problems on the new DNR-202L_REVA Firmware v2.5.8_Beta works perfectly. Playback of videos is NOT an issue for my camera system and the new DNR-202L firmware. At least they got it right in setting the maximum date to 2070.
thanks, this new viewer works well on my device DNR202L. good to uninstall the older version and install this one. try my home 4 unit of pc (windows 10 version 1909)
I have had an occasional (once every few days) long loud beep from the using the new beta firmware. Can't pin it down to any specific events though. Other than that everything works OK - no recording or playback problems
nothing has changed for years. issue is the new firmware
Can you check your Logs to see if you see any of these in the logs?
system watch-dog reboot.(code 64)
Has your DNR been factory reset and setup from scratch since the FW update?I have had an occasional (once every few days) long loud beep from the using the new beta firmware. Can't pin it down to any specific events though. Other than that everything works OK - no recording or playback problems
[/quote
I did perform a factory reset from scratch since the beta Firmware update. Nothing in my system logs to show why the beep occurs. I have not had a long loud beep for the past 7 days though. Seems to be a random occurrence so far. My recording hdd is not full. I use a WD MyPassport 2TB. Have 2 DC-932LB cameras on 24 hour recording mode.
I use the following and have changed nothing in camera or HDD setting except updated to latest firmware
1. Internet Explorer 11
2. Cameras DCS-932L (2 cameras on my network)
- 1 Camera records 24/7, other camera records for 12 hours/day
3. DNR-202L is used to setup and register Mydlink service
4. Issue is intermittment. I sometimes have the code 64 WebUI report every few hours, sometimes not for a day or so.
5. HDD used for recording is 2TB Passport Ultra that has been in use for 3 years without any problems until the updated firmware was installed then a consistent Code 64 error.
6. Factory reset of DNR-202L then installation of new firmware
64 bit Internet Explorer 11
I have one camera streaming 24/7 and the other 12 hrs/day. The reboots are random - 21 hours without a reboot then 6 reboots in 3 hours.
it has nothing to do with the HDD. It is a bug solely in the latest firmware. :'(
I have motion detection set for my 2 cameras. One camera 24/7 and the camera set for 12 hours/day. The Code 64 error is random sometimes 6/day and then 1/day and sometimes none. The error doesn't coincide with the motion detection being triggered.
My system config has not changed for YEARS, i have motion detection on 1 camera. no reboots on previous version of FW. Upgrade to lastest FW and reboots happen.
I will try a usb thumb drive and will report back in about 2-3 days with logs etc.
it is very easy for dlink eng to fix the issue. they know what in their code they changed to fix the 2020 bug and remving it, stops the reboots. they just need to read their code or perhaps they should open source it and then we (I) can fix it!