NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Linn AMS needs login free access to 102
I have a Linn Akurate Music server (Linux, http://docs.linn.co.uk/wiki/images/0/0a/AMS_installation_manual.pdf) that has been running happily for five years, pulling it's music off an NV+. The PSU in the NV+ failed (unable to check settings in the NV+) and I have replaced it with a 102. (Managed to save media off old discs - phew!)
It needs login free, NFS access to a share called "Media" with a capital M. I have set up the share and tried every possible combination of settings, but cannot get it to connect. Linn have said that if I type "\\<nas_name>\Media" into Windows Explorer and it asks me for a network password, the AMS will not be able to connect. This always seems to be the case no matter what combination of settings I try.
Also I spotted in the R6 software manual:
"2. Enter \\<hostname> in the Windows Explorer address bar. <hostname> is the name that you assigned to your ReadyNAS system or the default hostname if you did not change it.
Note:
If you cannot access the ReadyNAS using its host name, try entering \\<ReadyNAS IP address> in the Windows Explore address bar instead. <ReadyNAS IP address> is the IP address of the ReadyNAS.
You are prompted to log in to your ReadyNAS system.
3. Enter a user ID and password. You can log in with administrator or user credentials. If you log in as a user, your access is limited by the settings configured by the ReadyNAS system administrator"
Can someone please help me with how to get this to work? Any halp gratefully appreciated...
Many thanks in advance,
gimbers
It needs login free, NFS access to a share called "Media" with a capital M. I have set up the share and tried every possible combination of settings, but cannot get it to connect. Linn have said that if I type "\\<nas_name>\Media" into Windows Explorer and it asks me for a network password, the AMS will not be able to connect. This always seems to be the case no matter what combination of settings I try.
Also I spotted in the R6 software manual:
"2. Enter \\<hostname> in the Windows Explorer address bar. <hostname> is the name that you assigned to your ReadyNAS system or the default hostname if you did not change it.
Note:
If you cannot access the ReadyNAS using its host name, try entering \\<ReadyNAS IP address> in the Windows Explore address bar instead. <ReadyNAS IP address> is the IP address of the ReadyNAS.
You are prompted to log in to your ReadyNAS system.
3. Enter a user ID and password. You can log in with administrator or user credentials. If you log in as a user, your access is limited by the settings configured by the ReadyNAS system administrator"
Can someone please help me with how to get this to work? Any halp gratefully appreciated...
Many thanks in advance,
gimbers
10 Replies
Replies have been turned off for this discussion
- The instructions you are quoting are for CIFS, not NFS. Did you enable NFS for the share?
Also, when you look at share settings, click on the network access tab, and then the NFS tab underneath that. Do you see "AnyHost" with "read/write" checked?
When you click on the File Access Tab, do you have Everyone, Folder Owner and Folder Group all set to "read/write"?
It would be helpful to know what credentials (e.g., user name) the Linn server uses when it accesses the NAS share. Perhaps you could ask their support that?
Also, what firmware are you running in the RN102? - Hi StephenB,
Thanks for the reply.
NFS is enabled for the share, Linn have specified that this is the protocol the AMS uses. I have only enabled SMB so I can try and access it from my Windows PC for testing purposes. AnyHost is checked for read/write, and on the File Access tab, all options are set to read/write. I tried adding a Host with the AMS IP address, but this also didn't make any difference.
I think, according to Linn, it doesn't use any credentials. I have also seen things saying "set up a user with the same name and password as your computer". To log in to the Linn AMS, username is "root" and password is "aap", but the RN102 (running 6.1.1) won't let me create a user called "root" because that is already used in ReadyCloud or ReadyNAS Remote, even though I am not using either(?).
Arrrggghh,
gimbers - I think it could default to nobody and nogroup. Maybe try changing the ownership of Media to nobody and the group to nogroup and see if that helps?
Also it is case-sensitive, so make sure it is Media, and not media. Are you using the built-in Media share? Another thought is to rename that temporarily, and create a fresh Media share. - What is your volume name? The default I think is data, but you may have changed it.
It seems with the new readynas units, the nfs path must contain the volume and the share, normally you can omit the volume from the full address.
The address should be:
nfs://ipaddressofnas:/volumename/sharename:/pathinshare
Not sure how the linn asks you to enter this.
Obviously read access at least must be enabled, start with everyone and anonymous access, then see if it still works by being more restrictive if you need to. Alternatively, only give access to the ip addresses of your linn and the PC. - I don't think linn asks, the Media sharename is hard-coded. I haven't tried to mount a share from another linux system, so I am not sure if the pathname has in fact changed.
- I have a Dune HD media player, the full path that it uses to access my Ultra 6+ does not require the volume name, just IP address then share name and path. When I change the IP address to that of my 316 it fails to reach the relevant media files. Adding in the volume to the full path as I've described before, corrects the problem.
That would explain it. Unfortunately OP has no workaround, since Linn hard-codes the path.vandermerwe wrote: I have a Dune HD media player, the full path that it uses to access my Ultra 6+ does not require the volume name, just IP address then share name and path. When I change the IP address to that of my 316 it fails to reach the relevant media files. Adding in the volume to the full path as I've described before, corrects the problem. - Thanks StephenB & vandermerwe.
In order of your replies:
I can't change the ownership of Media to nobody - options are root, admin, guest and two users. I can't change the Group of Media to nogroup - options are root, admin, guest, users.
I have tried all permutations of root/admin/guest.
It is case sensitive and it is "Media". There were no shares at all on initial installation, so this is a new share, with nothing in it, called "Media".
The Linn doesn't ask for a name, the name is hard coded as "Media". I therefore cannot add the volume to the full path as I can't edit the path. All you can tell the Linn is the IP address so it knows where to look for the share "Media".
Anything else to try?
Many thanks,
gimbers - Have you contacted Linn, they seem to a high end company and should deliver some high end customer service. Perhaps they have a solution.
This is a long shot: Can you add the volume name to the end of the IP address ? Ipaddress/volumename
A very long shot.vandermerwe wrote: ...This is a long shot: Can you add the volume name to the end of the IP address ? Ipaddress/volumename
I agree that checking with Linn makes sense. Fixing this properly requires their help - and without the fix, their server won't work on any new NAS.
Another approach is to go in with ssh, and add a new NFS export. This might not survive NAS reboot or NAS firmware upgrade though.
Perhaps someone from Netgear can comment on whether the change in mount point is permanent, or on the list of things to fix?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
