NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Retired_Member's avatar
Retired_Member
May 22, 2014

Firmware Version 6.1.8 problem

I have a ReadyNAS 316 with OS6 using IE 11. I have not turned on my server for a while and in the administration site it asked me if I wanted to download Firmware Version 6.1.8 which I did. Now it is stating on the screen: Connection Lost. Connection could not be restored. Check your device. Do not reboot the device. Call Netgear for support. On the server itself it says: Restarting now. See you soon. for the past hour. Any thoughts on this please? P.S.: I have restarted the server several times using the ReadyNAS administration sites reset button. I'm about to just shut it down if I don't see any progress.

Since then I have investigated and in http://kb.netgear.com/app/answers/detail/a_id/7004 it states under: 2.Browser version. If you are faced with this error message please check your browser version. If you are using an older browser version please upgrade to a later version to ensure compatibility. Please try accessing the web management using a different browser. Firefox and Chrome browsers do not see this compatibility issue. If you are presented with this error and you have confirmed you are running a newer version of Internet Explorer, Firefox or Chrome then it is safe to assume it is not a browser compatibility problem.

I entered the admin page using Chrome. It says the download was complete and asked if I wanted to reboot. I did and it's still not working.

As soon as I entered the admin page using Chrome

2 Replies

Replies have been turned off for this discussion
  • DJDOC,
    Can you recall what firmware rev the 316 was on before V6.1.8? What add-on's may have been put on.?

    Article #7004 dealt with browser issues in 2013 where they were problems with earlier f/w revs., but that is not your issue now.

    If you cannot access data, and make not progress, you will need to open a support ticket, and enable SSH.

    Regards, Marto
  • Retired_Member's avatar
    Retired_Member
    Thank you for the reply Marto. Support has fixed the problem.