similar to: multiple passdb backends for standalone fileserver?

On Mon, 20 Aug 2018 18:02:32 +0200 Harry Jede via samba <samba at lists.samba.org> wrote: > Am Montag, 20. August 2018, 16:43:24 CEST schrieb Matthias Leopold > via samba: > > Hi, > > > > i (naively) would like to have local AND ldap users (and groups...) > > on my standalone fileserver (security = user). "passdb backend = > > ldapsam" already

Hi Rowland, > On Mon, 20 Aug 2018 18:02:32 +0200 > > Harry Jede via samba <samba at lists.samba.org> wrote: > > Am Montag, 20. August 2018, 16:43:24 CEST schrieb Matthias Leopold > > > > via samba: > > > Hi, > > > > > > i (naively) would like to have local AND ldap users (and > > > groups...) > > > on my standalone

Am 2015-09-24 um 20:32 schrieb Marc Muehlfeld: > Hello Matthias, > > Am 23.09.2015 um 10:45 schrieb Matthias Leopold: >> this seems to be a mat{,t}hias discussion ;-) > > oh, sorry. :-) > > > > >> Marc, you said i can have windows ACLs on a standalone server. How do i >> accomplish the >>

Am 11.02.19 um 14:22 schrieb Rowland Penny via samba: > On Mon, 11 Feb 2019 13:46:05 +0100 > Matthias Leopold via samba <samba at lists.samba.org> wrote: > >> >> >> Am 11.02.19 um 13:22 schrieb Rowland Penny via samba: >>> On Mon, 11 Feb 2019 12:30:51 +0100 >>> Matthias Leopold via samba <samba at lists.samba.org> wrote: >>>

Hi, we are using a _single_ LDAP server as backend for _multiple_ Samba standalone file servers (security=user). This LDAP server serves mainly other purposes and access for Samba is read only so the situation is not optimal but "it works for us". Still I don't understand one phenomenon concerning visibility of LDAP groups. The LDAP configuration in smb.conf for all our Samba

Am 11.02.19 um 16:33 schrieb Rowland Penny via samba: > On Mon, 11 Feb 2019 15:40:02 +0100 > Matthias Leopold via samba <samba at lists.samba.org> wrote: > >> >> >> Am 11.02.19 um 14:22 schrieb Rowland Penny via samba: >>> On Mon, 11 Feb 2019 13:46:05 +0100 >>> Matthias Leopold via samba <samba at lists.samba.org> wrote: >>>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, We are discussing removing the capability to chaining passdb backends. It's a decent idea but overly complicates things IMO and unless it has wide spread use, we'll probably axe it soon (voting is starting up on the samba-tecnnical ml now). To give you an example of what I mean, is anyone using something like: passdb backend =

On Mon, 28 Jan 2019 10:09:43 +0100 Matthias Leopold via samba <samba at lists.samba.org> wrote: > I noticed I didn't ask a question ;-) > I noticed that you didn't give us much to work with ;-) Can you post the smb.conf files from the working ldap machine and the non-working 'tdb' machine. Rowland

Hi, I'm building and managing standalone fileservers (security = user) with various passdb backends. I'm noticing different behaviour of Windows ACLs for servers with LDAP and TDB passdb backends. In a LDAP backed server (which I started with) I can freely add filesystem permissions (eg for groups) to objects (files/folders) via the Windows (7) permissions editor. In a TDB backed

Am 11.02.19 um 13:22 schrieb Rowland Penny via samba: > On Mon, 11 Feb 2019 12:30:51 +0100 > Matthias Leopold via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> we are using a _single_ LDAP server as backend for _multiple_ Samba >> standalone file servers (security=user). This LDAP server serves >> mainly other purposes and access for Samba is

Am 2018-02-19 um 17:39 schrieb Rowland Penny via samba: > On Mon, 19 Feb 2018 17:03:31 +0100 > Matthias Leopold via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> i'm trying to setup Samba 4.6 on CentOS 7.4 as a Domain Member of a >> Windows 2012R2 Domain Controller with AD. To administer share >> security i have to use the "username

Hi, i'm trying to setup Samba 4.6 on CentOS 7.4 as a Domain Member of a Windows 2012R2 Domain Controller with AD. To administer share security i have to use the "username map" feature. This works when i enumerate individual AD users there. When i want to use AD groups it only works with "primary" groups. This way i can't use the "Domain Admins" group

Hi, Recently I have installed samba 3.4.8 on my device. Since then ftp (vsftp,proftpd) which is taking users from samba database with pam_smbpass.so is not working. After enabling detailed log I have noticed it is looking for the passwords in smbpasswd (/etc/samba/private) which is of zero size . I think all users passwd are located in passwd.tdb.I could fix this by giving "passdb

Hi Gruss, At this stage there is only one server, running 3.6.25 on Ubuntu12.04. The plan to get LDAP to work on this one. Then add the second server 4.x and the promote it to BDC and then demote this one. Just a side info, we didn't want to go tdbsam in both as I read it breaks the domain trust. The domain names are real ones. I ran the commands you suggested, nothing in reply. I tried

dear list members is it possible to only have the users authenticate against an external ldap server and everything else managed locally on the samba server? the problem is that i only can authenticate against the central ldap but not write to it. this means that samba "root" as well as all machine accounts have to be managed locally and the users' homes information is

Hi Harry, When I install slapd , I didn't get the option to use MDB, so used hdb I went through your suggestions and cleaned up the smb.conf. Also added the unixidpool ldif dn: sambaDomainName=mydomain,dc=mydomain sambaDomainName: mydomain sambaSID: S-1-5-21-3936576374-1604348213-1812434911 sambaAlgorithmicRidBase: 1000 objectClass: sambaDomain objectClass: sambaUnixIdPool

hello the passdb backend no longer accepts multiple backends in a chaining configuration since samba 3.0.23a . question: will the following confi still work? passdb backend = ldapsam://ldapserver1 ldapsam://ldapserver2 ? the idea is to use 2 ldap servers werner Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

I am running Samba ver 3.0.33 on Solaris 10 (sparc.) Initially I had the server configured as a domain controller with the "passdb backend = tdbsam" option. The underlying unix accounts were stored in LDAP (Sun Directory Server.) Those accounts are also used for non-Samba services. Since I have domain trusts with NT domains, I am using winbind and idmapping. The idmap data was

I have Samba and LDAP up and running, but I'm having problems editing the password policy using pdbedit. (I'm running 3.0.22) I've had a look at the man page for pdbedit but I don't really fully understand what it does in relation to passwd backends. Does pdbedit update just one backend and expect a user to export the updates to other backends? I think I've set up ldap as

As some of you may know, I'm trying to set up Samba BDC on a disk- and fan-less tiny mipsel_CPU router running OpenWRT distribution. I already managed to compile Samba 3.0.21a and OpenLDAP 2.3.18 for it, and they seem to work fine. The problem is, this tiny distribution for routers doesn't seem to have anything like Name Service Switch (NSS), and relies solely on /etc/passwd and