similar to: Administrator can no longer connect to member server after removing uidnumber from administrator

On 27/02/15 19:09, Shane Robinson wrote: > Hello again List, Marc, and Louis! > > I'm afraid my message from yesterday may have been TL;DR. The short version > is as follows: > > Following the wiki's for AD member server (building from source on Debian > Wheezy) and Setting up shares with Windows acls did not give the expected > results > > First, I needed to

Hello again List, Marc, and Louis! I'm afraid my message from yesterday may have been TL;DR. The short version is as follows: Following the wiki's for AD member server (building from source on Debian Wheezy) and Setting up shares with Windows acls did not give the expected results First, I needed to link libnss_winbind.so to /usr/lib/x86_64-linux-gnu for winbind to work. Marc - may I

On 27/02/15 19:46, Shane Robinson wrote: > Hello all, > > Sorry about the top-posting. > > I have added the bit about the linking (YAY!, I'm helping!). > > Now if we can clear up the ACL issue, this will be a great day! > > Summary: To edit ACL's from Windows on a Debian Member server, we need to > either > 1) map the domain admin to root OR > 2) give

On 27/02/15 20:07, Shane Robinson wrote: > Hi Rowland, > > Chown to Administrator seems less flexible than Chgrp to Domain Admins on > the face of it. You could add/remove users from the Domain Admins group, > which allows/denies them the ability to change the permissions on the share. > By changing the owner to Administrator, only those credentials would have > that ability,

Hello all, Sorry about the top-posting. I have added the bit about the linking (YAY!, I'm helping!). Now if we can clear up the ACL issue, this will be a great day! Summary: To edit ACL's from Windows on a Debian Member server, we need to either 1) map the domain admin to root OR 2) give explicit permissions to Domain Admins with a chmod 0755 and chgrp "MYDOM\Domain Admins"

On 27/02/15 21:00, Shane Robinson wrote: > Hi Rowland, > > I'm also not an expert, but with the amount of help you provide on the list, > I will defer to you. > > I'd love to know your rational for prefering the "change ownership to > administrator" approach over the "change group to Domain Admins approach". > If it's just gut, that's

Hi Rowland, Chown to Administrator seems less flexible than Chgrp to Domain Admins on the face of it. You could add/remove users from the Domain Admins group, which allows/denies them the ability to change the permissions on the share. By changing the owner to Administrator, only those credentials would have that ability, no? What advantages do you predict with the change owner approach? What

Hello again Rowland, list! Sorry for the delayed response, and top posting. To recap: I'd like to complete the member server wiki so that ACLs can be set from windows without taking undocumented steps. The three ways I've found to do this are: 1) map root to administrator. (LPH VanBelle's script uses this option.) 2) chmod 0775 then chgrp "<DOMAIN>\Domain Admins"

Hi Rowland, I'm also not an expert, but with the amount of help you provide on the list, I will defer to you. I'd love to know your rational for prefering the "change ownership to administrator" approach over the "change group to Domain Admins approach". If it's just gut, that's fine too! Thanks! -----Original Message----- From: samba-bounces at

Hello List! I have a Samba AD domain with two virtualized DC's running 4.1.15 and 4.1.17. I have had two member file servers with odd permissions problems that I've now given up on, and decided to start fresh. I have created a File server (FS3) with Debian wheezy, built samba 4.1.17 from source, with configure options of : --with-ads --with-shared-modules=idmap_ad ... and placed the

Forgot to add the list in the TO line! Shane Robinson Chief Administrative Officer SimpeQ Care Inc. t. 604.988.3103 ext. 104 c. 604.506.3311 f. 604.988.3105 Please consider the environment before printing this email. -----Original Message----- From: Shane Robinson [mailto:srobinson at simpeq.ca] Sent: Wednesday, March 04, 2015 12:32 PM To: 'Rowland Penny' Subject: RE: [Samba] Domain

Hello list! I have a newish Samba 4.1.4 (from git) AD DC running in an Ubuntu Precise KVM guest. It seems to be running well. Recent list posts have led me to set up a second instance of samba/ubuntu as a file server. Like the domain controller, Samba was built from git, but then it was configured using the "Samba/Domain Member" wiki. I added the sfu attributes to a few users/groups

2015-03-04 21:35 GMT+01:00 Shane Robinson <srobinson at simpeq.ca>: > Hi Davor, > > If the mapping of administrator to root is not ideal, I do like the idea of > having a specific FileShareAdmin group. > > But, why chown and not simply chgrp? > If you consider 'root' as a BUILTIN\Administrator equivivalent it might work changing both Share and DACL "the

Hi Davor, If the mapping of administrator to root is not ideal, I do like the idea of having a specific FileShareAdmin group. But, why chown and not simply chgrp? Thanks! Shane Robinson Chief Administrative Officer SimpeQ Care Inc. t. 604.988.3103 ext. 104 c. 604.506.3311 f. 604.988.3105 Please consider the environment before printing this email. -----Original Message----- From:

Hello Rowland, Oh dear! I do feel rather silly. :/ Thanks so much for your patience! I think I'll clarify the wiki (which does mention this, but only mentions the local administrator). When I read it, it mentions that there will be mapping for non-domain accounts in TDB. I (quite wrongly) assumed that my domain administrator was not included in this, and, therefore, would need a UIDnumber

Will I really HAVE to use the idmap backends AD or RID? I was planning to use TDB2 with a script which I've already written: [root at fs3 samba]# ./idmap.sh IDTOSID UID 1301 SID:S-1-5-21-1632654815-303659134-1628659390-1950 [root at fs3 samba]# ./idmap.sh IDTOSID GID 198 SID:S-1-5-21-1632654815-303659134-1628659390-3247 [root at fs3 samba]# ./idmap.sh SIDTOID

Hi samba team ! I try to resolve for hours a problem I have with a Linux Host (Samba 4.3.9 ubutnu 16.04) as AD member.DCs are Windows 2008 R2, One is 2012 R2. Forest level is 2003 R2. my smb.conf : [GLOBAL] netbios name = CR-DEV-01 security = ADS workgroup = ADDOMAIN realm = ADDOMAIN.COM idmap config *:backend = tdb idmap config *:range =

On 04/07/16 18:35, Raphaël RIGNIER wrote: > Hi samba team ! > > I try to resolve for hours a problem I have with a Linux Host (Samba > 4.3.9 ubutnu 16.04) as AD member.DCs are Windows 2008 R2, One is 2012 > R2. Forest level is 2003 R2. > > my smb.conf : > [GLOBAL] > netbios name = CR-DEV-01 > security = ADS > workgroup = ADDOMAIN >

Hello, I have more info on my specific problem. pop 1) RedHat 7.3, fs1 fs3 pop 2) BSD/OS 4.3.1 www files rsync version 2.6.0 protocol version 27 fs1 --> fs3 500kB/s fs1 <-- fs3 420kB/s fs1 --> www 20kB/s fs1 <-- www 20kB/s files --> www 2.9 MB/s files <-- www 4,4 Mb/s This shows that within their own networks, there is no problem. It is only

On 10/11/15 13:42, mathias dufresne wrote: > Thank you for this quick answer Louis. > > On DC: > > On DC I had to add one line to have winbind retrieving uidNumber AD field > rather than having Winbind chosing some random UID for my users. > This line is: > > idmap_ldb:use rfc2307 = yes > > as explained in https://wiki.samba.org/index.php/Setting_up_RFC2307_in_AD