Uff.
I finally found the solution to this problem.
It's quite simple:
Use the correct samba.schema for the corresponding sambarelease!
(/samba-x.x.x/examples/LDAP/samba.schema)
There are some changes to the LDAP-schema so that this is absolutely
essential for "net rpc trustdom establish" to work as you can see here:
-->
Aug 15 13:07:17 debiantest slapd[2346]: conn=67 op=3 SRCH
base="sambaDomainName=
PRESSNG,sambaDomainName=TESTDOMAIN,dc=pressol,dc=com" scope=2 deref=0
filter="(&
(?objectClass=sambaTrustedDomainPassword)(sambaDomainName=pressng))"
Aug 15 13:07:17 debiantest slapd[2346]: conn=67 op=3 SEARCH RESULT tag=101
err=3
2 nentries=0 text=value does not conform to assertion syntax
Aug 15 13:07:17 debiantest slapd[2346]: conn=67 op=4 ADD
dn="sambaDomainName=PRE
SSNG,sambaDomainName=TESTDOMAIN,dc=pressol,dc=com"
Aug 15 13:07:17 debiantest slapd[2346]: conn=67 op=4 RESULT tag=105 err=21
text=
objectClass: value #0 invalid per syntax
<--
Before I think the interdomain trust information was completely
safed in secret.tdb
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
