[Samba] Samba4 binding LDAP Server
walk2sun at arcor.de
Mon Jun 2 13:14:48 MDT 2014
On 20:57:58 wrote steve:
> On Mon, 2014-06-02 at 20:05 +0200, Harry Jede wrote:
> > On 19:41:51 wrote steve:
> > > On Mon, 2014-06-02 at 18:55 +0200, Harry Jede wrote:
> > > > Am Montag, 2. Juni 2014 schrieb Danilo Mussolini:
> > > >
> > > > Two errors:
> > > > 1. The sid from cn=mussolini,ou=groups,dc=o2pos,dc=com does not
> > > > match your sambadomainsid. So this group is never used by your
> > > > samba server.
> > > >
> > > > 2. No groupmapping for group o2pos. This group is ignored by
> > > > samba.
> > > >
> > > > > > > > > Just to remember, this only happens in Samba4.
> > >
> > > Are you sure that this is the same db as you used for samba3?
> > > e.g. before any upgrade?
> > What upgrade? He is using samba in classic mode. No need to upgrade
> > schema.
> Eh? Who said anything about schema?
You are asking about the db. What db?
> > In classic mode one *must* use samba3 schema. AD schema is
> > unknown, no support for rfc2307bis, member/uniqemember just
> > memberuid, and so on...
> How about the supposition that the OP upgraded to Samba4? We use the
> term upgrade to mean moving from one version to another. As Samba 3
> is no longer developed, we consider it an upgrade to move to Samba
> 4. Maybe you do not?
I believe we are meaning the same. Just to clarify:
An upgrade from samba 3.5.x to 3.6.y to 4.1.z is just an update of the
software. In theory nothing has changed, in practice there are a lot of
changes in code and some changes in default settings.
But an upgrade is not a change from "classical samba" to "AD based
More information about the samba