search for: msg113387

...again .. Is > ldbedit safe to use: > > - on a running Samba server (or do I need to stop samba) > - in a multi-DC environment (or do I need to run it and make the same > changes on each DC) > Answering my own question here... it would appear not: http://www.spinics.net/lists/samba/msg113387.html So, I'm now not certain what the "correct" way to fix this is. I don't think I can use ldapmodify, as none of the users (me!) who should have access via LDAP actually do have access, so the AD side of things would just reject the modify request. I did deliberately remove th...

...to use: >> >> - on a running Samba server (or do I need to stop samba) >> - in a multi-DC environment (or do I need to run it and make the same >> changes on each DC) >> > Answering my own question here... it would appear not: > http://www.spinics.net/lists/samba/msg113387.html > > So, I'm now not certain what the "correct" way to fix this is. > > I don't think I can use ldapmodify, as none of the users (me!) who should > have access via LDAP actually do have access, so the AD side of things > would just reject the modify request....

On 04/01/16 23:26, Jonathan Hunter wrote: > The story gets deeper, also.. (nothing is ever easy, right? :-)) > > Using the ldbsearch command above, I could at least view the SIDs that have > access to the OU. > > One of them should be a group called "mysecretou Managers"; I can see from > ADUC that my user is indeed still a member of this group (so far, so good).