This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
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.
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).
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).
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.
