search for: 45999

...ldap idmap config DOMAIN_B:readonly = no idmap config DOMAIN_B:default=no idmap config DOMAIN_B:ldap_base_dn = ou=domain_b,ou=idmap,o=mydomain.com idmap config DOMAIN_B:ldap_user_dn = cn=Directory Manager idmap config DOMAIN_B:ldap_url = lldap://ldap1.domain.com idmap config DOMAIN_B:range = 40000-45999 .... ---------------------------------------------------------------------------------------------------------------------------- Domain_A (Windows 2003 AD in Mixed mode) has entries from prior to the upgrade and hasn't had new accounts added recently. Domain_B (Windows 2008 in Windows 20...

...ldap idmap config DOMAIN_B:readonly = no idmap config DOMAIN_B:default=no idmap config DOMAIN_B:ldap_base_dn = ou=domain_b,ou=idmap,o=mydomain.com idmap config DOMAIN_B:ldap_user_dn = cn=Directory Manager idmap config DOMAIN_B:ldap_url = lldap://ldap1.domain.com idmap config DOMAIN_B:range = 40000-45999 .... ---------------------------------------------------------------------------------------------------------------------------- Domain_A (Windows 2003 AD in Mixed mode) has entries from prior to the upgrade and hasn't had new accounts added recently. Domain_B (Windows 2008 in Windows...

Hi, I have recently upgraded a system with a Samba BDC, PDC and a couple of member servers from 3.2.14 to 3.4.9 (and also tested with 3.5.6). There appears to be some problem with Winbind (we need to run it on all servers as we have a trust relationship to a domain at another office). I have an Idmap range set up in our LDAP database. With 3.2.14, all worked well. The Idmap ou would be