Dataset permissions not working like they should

[bryce]

So, I've got 5 datasets and I got this to work last night just messing around but today the permissions do not want to work. What am I doing wrong with them.

My datasets are media, backups, temporary, documents, jails.

I have one user/group and one group for my jails, etc.

I have setup CIFS shares for each dataset minus the jails dataset. I have made the owner my user and the owner group my group (shareusers). I have made sure my user is in the shareusers group .

I've looked through the freenas wiki/docs and I seem to be setting up the permissions/shares correctly, I just don't understand why it's not allowing my user to login to the shares.

User: bryce, Group: bryce Group: shareusers

bryce is a member of bryce, shareusers, wheel

All the datasets are owned by bryce:shareusers with the exception of the jail dataset, that's owned by root:wheel.

I was doing it this way to give the plugin jails access to my data dataset (sab/sonarr) with the group shareusers.

But I'm unable to access any of the shares from my windows box, it keeps giving me an access denied message. I've even tried setting allow guest access to the shares and it still gives me access denied messages.


So, fresh install, still getting the same issue. Permissions are set correct that I know of and yet I have no access to my shares.

Here's some images of how I have permissions set on one of the datasets.

http://imgur.com/a/Cts1l

I have tried using windows permissions as well and same thing, access denied. Allow guest access isn't working either.


Ok, so fresh install completed. I go to make my volume, setup the ups, etc. And in the log section I have this. Should I be getting these errors on a complete fresh install of the system?

http://pastie.org/10939665

 

[pasiz]

Have you applied permissions recursively (checkbox is not set in your picture).

 

[bryce]

I thought the apply recursively was if I already had files/folders in that dataset. This is a brand new install/volume with nothing on the datasets at all. So would checking recursively really do anything? I mean I'm going to try it just to be sure, but yeah.

It seems everything I try and change a setting on a dataset and just randomly I get the following errors. Could that be related to the permissions not working for me? Not sure why this would happen after a fresh install and fresh volume made. These are the errors I get:

Code:

Oct  8 04:10:44 loki mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801407180 124.1.168.192.in-addr.arpa. (PTR) that's already in the list
Oct  8 04:11:02 loki manage.py: [common.pipesubr:66] Popen()ing: zfs list -H -o mountpoint,name
Oct  8 04:11:04 loki manage.py: [common.pipesubr:66] Popen()ing: zfs list -H -o mountpoint,name
Oct  8 04:11:05 loki generate_smb4_conf.py: [common.pipesubr:66] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Oct  8 04:11:05 loki generate_smb4_conf.py: [common.pipesubr:66] Popen()ing: mount
Oct  8 04:11:05 loki generate_smb4_conf.py: [common.pipesubr:66] Popen()ing: /usr/local/bin/net -d 0 getlocalsid
Oct  8 04:11:05 loki notifier: Performing sanity check on Samba configuration: OK
Oct  8 04:11:05 loki notifier: Reloading nmbd.
Oct  8 04:11:05 loki notifier: Reloading smbd.
Oct  8 04:11:05 loki notifier: Reloading winbindd.
Oct  8 04:11:05 loki notifier: Stopping mdnsd.
Oct  8 04:11:06 loki mDNSResponder: mDNSResponder (Engineering Build) (Oct  3 2016 06:58:50) stopping
Oct  8 04:11:06 loki mDNSResponder: mDNS_FinalExit failed to send goodbye for: 0000000801483580 01   23 _http._tcp.local. PTR loki._http._tcp.local.
Oct  8 04:11:06 loki notifier: Waiting for PIDS: 45295.
Oct  8 04:11:06 loki notifier: Starting mdnsd.
Oct  8 04:11:06 loki mDNSResponder: mDNSResponder (Engineering Build) (Oct  3 2016 06:58:50) starting
Oct  8 04:11:06 loki mDNSResponder:  10: Listening for incoming Unix Domain Socket client requests
Oct  8 04:11:06 loki mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Oct  8 04:11:06 loki mDNSResponder: CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for PCP & NAT-PMP announcements
Oct  8 04:11:07 loki mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801406D60 loki.local. (Addr) that's already in the list
Oct  8 04:11:07 loki mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801407180 124.1.168.192.in-addr.arpa. (PTR) that's already in the list

 

[pasiz]

What version you are running. Based on errors i assume 9.10. mDNSResponder is so noisy. Try updating your system to get rid of those.

 

[bryce]

Yes, 9.10. And I tried checking the recursive box and does nothing. I just don't get what I could be doing wrong, everything permission wise seems fine and is exactly how I had it setup before and it was working fine.

Just updated so I'll see if it fixes any of those errors. Still baffling why the permissions aren't working when they clearly were prior to the reinstall =/.

Yeah, the update did not fix any of those errors.

 

[pasiz]

Could you post your smb config?

 

[bryce]

Where is the smb config stored at?

 

[KennethW]

Where is the smb config stored at?

You will find it in /usr/local/etc

 

[bryce]

Ok, having a dumb moment. The shell isn't allowing me to copy/paste from the freenas webgui.

 

[bryce]

Ok, I just don't understand why I had this working prior to the reinstall using the exact same settings on the datasets and shares. I also didn't have any of those mdns messages spamming the log and what not.

 

[pasiz]

smb config maybe?

 

[bryce]

I don't why or how it started working, but it's working now...

 

[m0nkey_]

See my Samba how-to video in my signature.