Bug 2384 - joining domain often fails when LDAP master not local
joining domain often fails when LDAP master not local
Product: Samba 3.0
Classification: Unclassified
Component: smbldap-tools
All Linux
: P3 normal
: none
Assigned To: Tournier Jerome
smbldap-tools team
Depends on:
  Show dependency treegraph
Reported: 2005-02-23 00:22 UTC by Tomasz Chmielewski
Modified: 2005-08-24 10:17 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Chmielewski 2005-02-23 00:22:26 UTC
I have a setup like that:

Samba PDC + Master OpenLDAP <-> WAN/VPN <-> Samba BDCs + Slave OpenLDAPs +
workstations (different branch offices)

Because Master/PDC and Slaves/BDCs are connected through the internet, sometimes
joining a workstation to a domain is impossible, (workstation is in the same net
as a BDC).

Here is a possible workaround as suggested in this thread (read the whole thread
to get an idea what happens):


So adding something like this (sleep) to smbldap_tools.pm, around line 380 (it
is smbldap-tools-0.85) helps:

        $add->code && warn "failed to add entry: ", $add->error ;
        # take down the session
        return 1;
Comment 1 Tournier Jerome 2005-02-26 04:13:37 UTC
There's now a new option -t to smbldap-useradd to set a time to wait before
exiting the script. This option has no effect when using without the -w option
(ie can only be used when adding a computer account).
The Samba smb.conf configuration file should then look like this :
add machine script = /opt/IDEALX/sbin/smbldap-useradd -t 30 -w "%u"
(I set a time parameter because lots of architecture does not have a BDC. And
the PDC does not need to wait 30s).
Comment 2 Gerald (Jerry) Carter 2005-08-24 10:17:59 UTC
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.