similar to: Unable to change password

Hi everybody, I'm an italian system administration (newbie about Samba). I have installed on Mandrake 9.1 the rpm samba3-*-3.0.2a downloaded from a Samba.org's mirror. I have configured a PDC based on ldapsam (OpenLDAP 2.1.29) that works fine, i use smbldap tools to manage sincronization account. Now the problem, when I try from my W2000 Workstation to change my domain password I reach

Hello, Sorry to have posted in the wrong thread, resending the email. We have a samba domain and now some of the users from WINDOWS 2000 Pro are unable to change their password, below is the error : They are able to login without any problems. pdb_free_sam: SAM_ACCOUNT was NULL [2004/06/07 13:52:29, 0] smbd/chgpasswd.c:check_oem_password(817) check_oem_password: incorrect password length

Hello, I have searched hi and lo for a solution to being unable to change passwords from Windows 2000. Everything seems to work fine, shares, etc. but when I press ctrl-alt-del to bring up the Change Password dialogue, I get the message that "The user doesn't exist or the password was entered incorrectly" from Windows. I am running Samba 2.2.3a on Mandrake Linux 8.2 In my logs,

Hi, I sent this in a couple of days ago and have only gotten one suggestion. Can someone read the below problem and try to help me out? I have searched everywhere for a solution to this and have tried numerous 'passwd chat' strings to no avail. Help is much appreciated! James Herschel JSquared Network Solutions (905)847-0799 james@jsquared.ca -----Original Message----- From: James

Hi, I've got an issue with a samba 3 PDC with an ldap backend. I get a logon failure (unknown username or bad password) when trying to add a win2k box to the domain. I'm using Mandrake with Samba 3.0.2a and openldap 2.1.22. I am able to set up the workgroup on the w2k box, and access folders for users registered in the ldap database, however I am not able to join the domain with the user

Hi, Any user (besides root) cannot execute smbpasswd, neither for command line nor from the WinNT "Change password dialog". Samba works as a PDC for the domain. Additional info: 1) konsole output: Old SMB password: machine 127.0.01 rejected the password change: Error was: The specified password is invalid. Failed to change password for USERNAME (USERNAME stands for a real user name

Evening everyone. Im currently having some problems using the smbldap tools to add groups, users and such. Im using Samba 3.0.1pre3 with OpenLDAP 2.1.22. I have setup the required files: /etc/nsswitch.conf, /etc/ldap.conf and /etc/samba3/smb.conf I also configured smbldap_conf.pm as well to reflect my setup. (Quick side note: I have two of these files: one in /etc/samba3 and the other in

Hello, Getting this error: [2002/11/02 12:55:16, 0] passdb/pdb_smbpasswd.c:pdb_getsampwnam(1367) unable to open passdb database. [2002/11/02 12:55:16, 0] smbd/chgpasswd.c:check_oem_password(761) check_oem_password: getsmbpwnam returned NULL [2002/11/02 12:55:16, 0] passdb/passdb.c:pdb_free_sam(210) pdb_free_sam: SAM_ACCOUNT was NULL[2002/11/02 12:55:16, 0]

Why this log? Debian Lenny 5.0.4 Samba with PDC tailf -f /var/log/samna/log.nmbd tdb(unnamed): tdb_open_ex: /var/run/samba/unexpected.tdb (65025,49187) is already open in this process [2010/05/12 09:57:36, 1] lib/util_tdb.c:tdb_log(682) tdb(unnamed): tdb_open_ex: /var/run/samba/unexpected.tdb (65025,49187) is already open in this process [2010/05/12 09:57:36, 1] lib/util_tdb.c:tdb_log(682)

When I start winbindd (Samba v2.2.3a on Linux), I get the entries in log.winbindd shown below. What's the story on all those complaints about file "unexpected.tdb"? There is no general problem with Samba writing to that subdirectory: # ll /var/lock/samba/ total 288 -rw-r--r-- 1 root root 696 Feb 12 22:01 brlock.tdb -rw-r--r-- 1 root root 231 Feb 13

Please, What's this? Please, please, how to resolve ? [root@neosaldina-lj003 samba]# more nmbd.log tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb (835,457947) is alr eady open in this process [2005/08/04 00:12:51, 2] tdb/tdbutil.c:tdb_log(725) tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb (835,457947) is alr eady open in this process [2005/08/04

Hi all, I am running RedHat 7.3 and Samba 2.2.3a. I am using DHCP for my Linux box (hostname: NGPLinux, IP 132.189.26.62). I can see the list of shares I defined by using "smbclient -L NGPLinux -N". I can resolve the name using "nmblookup -U 127.0.0.1 NGPLinux". However, when I tried to use "nmblookup -B 132.189.26.255 NGPLinux" on the local machine, I got the

Hello there. I'm currently configuring a Samba PDC LDAP Master Server and two Samba BDC LDAP Slave Servers with slurpd replication service over Debian 3.1 Sarge and Samba 3.0.22. I'm trying to fix a problem related with the info domain entry. When I execute the "net getlocalsid [Domain]" in the PDC server, I receive the following response: # net getlocalsid [domain] [2006/04/16

Hi Samba people I saw this as a problem in the archives about a month ago but no solution ? I'm running samba 2.2.10 on Solaris 8. We have a script to replace /usr/bin/passwd which changes the NIS passwd and then uses smbpasswd to change the user's smb password to the same thing. Some users are getting : NIS password changed for diane on cauchy machine 127.0.0.1 rejected the password

Hello, I am trying to change my passwd via windows password utility. Here is what I have set: passwd program = /usr/local/sbin/smbldap-passwd.pl %u passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication* unix password sync = Yes passwd chat debug = yes I am using ldap to store everything. Auth works and the pdc stuff all works

I am trying to build 3.0.14a and use it's smbpasswd binary to change passwords on a remote debian woody samba install -- the samba install on the remote debian machine is listed as '2.2.3a-15' I can use the previous smbpasswd binary from the same version on the client linux machine to smbpasswd -r and change user passwords, but the new version from 3.0.14a does not work against the

Experts, We've just migrated from samba 2.2.8a to samba 3.0.20b in a very large corporate environment. Everything was really fine in our lab, but we began experiment serious load problems on the productive servers the morning after the procedure took place. I'll try (briefly) to describe the characteristics of the scenario: Resources: Old Environment: Hardware:

The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 2974 (/usr/sbin/smbd). This means there was a problem with the program, such as a segfault. Below is a backtrace for this process generated with gdb, which shows the state of the program at the time the error occurred. The Samba log files may contain additional information about the problem. If the

Trying to upgrade from 2.2.3a to 2.2.4 broke our Solaris 8 PDC. We see the following issues: - Compile flag -KPIC is not valid for gcc, does not seem to bread build - Now looks like directory /usr/spool/samba is needed, but not created by install - smbclient -L hemlock fails with login problem: [2001/10/16 10:43:28, 0] smbd/password.c:connect_to_domain_password_server(1295)

I am trying to get Samba to connect to a LDAP server. I am using Samba 3. When I start Samba, the following error is in the smbd.log: [2004/02/22 16:53:10, 2] lib/smbldap.c:smbldap_search_suffix(1066) smbldap_search_suffix: searching for: [(&(objectClass=sambaDomain)(sambaDomainName=IS))] [2004/02/22 16:53:10, 0] lib/smbldap.c:smbldap_open_connection(530) ldap_initialize: Time limit