ns stored. With
ldap filter = (&(sambaDomainName=)(uid=%u))
we make these samba-servers work without a problem. But if we can't filter
username, SID's and groupname are not proper seperated.
Met vriendelijke groet/Regards
Prompt
R.J. Baart
Kerkstraat 173
5261CW Vught
tel: +31 73 65
I've read that the sm.conf configuration option "ldap filter" is removed after
3.0.14. Why is that? For one of the networks we maintain it is a very crucial
option. I could not found an explanation or work around.
Met vriendelijke groet/Regards
Prompt
R.J. Baart
Kerkstraat 1
I've read that the sm.conf configuration option "ldap filter" is removed after
3.0.14. Why is that? For one of the networks we maintain it is a very crucial
option. I could not found an explanation or work around.
Met vriendelijke groet/Regards
Prompt
R.J. Baart
Kerkstraat 1
There is no need to edit in pam.d directory.
1. /etc/security/pam_unix2.conf must contain:
auth: use_ldap nullok
account: use_ldap
password: use_ldap nullok
session: none
2. /etc/nsswitch.conf:
passwd: files ldap
group: files ldap
shadow: files ldap
But read for the serious problems we had
failure as a network failure: the client can't
communicate with the SMB server within a reasonable time. It this correct
and are there other reasons why this error may occur?
Met vriendelijke groet/Regards
Prompt
R.J. Baart
Marktveldpassage 35c
5261ED Vught
tel: +31 73 6567041
mailto:[
other reasons why this error may occur?
Met vriendelijke groet/Regards
Prompt
R.J. Baart
Marktveldpassage 35c
5261ED Vught
tel: +31 73 6567041
mailto:[EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba