I had the same problem, and it turned out I had made a silly mistake in my /etc/smbldap-tools/smbldap_bind.conf file. The password was correct, but the DN entries started with "dc=admin, ..." instead of "cn=admin, ...".
In the end, what helped me find the problem was to add the "stats" loglevel to the slapd config. This showed the following in the logs: Feb 2 11:50:27 lenny1 slapd[5502]: conn=150 op=0 BIND dn="dc=admin,dc=example,dc=com" method=128 Feb 2 11:50:27 lenny1 slapd[5502]: conn=150 op=0 RESULT tag=97 err=49 text= After this error, the smbldap-useradd continued and failed with the next error. If it had stopped right there, it would have been much easier to find the problem. So in my case, I believe the bug would be that smbldap-useradd continues after failing to bind as admin, and then reports a misleading error at the next step. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680177 Title: smbldap-useradd fails to authenticate to allow changes to LDAP server -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
