To which samba version does the samba schema adhere?
On Fri, May 9, 2008 at 2:32 PM, Pierre Smits <[EMAIL PROTECTED]> wrote: > Reinstall the server, set m-disabled for nis to FALSE and then set > m-disabled for samba to FALSE did the trick. Samba objects classes are now > available. > > Thanks. > > > > On Fri, May 9, 2008 at 2:25 PM, Pierre Smits <[EMAIL PROTECTED]> > wrote: > >> I see that nis (which is has m-oid= 1.3.6.1.1.1.1.0) has m-disabled = >> true, but see no way to change te value. >> >> Do you know how I could go about it? >> >> >> On Fri, May 9, 2008 at 11:16 AM, Jeroen Vriesman <[EMAIL PROTECTED]> >> wrote: >> >>> Hi, >>> >>> maybe the schema defining attribute type 1.3.6.1.1.1.1.0 is disabled? >>> >>> Looking at the samba schema I see: >>> m-dependencies: system >>> m-dependencies: core >>> m-dependencies: inetorgperson >>> m-dependencies: nis >>> >>> did you also set m-disabled=FALSE in inetorgperson and nis? >>> >>> On Fri, May 9, 2008 at 11:09 AM, Pierre Smits <[EMAIL PROTECTED]> >>> wrote: >>> >>> > The verion I am using is apacheds 1.5.2 with jvm 1.5. >>> > >>> > It happened both on the linux and the windows version. >>> > >>> > On Thu, May 8, 2008 at 11:40 PM, Alex Karasulu <[EMAIL PROTECTED]> >>> > wrote: >>> > >>> > > Give me some information to go on: platform, jvm, and ApacheDS >>> version. >>> > > Also turn on debugging after clearing out the log file and send it >>> over. >>> > > >>> > > Alex >>> > > >>> > > On Thu, May 8, 2008 at 11:19 AM, Pierre Smits < >>> [EMAIL PROTECTED]> >>> > > wrote: >>> > > >>> > > > When enabling the samba schema via above mentioned method and >>> > restarting >>> > > > the >>> > > > server again, I get following error message: >>> > > > >>> > > > >>> > > > Error while opening connection >>> > > > [LDAP: error code 80 - failed on search operation: attributeType w/ >>> OID >>> > > > 1.3.6.1.1.1.1.0 not registered!] >>> > > > [LDAP: error code 80 - failed on search operation: attributeType >>> w/ >>> > OID >>> > > > 1.3.6.1.1.1.1.0 not registered!] >>> > > > Error occurred while loading schema, using default schema >>> > > > >>> > > > How do I correct this? >>> > > > >>> > > > Regards, >>> > > > >>> > > > Pierre >>> > > > >>> > > > >>> > > > On Thu, May 8, 2008 at 3:28 PM, Jeroen Vriesman < >>> > [EMAIL PROTECTED] >>> > > > >>> > > > wrote: >>> > > > >>> > > > > I had the same problem some time ago, >>> > > > > >>> > > > > under cn=admin,ou=shema you can see that "m-disabled" is TRUE, >>> set it >>> > > to >>> > > > > FALSE >>> > > > > >>> > > > > >>> > > > > By the way, another question for the rest of us, is there an easy >>> way >>> > > to >>> > > > > convert the openldap schema's to apachds (is it enough to convert >>> > them >>> > > > and >>> > > > > add them under ou=schema?) >>> > > > > >>> > > > > what I want is to take the file of an openldap schema and just >>> > ldap-add >>> > > > > some >>> > > > > converted stuff to apache on the commandline, is there such a >>> > > converter? >>> > > > > >>> > > > > >>> > > > > >>> > > > > On Thu, May 8, 2008 at 3:20 PM, Pierre Smits < >>> [EMAIL PROTECTED] >>> > > >>> > > > > wrote: >>> > > > > >>> > > > > > I am testing the 1.5.2 windows version. >>> > > > > > >>> > > > > > When accessing the running ds service with apache studio I see >>> the >>> > > > samba >>> > > > > > schema. However, when creating new entries I cannot select >>> samba >>> > > > objects. >>> > > > > > >>> > > > > > How do I make the samba schema available in the list of >>> selectable >>> > > > > > objects? >>> > > > > > Do I need to configure something? >>> > > > > > >>> > > > > > >>> > > > > > Regards, >>> > > > > > >>> > > > > > Pierre >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >>> >> >> >
