On Fri, 2013-01-04 at 08:57 +0100, Juan Asensio Sánchez wrote:
Hi
I forgot to explain my scenario... I have one Samba3 test-production
with LDAP backend (it's a test server, but used intensively), so to
make the tests I created a new virtual machine in a separated/isolated
network. This
Hi
2013/1/4 Andrew Bartlett abart...@samba.org
On Fri, 2013-01-04 at 08:57 +0100, Juan Asensio Sánchez wrote:
Hi
I forgot to explain my scenario... I have one Samba3 test-production
with LDAP backend (it's a test server, but used intensively), so to
make the tests I created a new
Hi
I am testing the migration from our actual Samba domain, based on Samba
3.3.8 and LDAP (389DS) to Samba 4. I have followed the Samba4 Howto, and I
have successfully compiled it. Now I am running the classicupgrade command,
but I am getting some errors.
First of them is that the script is
Hi again
Well, finally I got it, adding ldap timeout to smb.conf. Now I am getting
another error when running the domain classicupgrade command of samba-tool:
...
init_sam_from_ldap: Entry found for user:
init_sam_from_ldap: Entry found for user: $
Next rid = 12801001
Failed to
Can you connect to your ldap server locally?
*internal error: NT_STATUS_BAD_NETWORK_NAME
Failed to connect to 'ldap://XXX.XXX.XX' with backend 'ldap': (null)
Could not open ldb connection to ldap://XXX.XXX.XX, the erro*
If not check the ldap.conf, nslcd.conf and the PAM which is
On Thu, 2013-01-03 at 12:52 +0100, Juan Asensio Sánchez wrote:
Hi again
Well, finally I got it, adding ldap timeout to smb.conf.
Good. The 'ldap suffix' is used because while we write new groups under
'ldap group suffix' we always search under 'ldap suffix' for all
objects. That is, it is
Hi
I forgot to explain my scenario... I have one Samba3 test-production with
LDAP backend (it's a test server, but used intensively), so to make the
tests I created a new virtual machine in a separated/isolated network. This
is a clean CentOS 6.3 machine, just installed the compile dependencies
