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

Forum Discussion

PFS's avatar
PFS
Aspirant
Apr 16, 2016
Solved

readynas 202 user login via browser fails

Similar problem as discussed in topic https://community.netgear.com/t5/Using-your-ReadyNAS/readynas-104-user-login-fails/td-p/1025727 but now for an rn202.

Followed the instructions as mentioned in http://kb.netgear.com/app/answers/detail/a_id/23178 but after entering the user credentials the log in window remains reappearing.

RN202 is not mentioned in the list of models that the solutions applies to.

Any suggestions?

  • I don't use HTTP, but I see it is greyed out if you try to enable it, so I guess that is true.

5 Replies

Replies have been turned off for this discussion
  • The solutions apply to all OS6 units.  Note that you can only go to a share (http://nasname/share), not to top level of the NAS (http://nasname or http://nasip), and share names are case sensitive.  If you try to go to top level, you will be redirected to te admin page, where only admin credentials will work.  But HTTP access is really a pretty clumsy way to access the NAS. 

    • mdgm-ntgr's avatar
      mdgm-ntgr
      NETGEAR Employee Retired

      Pretty much anything in the UI should work the same on all OS6 models. We don't have performance graphs in the UI on ARM models and obviously there are some differences due to hardware (e.g. number of drive bays - can't create a RAID-5 volume in a 2-disk NAS, as a RAID-5 volume requires a minimum of three disks).

    • StephenB's avatar
      StephenB
      Guru - Experienced User

      Sandshark wrote:

      But HTTP access is really a pretty clumsy way to access the NAS. 


      Users normally access the NAS using windows file sharing (\\ipaddress or \\ipaddress\sharename in file explorer, or by adding a network place, shortcut, or creating a mapped drive).

       

    • PFS's avatar
      PFS
      Aspirant

      Thank you Sandshark, I had not realized that the case sensitivity and the fact that a user can only access shares were the problem. Both acces methods via a browser and via windows file sharing work properly after all. Despite HTTP acces is clumsy as you say, I had to try it to find out how it works.

       

      Is it correct that after a user has logged in using HTTP access, the user's personal folder remains hidden? Because when using windows file sharing the personal folder is displayed properly between the shares the user is allowed to access. 

       

      Thanks again

       

       

       

      • I don't use HTTP, but I see it is greyed out if you try to enable it, so I guess that is true.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More