similar to: SID versus user-group name in Property windows

I have a samba server on linux with a LDAP DC, On a client server, I was do net join -S DOMSERV -Uadmin%PASSWORD and that's work The server member of DOMSERV have a share XFS filesystem. When I set manualy the acl (setfacl -m g:group:rwx the_file) It's ok, the other domain member see the ACL But when I set the acl with a Windows Workstation, that's don't work

On Samba 3.0.24, on Solaris 10, I can set ACLs from the command line using setfacl and view them using getfacl. When I look at the security for the mounted share on Windows, I only see the owner, group and world permissions. I can modify those permissions, at least for world. What I can't do is add another user or group to the ACL. I get the error "Unable to save permission changes

On 27/06/16 22:42, Thomas DEBESSE wrote: > Hi, thank your for your answer. > > > Are the 'File servers' joined to the domain ? > Yes > > > Are the smb.conf files you posted complete > No, they are abstracted ones, because they are very long > > > if not, can you post the complete ones, exactly as they are on the > computers (you can sanitize them if

On 27/06/16 21:03, Thomas DEBESSE wrote: > Hi, some months before, I was serving files and profiles using a Samba 3 > PDC server (I will name it PDCSERV), this is some abstracts fro smb.conf: > > PDCSERV:/etc/samba/smb.conf > > [general] > logon path = \\%N\profile > logon drive = U: > logon home = \\%N\%U > logon script =

Hi all, Today our domain went down. When looking in the log it appears that a windowsXPpro machine won the election. The domain controller has an OSlevel of 65 (3.0.14a). Restarting the smb process (/etc/init.d) resolved the problem. How is it possible that the XP machine was able to win the election ? After the election the XP machine (of course) failed to become the master browser. But why

Hi, some months before, I was serving files and profiles using a Samba 3 PDC server (I will name it PDCSERV), this is some abstracts fro smb.conf: PDCSERV:/etc/samba/smb.conf [general] logon path = \\%N\profile logon drive = U: logon home = \\%N\%U logon script = "logon.cmd" valid users = %S [homes] path =

> OK, I think your problem is that you are trying to run your AD domain as if it is still an NT4-style domain. This does not sound like a surprise to me. ;-) > with AD, you would add […] to each users object in AD. You can do this with ADUC or by creating an ldif file on the DC and then use ldbmodify to add it. Oh, yes, you're right, I had to do the same for the logon.cmd, I already

Hi, thank your for your answer. > Are the 'File servers' joined to the domain ? Yes > Are the smb.conf files you posted complete No, they are abstracted ones, because they are very long > if not, can you post the complete ones, exactly as they are on the computers (you can sanitize them if you need to) Yes > Try taking a look here:

At the suggestion of Stas, I'm starting a new thread on this one. This pretty much covers where I'm at right now: Doug, thanks, here's a complete listing of the config file, and some logging, hopefully this will be illuminating to somebody. > Neither of these lines set the log level. Yes, I've been setting it in the init script. When I do ps -ef | grep smbd, I see that

I have samba server joined to a domain that I'm trying to use ads security and acls on. I can set acls on the Unix file system, and access from a windows client seems to honor them. I can't view the acls under the security tab, all I see are the standard Unix permissions instead. If I try to add an entry to the acl, I get an access denied error, even if the user is on the list of admin

Hi, Just wondering when one would use "include" over "extend"? Both seem to bring in methods to the class no? The context is I''m just trying to understand why both are used with the acts_as_audited plugin: Full extract from plugin (used within here): ================================================== # Copyright (c) 2006 Brandon Keepers # # Permission is hereby

Hi!! I'm not able to change a user password on a workstation and with smbpasswd when I'm log. ex: [usertest@pc070 usertest]$ smbpasswd Old SMB password: New SMB password: Retype new SMB password: machine 127.0.0.1 rejected the password change: Error was : RAP86: The specified password is invalid. Failed to change password for usertest so when I'm root, that's work The log