ReadyNAS Remote user priv..

[kh_vorsteh]

My user-id in DUO are the same as my windows user (different passwords), and when i connect to my DUO i get my privare share and the public shares on DUO.
My readyNAS Remote user have also the same user-id as my Windows/DUO (different password) and when i connect via Remote i get my private and public shares there as well.

If i had created a Remote-user with other id, say "Turbo", then i will only get public shares with guest authority ?

Can there be several Remote-users named "John" ? or must Remote-user-profile have a property for "Connect to ReadyNas as" "John" if remote-user is named "Turbo" ?

[yoh-dah]

Keep in mind that the Remote username is used just to get remote access (consider it like a VPN login). You will still need to login to the ReadyNAS using the username you use on the LAN to access the ReadyNAS shares, or user will just have access to shares with guest access.

[blue_avatar]

Hi,

I was trying to use the remote feature the other day and was just a little confused on how user accounts are managed. Apologies in advance if this topic is already covered elsewhere - if a link is provided, I'll happily jump over and read that.

I logged into the ReadyNAS front panel, created an initial user account for myself, and then added a second. I then opened up the ReadyNAS remote admin page, and searched for users to add. Only the first user account came up. I added it, but a second search attempt came up empty. Is there something different perhaps about that second account which prevents it from appearing in the box? Or am I going about this completely wrong and should be treating the user accounts as separate?

BTW, in running the ReadyNAS remote desktop client I was able to successfully access my ReadyNAS using the first user account that I added, so it seemed to work ok. I must be missing something though, due to the problem with the second account.

Thanks for the help.

[dbott67]

I posted this for another user, but hopefully it will explain things:

If you want your remote users to use ReadyNAS Remote, a few things need to take place:

1. You need to create a user account on the NAS for them (Frontview > Security > User & Group accounts). This is where the actual security and access to the files on YOUR ReadyNAS is controlled. If they do not have/know a username & password they will not be able to access the files/shares on the NAS (either locally or remotely).
2. You need to install / enable ReadyNAS Remote on the NAS.
3. They need to create a ReadyNAS Remote account.
4. You need to add their ReadyNAS Remote account in Frontview (Frontview > Services > Installed Add-ons > Manage ReadyNAS Remote). If you don't add their ReadyNAS Remote account, they won't even be able to see your NAS when on the ReadyNAS Remote network.
5. They need to install the ReadyNAS Remote client and login. Your NAS will appear and they should be able to access everything just as though they were on your internal LAN.

All of the steps are outlined here:

http://www.readynas.com/?cat=52

The account created in step #1 is different and unrelated to the account created in step #3. For example, suppose I want to give John Smith remote access to my NAS. I create an account in Frontview called 'jsmith' and assign access to whatever shares I want him to have access to.

Then I instruct him to create an account at the ReadyNAS Remote site by sending an e-mail invite & he creates one called 'JohnS123'. To grant him remote access I need to add the JohnS123 account in the ReadyNAS Remote manager section (Frontview > Services > Installed Add-ons > Manage ReadyNAS Remote) and search for his account name ('JohnS123') or search for his email address).

At this point, John can install the ReadyNAS software and attempt to connect to my NAS. He will be prompted to login to the ReadyNAS Remote network (using the 'JohnS123' account). When he tries to connect to my NAS, he will be prompted to enter another username and password. In this case, it will be the username 'jsmith' that I created for him. Now, John can access the shares that I have authorized him to.

I hope this makes sense.

-Dave

[blue_avatar]

Dave, that makes complete sense. Thanks!

[glenm99]

I have done everything I have seen suggested so far with ReadNAS remote. It would appear there are permission issues or bugs in ReadyNas Remote Service.

I have setup a user name and password for the shares and can access them locally on my Lan.

I completed the setup as outlined in the ReadyNAS Remote setup instructions. I can login and I can see the NAS ans shares and when I click on a share it pops up a screen asking for a User name and Password which I put in as if I was on the LAN but it fails and says that I do not have access. I have tried this with several shares and users.

