]
Sent: Wednesday, November 25, 2009 10:01 PM
To: samba@lists.samba.org
Subject: RE: [Samba] samba 3.4.3 DC breaks Windows groups
I have done the following
- Added index for sambaSID and other attributes as per the following
http://wiki.samba.org/index.php/2.0:_Configuring_LDAP
I added the index. (The Sun DS Admin guide has pretty simple
instructions on doing this.)
I also added some additional indexes as per the following
http://wiki.samba.org/index.php/2.0:_Configuring_LDAP
Unfortunately did not resolve the problem.
It does look like I have the 3.0 schema
I have done the following
- Added index for sambaSID and other attributes as per the following
http://wiki.samba.org/index.php/2.0:_Configuring_LDAP
- replaced the samba 3.0 schema file in my LDAP Server (Sun Directory
Server) with the 3.2 version
- installed samba 3.4.3
...@gmail.com]
Sent: Wednesday, November 25, 2009 10:01 PM
To: samba@lists.samba.org
Subject: RE: [Samba] samba 3.4.3 DC breaks Windows groups
I have done the following
- Added index for sambaSID and other attributes as per the following
http://wiki.samba.org/index.php/2.0
I assume an index is not an actual LDAP attribute or object like
sambaSID but is more like a database index for optimizing searches?
I use Sun's Directory Server (LDAP server) as the backend. I use Apache
Directory Studio for managing objects and attributes with in ldap.I
should be able
I have the following setup:
PDC: Samba 3.0.37 on Solaris 10
BDC1: Samba 3.0.37 on Solaris 10
BDC2: Samba 3.4.3 on Solaris 10
Samba 3.0.37 is the bundled version of Samba.
Samba 3.4.3 is compiled from source.
BDC2 is a recent addition to the network.
All machine use LDAP as the
On the assumption that Unix systems (solaris and linux) will not like spaces
in names, I never created unix groups called Domain Admins and Domain
Users etc. Instead I had created smb_domadmins and smb_domusers etc
instead.
I don't know if Windows systems actually pay attention to the name
