Strange behavior with ReadyNAS NV in Windows Domain/AD

[jfucci]

I have a ReadyNAS NV with 4 Seagate 250GB drives in RAID-X configuration. I have downloaded and applied the latest code update (3.01c1-p6). The ReadyNAS is set to use Domain authentication. It has contacted the domain controller and I can see all my users and groups in the ReadyNAS setup. So I created a share, made the default access none, added a specific user with read/write permissions, and the group Domain Admins with read/write permissions. I go to a PC and login as the user, map a drive to the share, and create a folder and some files. I then go to another PC, and login as an administrator, map a drive to the same share, but now I cannot see the folder or files created by the other user. I then create another folder and some files as the administrator, but when I go back to the first PC logged in as the user, I cannot see the files or folder created by the administrator. The whole purpose behind getting a ReadyNAS is to be able to share information, but I cannot share it if I cannot get everyone to be able to see it. Why is it doing this?

[ego1138]

I'm having the exact same problem.

One of my regular users has copied some files and dirs into the share. And I am under the administrative account on my AD.

The user cannot see what the admin put in, and the admin cannot see what the user put in.

HELP!

Thanks

[ego1138]

I think I've figured out the issue.

The share that I created . . . it also had the same name as one of the users who was logging into the network. It looks like the ReadyNAS actually creates two different shares with the same name.

In my case, the share I created was called CMM. I also have a user called CMM. Because the function to allow users to have home directories was also enabled, there was a CMM home folder created. So, the user put everything in there, and I was putting files in the OTHER CMM folder. And neither of us could see what the other was doing.

So, I've renamed MY CMM folder to something else, then I'm having the user move the files there, then I'm disabling home folders.

Hopefully that's the same issue you're seeing and that helps.

[yoh-dah]

Strange -- FrontView should not allow you to create a share with the same name as a user, or vice versa. Were you using the latest RAIDiator 3.01c1-p6 when you created the user and share?

[ego1138]

Yes, everything is up to date.

Remember, I'm in AD mode, so . . . I've not "created" any users - they come from AD. Not sure if that matters, or if that's what you were alluding to or not.

The only other thing to note is that the user is named "cmm", whereas the share I named "CMM".

But either way, when the cmm users browsed to the ReadyNAS' UNC path, he only saw the one share, cmm.

And when I (with a different user account), browsed to the same UNC path, I saw the CMM share, and not his user share.

Let me know if there's anything I can do to help troubleshoot this.

Not a huge deal . . . now that I figured it out, I just renamed my share (and disabled the user shares . . . . because I don't want to use them anyway). But . . . if I can be of assistance to help prevent it from doing that in the future, let me know.

[yoh-dah]

Hmmm, I thought we take care of case, but this might be something we've fixed post p6. Thanks for the follow-up.