D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNR-202L => Topic started by: daveabbey on October 10, 2015, 10:26:32 PM
-
Updating the firmware fails each time.. it spins and spins and then ultimately gives message that it failed.
Frustrating.. my unit is hw version a1 and current firmware is 2.00.10
-
If you are trying to do the update using the mydlink portal, you are not alone, this is something several other customers are experiencing. D-Link is currently investigating these incidents.
As a work around you can try the manual firmware update, follow the steps below:
- Go to http://support.dlink.com/DNR-202L (http://support.dlink.com/DNR-202L) and download the firmware 2.02.00.
- Unzip the packages to your desktop to make sure you can find it once you are inside the local GUI.
- Login into the local IP address of the DNR-202L, you can use the early steps of the wizard to find the IP, cancel out once you know the IP, as an alternative you can check the router's DHCP table to find the local IP address of the DNR-202L
- Go to settings (click the gears icon) and look for firmware update option on the left side menu.
- Browse to the unzipped .bin file on your desktop and begin the firmware update
PLEASE NOTE: You will need to install the AciveX controls to gain access to the Local GUI. If you come across a windows certificate issue, see if you can still accept it (this is one of the issues the new firmware is addressing), if you are unable to override it, go back to to try updating using the mydlink portal, make sure this time you don't use any other application or have other programs communicating to the internet while trying the update the firmware. I know is a lot to do for the manual update, so is OK if you choose not to try. I hope you do and share your experience with others here.
Please let us know.
-
Don't update to the new one
-
Don't update to the new one
Would you like to elaborate a bit more on the reasons why?
-
Mine is stuck in a constant reboot loop after trying to update to 2.02. If they're going to bother us with upgrade warnings, D-Link should do a better job testing their firmware. >:(
-
Others have not reported issues in upgrading the DNR.
PC 3rd Party Security Software Configurations
- Turn off all anti virus and firewall programs on PC while donig FW updates. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.
- Turn off all devices accept for one wired LAN PC while testing.
PC Web Browser Configurations
What browser are you using? IE or FF is recommended to do the FW updates.
If you can't get the DNR back into a working mode, 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.
Mine is stuck in a constant reboot loop after trying to update to 2.02. If they're going to bother us with upgrade warnings, D-Link should do a better job testing their firmware. >:(
-
Mine is stuck in a constant reboot loop after trying to update to 2.02. If they're going to bother us with upgrade warnings, D-Link should do a better job testing their firmware. >:(
same here, and now the dnr is useless and im not recording anything! what a bad idea to upgrade.. though i had to because of java security errors due to some revoked certificate..
what to do now??
-
If you can't get the DNR back into a working mode, 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.
same here, and now the dnr is useless and im not recording anything! what a bad idea to upgrade.. though i had to because of java security errors due to some revoked certificate..
what to do now??
-
Mine is stuck in a constant reboot loop after trying to update to 2.02. If they're going to bother us with upgrade warnings, D-Link should do a better job testing their firmware. >:(
same here, and now the dnr is useless and im not recording anything! what a bad idea to upgrade.. though i had to because of java security errors due to some revoked certificate..
what to do now??
A paperclip to the reset button has zero effect so welcome to the brick club.
I went out and bought a NAS with built in surveillance recording software and added a WD Purple drive made for 24/7 recording. I had planned on doing this eventually, but thanks for the motivation D-Link! Needless to say, none of my D-Link hardware will be replaced with D-Link hardware in the future. There's no point when the software is this bad. Going to go with companies that have the fewer pieces of hardware to keep updated or business class from now on.
-
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.
quote author=quixy link=topic=63587.msg261220#msg261220 date=1446340216]
Mine is stuck in a constant reboot loop after trying to update to 2.02. If they're going to bother us with upgrade warnings, D-Link should do a better job testing their firmware. >:(
same here, and now the dnr is useless and im not recording anything! what a bad idea to upgrade.. though i had to because of java security errors due to some revoked certificate..
what to do now??
A paperclip to the reset button has zero effect so welcome to the brick club.
I went out and bought a NAS with built in surveillance recording software and added a WD Purple drive made for 24/7 recording. I had planned on doing this eventually, but thanks for the motivation D-Link! Needless to say, none of my D-Link hardware will be replaced with D-Link hardware in the future. There's no point when the software is this bad. Going to go with companies that have the fewer pieces of hardware to keep updated or business class from now on.
[/quote]
-
so my dnr-202l got stuck in the reboot loop as well last night after i upgraded to firmware 2.02. after an hour on the phone with dlink they issued me an RMA. i however didn't give up. all night and this morning. i was able to get on the GUI for a few seconds then it would reboot. i had tried 10sec on the reset button then continue to hold it for 30sec with the power cord pulled out then another 10sec with the plug back in and nothing would reset it. i then just held the reset button in and didn't let go the power cord plugged in the whole time. took about a minute or so but i heard a beep!! i had turned off the beeps in the settings already so i knew something happened. it then stayed blinking blue/working for almost 2min. then started the reboot loop again. so i held the pin in again and soon as i heard the beep and the blue light was blinking i went to the IP address logged in and quickly ran a firmware upgrade for 2.01 and it TOOK!! it is now back running with no reboot loop!
-
I recommend you follow this process for doing FW updates in the future:
FW Update Process (http://forums.dlink.com/index.php?topic=42457.0)
Besure to use IE or FF and disable any PC security SW programs before starting the update.
Glad you got it working. Post back if you seen any other issues.
so my dnr-202l got stuck in the reboot loop as well last night after i upgraded to firmware 2.02. after an hour on the phone with dlink they issued me an RMA. i however didn't give up. all night and this morning. i was able to get on the GUI for a few seconds then it would reboot. i had tried 10sec on the reset button then continue to hold it for 30sec with the power cord pulled out then another 10sec with the plug back in and nothing would reset it. i then just held the reset button in and didn't let go the power cord plugged in the whole time. took about a minute or so but i heard a beep!! i had turned off the beeps in the settings already so i knew something happened. it then stayed blinking blue/working for almost 2min. then started the reboot loop again. so i held the pin in again and soon as i heard the beep and the blue light was blinking i went to the IP address logged in and quickly ran a firmware upgrade for 2.01 and it TOOK!! it is now back running with no reboot loop!
-
Glad to hear I'm not alone in all of this shenanigans. I tried updating my DNR-202Ls wirelessly and ended up in the boot loop. Returned them for replacements and tried updating firmware hard wired this time and boot loop. It would appear the firmware is at fault here. I wonder if anyone has successfully upgraded their firmware?!
I did call D-Link who kept me on the phone for about an hour only to conclude the DNR is defective. What's funny is I asked if this is a common issue and he told me I'm the first one! Yea right...LOL
BTW, I have successfully upgraded 6 D-Link cameras through 3 different firmware versions.
This frustration, along with my cameras not being able to record at advertised qualities even though I have more than adequate bandwidth, has encouraged me to never go D-Link again...
I've spent HOURS on this stupid set-up....
-
DNS and DNRs should never be updated by wireless connections. ALWAYS use a LAN wire cable between the DNR and the managing PC to update FW. This also goes for routers. Wireless introduces too many variables. Best practice to ensure a good clean FW installation is to use LAN wired cable connections with NAS and routers and with the managing PC. ALWAYS!
-
Here is a way of manually updating the firmware without having to worry about the browser issues.
How do I manually update the firmware on my DNR-202L (http://support.dlink.com/FAQView.aspx?f=ST1P9C0jMxkTqMSBvzlquA%3d%3d)
Version 2.00 has introduced a large number of fixes and enhancements to the DNR-202L. Take a look at the release notes Click Here! (ftp://ftp2.dlink.com/PRODUCTS/DNR-202L/REVA/DNR-202L_REVA_RELEASENOTES_2.02.00_EN.PDF) read the details under page 4.
-
Thnx for the link. I will try that next time.
I don't believe the issue is with the update process but with firmware 2.02. I'd be interested in hearing from anyone who has successfully updated their DNR-202: with 2.02 w/o bricking their DNR.
-
Thnx for the link. I will try that next time.
I don't believe the issue is with the update process but with firmware 2.02. I'd be interested in hearing from anyone who has successfully updated their DNR-202: with 2.02 w/o bricking their DNR.
Any update on the results? Did it work?
-
http://forums.dlink.com/index.php?topic=63583.0 (http://forums.dlink.com/index.php?topic=63583.0)
Thnx for the link. I will try that next time.
I don't believe the issue is with the update process but with firmware 2.02. I'd be interested in hearing from anyone who has successfully updated their DNR-202: with 2.02 w/o bricking their DNR.
-
MY OS is Windows 10 that I use to upgrade Dlink products in mydlink. I used mydlink on LinuxMint in the past until they changed java crap etc . I have had the same problem upgrading to version 2.02 firmware too on Windows 10 , tried everything from Mydlink install and manual install same results . When I did the update to 2.02 it kept on rebooting over and over I could log into it when the blue light was on by IP address but it starts to reboot before I could do anything . So I ended up pushing reset button to bring back original version after being fed up. It would take version 2.00.1 firmware but not version 2.02 ,weird. The upgrade 2.02 ruined the other DNR 202L It would not reset at all or take manual update to 2.00.1 I was lucky the store replaced it for me . So far I hope there will be a bug fix coming soon as I can not use the DNR on mydlink web site only thru IP address .
-
Found out the problem to the firmware 2.02 upgrade . There was a conflict of IP address on the DNR to the router so it kept on rebooting so I changed the IP address to original IP address of DNR when it was new before any changes to ip address example 192.168.0.199:80 . I had the address before upgrade at example 192.168.0.199:25611 and there was a conflict of booting . So there is a small bug or advise to fix ip address set up when upgrading .
-
I recommend setting a static IP address ON the DNR outside of the main host routers default DHCP IP address pool (192.168.#.100 thru .200), i.e. 192.168.#.20 or .202. This will help avoid any conflicts in IP addressing with other devices and router DHCP handling.
Found out the problem to the firmware 2.02 upgrade . There was a conflict of IP address on the DNR to the router so it kept on rebooting so I changed the IP address to original IP address of DNR when it was new before any changes to ip address example 192.168.0.199:80 . I had the address before upgrade at example 192.168.0.199:25611 and there was a conflict of booting . So there is a small bug or advise to fix ip address set up when upgrading .
-
Found out the problem to the firmware 2.02 upgrade . There was a conflict of IP address on the DNR to the router so it kept on rebooting so I changed the IP address to original IP address of DNR when it was new before any changes to ip address example 192.168.0.199:80 . I had the address before upgrade at example 192.168.0.199:25611 and there was a conflict of booting . So there is a small bug or advise to fix ip address set up when upgrading .
So...are you gtg now with the updated/most current firmware?
-
I updated firmware through mydlink website and got endless reboot loop.
After 2 weeks of returning/replacing item, I installed firmware 2.04.03 , but with internal website. I turned off antivirus just in case. It was successfully.
-
We recommend doing any FW updates manually by downloading the FW file using IE11 or FF browsers and disabling PC security SW.
Enjoy. ;)
I updated firmware through mydlink website and got endless reboot loop.
After 2 weeks of returning/replacing item, I installed firmware 2.04.03 , but with internal website. I turned off antivirus just in case. It was successfully.