Hi, there!
When my XP users try to change passwords, they get a message saying that
password has been changed. That's not true!
NT and LM passwords are changed but unixPassword isn't.
Look at this openldap.log lines:
Feb 12 07:50:28 apolo slapd[22826]: conn=698021 op=40 MOD
Jerome Tournier escreveu:
I tried on CentOS release 4.6 (Final)
samba-3.0.25b-1.el4_6.4
openldap-servers-2.2.13-8.el4_6.2
smbldap-tools-0.9.5-pre4 (but changing password work with latest
packages)
I'm using FreeBSD 6.3 in both samba and openldap servers, Samba 3.0.26a and
openldap 2.3.38. Not
Le Thu, Feb 14, 2008 at 09:33:49AM +0100, Jerome Tournier a ecrit:
Le Wed, Feb 13, 2008 at 11:25:41PM -0200, Fabiano Caixeta Duarte a ecrit:
Have you try 'access to * by * write' in slapd.conf (don't think it come
from here as passwords are changed, but maybe users don't have write access
to
Le Wed, Feb 13, 2008 at 11:25:41PM -0200, Fabiano Caixeta Duarte a ecrit:
I assume that your ldap sync passwd is enough (like I wanted to) because
smb.conf tells us that passwd chat is not used if unix password sync is set
to no.
passwd chat (G)
Note that this parameter only is only
hi Fabiano,
hi Edmundo,
the second problem here (user has no permission) when using an
external passwd program sounds familiar to me:
Sure enough smbldap-passwd works. I have tried this once ldap passwd
sync was not working. Though, there are two problems: 1) it's too slow
and 2) it
Edmundo Valle Neto escreveu:
Fabiano Caixeta Duarte escreveu:
Fabiano Caixeta Duarte wrote:
Hi, there!
When my XP users try to change passwords, they get a message saying
that
password has been changed. That's not true!
NT and LM passwords are changed but unixPassword isn't.
Look at this
Le Tue, Feb 12, 2008 at 09:44:01AM -0200, Fabiano Caixeta Duarte a ecrit:
Hi, there!
When my XP users try to change passwords, they get a message saying that
password has been changed. That's not true!
I can confirmed you that the following configuration work for me:
unix password sync = No
(...)
Sure enough smbldap-passwd works. I have tried this once ldap passwd
sync was not working.
How?
Though, there are two problems: 1) it's too slow and 2) it shows a
message to the user telling he has no permissions to change password.
Where? How?
So it's confusing. I don't feel
Jerome Tournier escreveu:
Le Tue, Feb 12, 2008 at 09:44:01AM -0200, Fabiano Caixeta Duarte a ecrit:
Hi, there!
When my XP users try to change passwords, they get a message saying that
password has been changed. That's not true!
I can confirmed you that the following configuration work for me:
Fabiano Caixeta Duarte escreveu:
Fabiano Caixeta Duarte wrote:
Hi, there!
When my XP users try to change passwords, they get a message saying
that
password has been changed. That's not true!
NT and LM passwords are changed but unixPassword isn't.
Look at this openldap.log lines:
Feb 12
Fabiano Caixeta Duarte wrote:
Hi, there!
When my XP users try to change passwords, they get a message saying that
password has been changed. That's not true!
NT and LM passwords are changed but unixPassword isn't.
Look at this openldap.log lines:
Feb 12 07:50:28 apolo slapd[22826]:
The question may not be related to LDAP since your domain passwords are
changed. You should be looking at why the Unix password isn't being
changed.
- Are you using LDAP for Unix authentication?
- Can you change the Unix password using passwd?
- is your password chat in smb.conf correct for
Hi, there!
When my XP users try to change passwords, they get a message saying that
password has been changed. That's not true!
NT and LM passwords are changed but unixPassword isn't.
Look at this openldap.log lines:
Feb 12 07:50:28 apolo slapd[22826]: conn=698021 op=40 MOD
John H Terpstra:
The Samba-HOWTO-Collection is literally intended to be correct and
capable of being followed literally! Please document what sucks and
help us to improve our documentation. I encourage you to file a bug
report with details of what needs to be fixed. You can file a bug
On Tuesday 08 February 2005 02:07, Tony Earnshaw wrote:
I have no gripes with the official Samba docs as included in the Red Hat
3.0.9 Samba srpm. Either the Terpstra docs or Jerry Carter's O'Reilly
boot. They are very clear, accurate and to the point; much trouble has
Thank-you for clarifying
Tony Earnshaw:
[...]
Hope this helps someone, it cost me enough pain before it worked properly
for me.
Oh yes - regular (existing or new) Posix group users can be anywhere in
your DSA, in any group (though it makes sense to put computer trusts under
ou=smb).
Simply run smbpasswd or pdbedit
John H Terpstra:
[...]
The Samba-HOWTO-Collection is literally intended to be correct and
capable of being followed literally! Please document what sucks and help
us to improve our documentation. I encourage you to file a bug report with
details of what needs to be fixed. You can file a bug
Hope this helps someone, it cost me enough pain before it worked properly
for me.
Oh yes - regular (existing or new) Posix group users can be anywhere in
your DSA,
I think you mean anywhere in your Dit; anywhere in your DSA doesn't
make much sense,
in any group (though it makes sense
On Saturday 05 February 2005 02:17 pm, Alexander Zubkov wrote:
In debug mode smbpasswd say this:
samba 3.0.11
...
smbldap_check_root_dse: Expected one rootDSE, got 0
ldap_connect_system: succesful connection to the LDAP server
ldap_connect_system: LDAP server does not support paged
On Monday 07 February 2005 03:43, Tony Earnshaw wrote:
John H Terpstra:
[...]
The Samba-HOWTO-Collection is literally intended to be correct and
capable of being followed literally! Please document what sucks and help
us to improve our documentation. I encourage you to file a bug report
Adam Tauno Williams:
[...]
Oh yes - regular (existing or new) Posix group users can be anywhere in
your DSA,
I think you mean anywhere in your Dit; anywhere in your DSA doesn't
make much sense,
Yep.
in any group (though it makes sense to put computer trusts under
ou=smb).
I think
Adam Tauno Williams:
[...]
My guess: the behaviour of 3.0.11 is more correct, and something is
clearly wrong with your DSA - the client cannot read the rootDSE. Possibly
you've got an ACL doing something you don't intend; it doesn't look like
a Samba problem. The rootDSE is used to
On Sunday 06 February 2005 09:55, Tony Earnshaw wrote:
Adam Tauno Williams:
[...]
My guess: the behaviour of 3.0.11 is more correct, and something is
clearly wrong with your DSA - the client cannot read the rootDSE.
Possibly you've got an ACL doing something you don't intend; it doesn't
Hi.
I've samba-3.0.11 now, installed from rpm on Redhat 9.0. Problem was
with 3.0.10 too. I don't exactly know when it was broken, because I
found it week ago.
I've samba as PDC with LDAP backend some time ago when user changes
password in windows or when password chenged with smbpasswd - LDAP
I've samba as PDC with LDAP backend some time ago when user changes
password in windows or when password chenged with smbpasswd - LDAP
password of this user was changed too. Now LDAP passwords remains the
same as it was.
I've searched this list a while and found only one mail, said that it
I've found only samba 3.0.6 and 3.0.9 - 3.0.11 versions downloaded at my
server. When reverting samba to 3.0.6 version sync works ok, but with
3.0.9 it is bad. I'll search through for 3.0.7, 3.0.8 versions in
Internet and will tell more when I'll check them.
--
To unsubscribe from this list go
I've samba as PDC with LDAP backend some time ago when user changes
password in windows or when password chenged with smbpasswd - LDAP
password of this user was changed too. Now LDAP passwords remains the
same as it was.
I've searched this list a while and found only one mail, said that it
was
I've samba as PDC with LDAP backend some time ago when user changes
password in windows or when password chenged with smbpasswd - LDAP
password of this user was changed too. Now LDAP passwords remains the
same as it was.
I've searched this list a while and found only one mail, said that it
In debug mode smbpasswd say this:
samba 3.0.6
# smbpasswd -D 4 test
Searching for:[((objectClass=sambaDomain)(sambaDomainName=DOMAIN))]
smbldap_open_connection: connection opened
ldap_connect_system: succesful connection to the LDAP server
The LDAP server is succesfully connected
New SMB
samba 3.0.11
[EMAIL PROTECTED] samba]# smbpasswd -D 3 test
Searching for:[((objectClass=sambaDomain)(sambaDomainName=DOMAIN))]
smbldap_open_connection: connection opened
smbldap_check_root_dse: Expected one rootDSE, got 0
ldap_connect_system: succesful connection to the LDAP server
My guess: the behaviour of 3.0.11 is more correct, and something is
clearly wrong with your DSA - the client cannot read the rootDSE.
Possibly you've got an ACL doing something you don't intend; it doesn't
look like a Samba problem. The rootDSE is used to determine features
supported by the DSA,
My guess: the behaviour of 3.0.11 is more correct, and something is
clearly wrong with your DSA - the client cannot read the rootDSE.
Possibly you've got an ACL doing something you don't intend; it doesn't
look like a Samba problem. The rootDSE is used to determine features
supported
Seems to be the case, from very cursory inspection.
Really an issue with the DSA, it should properly report its
capabilities.
Yeah! I did it, thanks all, who helped.
Searching for rootDSE in Internet showed that it is exported by LDAP
server as other data (in common words) so access control are
Hi,
On Sat, Feb 05, 2005 at 03:09:42PM -0500, Adam Tauno Williams wrote:
You want to say that samba asks LDAP of its possibilities, it returns
nothing and samba think that it can not do nothing. Am I right?
Seems to be the case, from very cursory inspection.
Really an issue with the
Hi,
On Sat, Feb 05, 2005 at 11:33:39PM +0300, Alexander Zubkov wrote:
Yeah! I did it, thanks all, who helped.
Searching for rootDSE in Internet showed that it is exported by LDAP
server as other data (in common words) so access control are applied to
it too. And my hands ( lame ;) ) wrote
Hi.
I've samba-3.0.11 now, installed from rpm on Redhat 9.0. Problem was
with 3.0.10 too. I don't exactly know when it was broken, because I
found it week ago.
I've samba as PDC with LDAP backend some time ago when user changes
password in windows or when password chenged with smbpasswd - LDAP
Hi.
I've samba-3.0.11 now, installed from rpm on Redhat 9.0. Problem was
with 3.0.10 too. I don't exactly know when it was broken, because I
found it week ago.
I've samba as PDC with LDAP backend some time ago when user changes
password in windows or when password chenged with
37 matches
Mail list logo