I can not make this stupid thing work except to enable guest access which of course I do not want to do as it has to be secure. But this is crazy, even after triple checking everything. I have multiple NAS devices and I have made this work on Others but my 1100 I can't make work to save my life!!!

I'm going nuts!!


Help? Anyone?

[cap1]

Is this a Vista machine?

If so, can you try:

Can you go to Control Panel ->Administrative Tools->Local Security Policy then under Security settings expand Local Policies->Security Options and change "Network security: LAN Mnager authrentication level" from "Send NTLMv2 response only" to "Send LM and NTLM"

[mchards]

I having what appears to be the same problem accessing shares with guest access disabled.

I'm running the latest NAS side (1.0.9.23) and client side (1.2 beta) software on a Duo with the latest firmware.

I established a share with CIFS and AFP enabled, both with default access disabled and with write access granted to a group with two user members. No guest access for either protocol. This share is accessible on the LAN but not from the WAN using the credentials of either user in the group. The share is not mapped to a drive letter and is not being accessed by any other user. I do have access to the Backup share that has guest access enabled.

For reference, none of the users defined on the NAS, the single remote user, nor any of the machines that I have that access the NAS share any credentials.

I get the dreaded message:

\\5.x.x.x\[share name] is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again..

I seem to have Remote set up OK as I can get to the shares list, I just can't seem to get at any shares that don't have guest access enabled.

Am I missing something?

Update: remote access works fine from a Mac (no common credentials as NAS users) as well as another XP machine (with a common login name as a NAS user but with different passwords). So there is something about the one XP machine that is problematic. Could it be that the two machines that work are not associated with a domain while the one that doesn't is?

[cap1]

Are you accessing from a Vista machine?

can you try the following:

1) Open a dos window and type
net use * /delete

and then try.

If that does not work, please try:


http://www.linux-watch.com/news/NS4434907782.html

Click "Start -> Run." Then, type in the Run field: "secpol.msc." That will bring you to Vista's security policy system. Once there, use "Go to: Local Policies > Security Options" and then find "Network Security: LAN Manager"
authentication level. Once there, change the Setting from "Send NTLMv2 response only" to "Send LM & NTLM -- use NTLMv2 session security if negotiated."

[mchards]

I'm running XP Pro. Tried deleting shares via net use and I'm still getting the same behavior--access to guest enabled shares, not able to authenticate to those without guest access. I opened the secpol management console and found the Network security: LAN Manager policy and it is set to "Send LM & NTLM responses". It doesn't seem like changing that to your suggestion of an optional NTLMv2 would help but I'll try it if you think it will make a difference.

[blakejus]

I am having the exact same issue. I change the Setting from "Send NTLMv2 response only" to "Send LM & NTLM -- use NTLMv2 session security if negotiated.", but this did not improve anything.

Any suggestions?

[mkwap]

Hello.

Has anyone found a fix for this? Is seems a common problem.

Thankyou.

[mchards]

Haven't bothered with this for a while and recently noticed that I couldn't get my Duo to show up in the ReadyNAS Shares list. I installed updates (RAIDiator 4.1.6, Remote server version 1.0.9.25, and Remote client version 1.5) and tried remote access again.

It is worse than before. I don't even get to a list of available shares on the Duo. I only get a message that "The path '\\5.xxx.xxx.xxx' does not exist or is not a directory." I've been through the FAQ and nothing seems pertinent.

Feh.

UPDATE: Found the tip to disable the firewall in the client Properties/Advanced tab and all seems to be working as it should. I'm not sure what the client firewall is for but it certainly gets in the way.

Thanks to the Netgear crew for getting this working.

[sebush61]

Sorry for this... but I can't figure out what the 'client Properties/Advanced tab' is.... where is this dialog box so I can set the option to disable? THanks!

[mchards]

It is the Properties of the ReadyNAS remote client.