Completely baffled by setting up shares for users

I don't know if I'm just a complete idiot or if OMV is. It can't be this hard....

All I want to do have is have multiple shared SMB folders....and be able to configure each folder's access rights (read-only, read-write) based on user accounts.

I've been looking over a bunch of online/YT instructions for how this is supposed to be setup, but nothing seems to work.

Existing Windows computer user (name:pass on the windows computer) (on the same Workgroup)

OMV

- Create user account with name:pass to match Windows user

- Existing shared folder in OMV -> Privileges -> Set r/w permission for Windows user

-

SMB

- Shares -> Add shared folder from above

- Shares -> Shared folder - Public -> No

Anything else?

At this point, when attempting to access the folder, I am prompted for the password (user name is already pre-populated). I enter the password and am met with the message:

\\OMV is not accessible. You might not have permissions to use this network. Blah, blah, blah.

Double-checked, and yes, the user settings under Shared Folders ->Privileges is set for r/w access and if I go into the Shared folder -> ACL (in the upper half), I see the user account also configured with r/w access. So they match.

In the UNIX file/folder perms in the lower half though ("Extra Options" section), how do I configure/add this user? The only thing I can see to do there is to change the owner/group/others configuration.

Zitat von HannesJo

I also never had any problem here but heard about some several times. Also good thing to keep things simple as possible. Anyway the main problem here seem to be he just doesn’t tell us all the settings he made.

Admittedly, I've probably changed some things that don't need to be changed (or maybe shouldn't even be changed) while trying to sort this out.

If I can possibly create even a single working 'example' though, I can replicate the settings and go from there.

gderf No, never have seen that message while trying to get this to work.

It seems like I earlier ran across a post that had something about installing a plugin that would essentially reset all of the perms/ACLs/etc back to default. Is that something I could use here? I'd be MORE than happy to reset all of that stuff back to default and have someone show me how to correctly set things up for 1 remote user and 1 shared folder (the use-case I specified in the first post).

gderf Yes, you are correct. I was imagining that message happening somewhere else. Just to confirm, I did into a shared folder and into the Privileges section and I do see the EXACT same message you posted.

so this is saying....the configurations set there in the privileges section are used by, in my case, SMB to setup the access rights for -users-...and don't cause any changes to the file system's permissions for the actual content existing within the shared folder, correct?

Is this saying that if I assign r/w privileges to a shared folder that this simply gives the SMB service r/w access to the shared folder....and has nothing to do with whether or not a specific user has r/w or ro access to the share?

Zitat von crashtest

Maybe this might help -> Permissions.

I hadn't run across this (somehow), but a quick scroll through it looks like this will be VERY helpful. MUCH appreciated!

Okay...making some SLOW progress here.

Something odd that I've now run across though.

On the remote client (with user:pass that exist in OMV), if I browse the network (explorer window), I see the OMV service (icon for my OMV) show up. If I click on it, I'm then prompted to "Enter your Network Credentials". My understanding now is that this shouldn't happen (if things are working and setup correctly with matching account credentials on both ends). If I go ahead and enter what is the correct pw though, I get the message that started this thread, "\\OMV is not accessible...blah, blah, blah".

BUT......if I go to a run prompt and simply enter \\OMV, I'm then presented with an explorer window listing all of the network shares I have setup...and I can access them.

So, what is happening here?

Correct...none of the SMB shares have any ACL boxes ticked. (Installed reset plugin earlier and reset all the shares)

The remote client is a Win10 client.

Thanks for the link to that doc. Hadn't run across that one either.

I have no problems when setting up a shortcut on the Win10 remote client. Works perfectly....but still doesn't change the previously described behavior where if I select the OMV network icon discovered in an explorer window, it then prompts me for a password...which doesn't even work if entered. This isn't a show-stopper though - just wondering why the Win10 client is behaving like this (wondering if maybe there's something not setup quite right).