similar to: zfsacl problem with share permissions set from Computer Management

> The workaround may be to have the client log out and log back in after > making the changes. :-)  I just tested on a FreeBSD system. The permissions > work as expected once the client establishes a fresh connection. It appears that when a user has SeDiskOperatorPrivilege​ they always have full access regardless of the share permissions. When I attempt access using credentials

On 17/02/16 17:27, Ian wrote: > > On 2/17/2016 5:00 AM, Rowland penny wrote: >> On 17/02/16 00:03, Ian wrote: >>> I've recently attempted to migrate some windows server files over to >>> samba 4 hosted on a FreeNAS server. >>> >>> Using robocopy with the /copyall switch, I expected everything, >>> including ACL's and ownership

On 2/17/2016 9:43 AM, Rowland penny wrote: > On 17/02/16 17:27, Ian wrote: >> >> On 2/17/2016 5:00 AM, Rowland penny wrote: >>> On 17/02/16 00:03, Ian wrote: >>>> I've recently attempted to migrate some windows server files over to >>>> samba 4 hosted on a FreeNAS server. >>>> >>>> Using robocopy with the /copyall switch,

On 2/17/2016 5:00 AM, Rowland penny wrote: > On 17/02/16 00:03, Ian wrote: >> I've recently attempted to migrate some windows server files over to >> samba 4 hosted on a FreeNAS server. >> >> Using robocopy with the /copyall switch, I expected everything, >> including ACL's and ownership information to transfer over. For the >> most part they have.

I'm seeing some really poor performance out of my FreeNAS (ver 9.10) machine, running Samba "4.3.6-GIT-UNKNOWN". I'm using IOMeter to benchmark sequential reads, and getting around 35-40 MB/sec, which seems unusual. Mostly, I'm hoping someone can point me in the direction of a decent tuning guide for a SOHO machine running Samba, but if you're inclined, I'll delve

This is the samba conf file (not on the DC's, but on the box where profiles are being stored - which is where our problem is, IMO) - does anything in here need addressing? [I've slightly sanitized some names.] I'm trying to gather relevant samba logs from this same box, as well as anything that looks relevant from the Windows station event logs. But I thought starting here might be

I'm running Samba 4.7.0 on FreeNAS 11.1-U2. It's configured as an Active Directory Domain Controller, and I'm trying to configure roaming profiles. I've created a profile dataset in ZFS that uses Windows permissions. I've configured the share and file system permissions as described in the "Using Windows ACLs" section of:

I'm trying to learn more about samba by experimenting with samba on FreeNAS. This involves a certain amount of reading how default smb4.conf parameters are set in FreeNAS and then reading the manpages for those parameters. Async I/O is implemented in samba in freenas via the aio_pthread VFS module. The manpage for vfs_aio_pthread states: "the smb.conf parameters aio read size and aio

Looking to see if any one else is having this issue. Running 3.4.5 on solaris 10 with ZFS file system. When I add the vfs objects = zfsacl, Windows clients seem to fine but all my Mac OS X clients can no longer access folders on the share. They can mount the share fine but permissions are not being followed for Mac clients. "The folder "Name" could not be opened because you

I'm not sure if this is an LDAP issue, a Samba issue, a BSD issue or a FreeNAS issue... I'm working at migrating a large block of file shares from an aging CentOS/Samba 3.0.9 server to a FreeNAS (8.0.2) server. (The FreeNAS box is running FreeBSD 8.2-RELEASE-p3 and Samba 3.5.11.) I will eventually be migrating the entire domain and user base off of that server, but for the time being, I

I am looking for where zfsacl settings such as, zfsacl: acesort = dontcare , are documented. Do I need NFS settings such as, nfs4: mode = simple , if I am not using NFS? If I do, where are they documented? Thanks

Hi, When samba is joined to a 2k3 domain, UPN authentication does not work. It works using smbclient, but not from a workstation that is not part of the domain. I can reproduce this easily and provide logs and tcpdump's if necessary. The same problem does not occur when samba is joined to 2k8 or 2k12 domains. Is this by design? Am I missing something? - John -------------- next part

And this is some Samba logs from a connect where the profile isn't handled properly. Near the end, it looks like Samba resets this connection... (I could be wrong - I know nothing about how to read Samba logs.) --- [2019/01/24 10:36:38.097773, 3] ../lib/util/access.c:361(allow_access) Allowed connection from 10.8.20.60 (10.8.20.60) [2019/01/24 10:36:38.097869, 3]

No. If it was mentioned in any of the samba docs consulted, then I missed it. On February 17, 2019 9:43:18 PM EST, Luke Barone via samba <samba at lists.samba.org> wrote: >Did you add the seSecurityPrivilege permission for Domain Admins as >well? > >On Sun, Feb 17, 2019 at 3:13 PM Marco Shmerykowsky via samba < >samba at lists.samba.org> wrote: > >> Can't

Can't figure out what is going on. I define the shares in smb.conf [share] path = /server/share read on = no When I go to "Computer Management" in Windows I can create the share and I can set Share Permissions. However, when I go to the "Security" tab for the share I get "You must have Read permissions to view the properties of this object" I set

Hello, I am unable to change ownership of Samba shares on Windows. It makes no difference if Samba is a PDC or if it is a member server in an Active Directory. I am running Samba 4.1.9 on FreeBSD 9.2 with ZFS. I can easily change ownership locally on the FreeBSD box, however, when trying to do it from Windows it errors out with access is denied. I've attempted to use net rpc rights grant

Perhaps I missed a permission change on the shared directory? It's supposed to be set to 0770, correct? I created the directory from root - can't recall what the permissions where or if I chmod'd it. Would a goof on that result in the inability to set permissions when using the windows administrator account. Basically the behavior I'm seeing? On 2019-02-18 3:36 am, Viktor

Hi Gregory, I see few things, start here : from smb.conf remove : map to guest = Bad User This enabled on a domain member or other domain server is really a no go. This makes debugging really hard. interpret_string_addr_internal: getaddrinfo failed for name > freenas.ad.abc.local (flags 1026) [hostname nor servname > provided, or not known] Looks like there are resolving problems.

Very well. Here is the affected smb.conf. ------ [global] server min protocol = NT1 server max protocol = SMB3 interfaces = 127.0.0.1 10.0.0.8 bind interfaces only = yes encrypt passwords = yes dns proxy = no strict locking = no oplocks = yes deadtime = 15 max log size = 51200 max open files = 2830016 logging = file load printers = no

Hi, I have a FreeNAS server with a cifs share, accessible by all the lan users (guest access) Every one can access it and write in it. When Mac OSX users are creating a file or a folder, they write it with the following permissions : rwxr-xr-x Rhis only happen with mac users. So the other users can't modify or delete theses files/folders. How to configure my share if I want that all the