Ive just discovered that my previous email is wrong - the password sync does in fact work under Solaris fine. What is happening however is that when I create a new account, and call smbpasswd $user as root, it only updates the SMB password and not the Unix password as well. I though I could change my call to /bin/passwd in my new user creation scrip with /usr/local/samba/bin/smbpasswd -a, but as it doesnt actually update the unix password this isnt particularly usefull and I would rather not have to call passwd AND smbpasswd and enter the password 4 times. -- Matthew Geier, matthew@law.usyd.edu.au Computer Systems Manager, +61 2 9351 0240 Law School, University of Sydney +61 2 9351 0200 (fax)
Matthew Geier wrote:> > Ive just discovered that my previous email is wrong - the password sync > does in fact work under Solaris fine. What is happening however is that > when I create a new account, and call smbpasswd $user as root, it only > updates the SMB password and not the Unix password as well. >Well if you compile Samba with -DALLOW_CHANGE_PASSWORD and set up the parameters : passwd program - program to call to change unix password passwd chat - expect/send style script to drive the above unix password sync = true Then smbd *will* change your UNIX password as well as the smb password. The tricky part is setting up the passwd chat script correctly for your system. Hope this helps, Jeremy Allison, Samba Team. -- -------------------------------------------------------- Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. --------------------------------------------------------
Hi Samba Folks!
I am having trouble using the "unix password sync" feature.
I try to use smbpasswd to change both the smbpasswd and UNIX passwords. When I
run smbpasswd as root to change a users password it changes the samba password
but not the UNIX password. I would have expected the "unix apssword
sync" feature
to change both passwords. "smbpasswd username" runs without errors.
My Environment:
AIX 4.3.2
Samba 2.0 (Downloaded AIX binary from samba.org yesterday)
My smb.conf
workgroup = MYGROUP
server string = Samba Server
encrypt passwords = Yes
passwd chat = *Old*password* %o\n *New*password* %n\n *new*password*
%n\n
passwd chat debug = Yes
unix password sync = Yes
log level = 100
log file = /var/log/samba/log.%m
max log size = 50
printcap name = /etc/printcap
dns proxy = No
Output when sbmpasswd run in debug mode:
# smbpasswd -D 100 username
doing parameter log file = /var/log/samba/log.%m
doing parameter max log size = 50
doing parameter printcap name = /etc/printcap
doing parameter dns proxy = No
pm_process() returned Yes
lp_servicenumber: couldn't find homes
codepage_initialise: client code page = 850
load_client_codepage: loading codepage 850.
Adding chars 0x85 0xb7 (l->u = True) (u->l = True)
Adding chars 0xa0 0xb5 (l->u = True) (u->l = True)
Adding chars 0x83 0xb6 (l->u = True) (u->l = True)
Adding chars 0xc6 0xc7 (l->u = True) (u->l = True)
Adding chars 0x84 0x8e (l->u = True) (u->l = True)
Adding chars 0x86 0x8f (l->u = True) (u->l = True)
Adding chars 0x91 0x92 (l->u = True) (u->l = True)
Adding chars 0x87 0x80 (l->u = True) (u->l = True)
Adding chars 0x8a 0xd4 (l->u = True) (u->l = True)
Adding chars 0x82 0x90 (l->u = True) (u->l = True)
Adding chars 0x88 0xd2 (l->u = True) (u->l = True)
Adding chars 0x89 0xd3 (l->u = True) (u->l = True)
Adding chars 0x8d 0xde (l->u = True) (u->l = True)
Adding chars 0xa1 0xd6 (l->u = True) (u->l = True)
Adding chars 0x8c 0xd7 (l->u = True) (u->l = True)
Adding chars 0x8b 0xd8 (l->u = True) (u->l = True)
Adding chars 0xd0 0xd1 (l->u = True) (u->l = True)
Adding chars 0xa4 0xa5 (l->u = True) (u->l = True)
Adding chars 0x95 0xe3 (l->u = True) (u->l = True)
Adding chars 0xa2 0xe0 (l->u = True) (u->l = True)
Adding chars 0x93 0xe2 (l->u = True) (u->l = True)
Adding chars 0xe4 0xe5 (l->u = True) (u->l = True)
Adding chars 0x94 0x99 (l->u = True) (u->l = True)
Adding chars 0x9b 0x9d (l->u = True) (u->l = True)
Adding chars 0x97 0xeb (l->u = True) (u->l = True)
Adding chars 0xa3 0xe9 (l->u = True) (u->l = True)
Adding chars 0x96 0xea (l->u = True) (u->l = True)
Adding chars 0x81 0x9a (l->u = True) (u->l = True)
Adding chars 0xec 0xed (l->u = True) (u->l = True)
Adding chars 0xe7 0xe8 (l->u = True) (u->l = True)
Adding chars 0x9c 0x0 (l->u = False) (u->l = False)
Derived broadcast address 9.255.255.255
Added interface ip=9.3.240.215 bcast=9.255.255.255 nmask=255.0.0.0
New SMB password:
Retype new SMB username:
startsmbfilepwent: opening file /usr/local/samba/private/smbpasswd
search by name: username
startsmbfilepwent: opening file /usr/local/samba/private/smbpasswd
getsmbfilepwent: skipping comment or blank line
getsmbfilepwent: skipping comment or blank line
getsmbfilepwent: skipping comment or blank line
getsmbfilepwent: returning passwd entry for user root, uid 0
getsmbfilepwent: entry invalidated for user daemon
getsmbfilepwent: entry invalidated for user bin
getsmbfilepwent: entry invalidated for user sys
getsmbfilepwent: entry invalidated for user adm
getsmbfilepwent: entry invalidated for user uucp
getsmbfilepwent: entry invalidated for user guest
getsmbfilepwent: entry invalidated for user nobody
getsmbfilepwent: entry invalidated for user lpd
getsmbfilepwent: entry invalidated for user nuucp
getsmbfilepwent: entry invalidated for user imnadm
getsmbfilepwent: returning passwd entry for user username, uid 201
found by name: username
endsmbfilepwent: closed password file.
mod_smbfilepwd_entry: opening file /usr/local/samba/private/smbpasswd
mod_smbfilepwd_entry: skipping comment or blank line
mod_smbfilepwd_entry: skipping comment or blank line
mod_smbfilepwd_entry: skipping comment or blank line
mod_smbfilepwd_entry: entry exists
endsmbfilepwent: closed password file.
Password changed for user username
#
In could not find anything relating to passwords in log.smb and
log.<systemname>.
Also, interesting that testparm reports the following errors even though all
changes to smb.conf were done though swat:
ERROR: the 'passwd chat' script [*Old*password* %o\n *New*password*
%n\n *new*password* %n\n]
expects to use the old plaintext password via the %o substitution. With
encrypted passwords this is not possible.
(I modified the password chat for AIX)
My Questions are:
1. Is there something obviously wrong with my configuration?
2. Does smbpasswd always work in a client-server mode where the change of both
passwords
is performed by smpd?
Any suggestions are welcome.
Zoran Gagic (zorang@ozemail.com.au)
__________________________________________________________
Message sent by MyMail http://www.mymail.com.au/
Hi! My problem: I have to setup a Samba-Server and I want to syncronize the smbpasswd File with the passwd File. Here are my information about my system and smb.conf file: My OS: SuSE Linux 6.3 (Kernel 2.2.13) Samba: 2.0.6 some smb.conf Parameters: encrypt passwords = Yes passwd program = /usr/bin/passwd %u unix password sync = Yes passwd chat = "*New password*" %n\n "*New password (again)*" %n\n "*Password changed*" Now my problem: The syncronization doesn't work. If I'm logged in as a user and want to change the password with the smbpasswd command, I get this error: machine 127.0.0.1 rejected the password change: Error was: The specified password is invalid. But I know that the password is correct! In the smb.log I is the following error: [2000/03/21 15:00:13, 0] smbd/chgpasswd.c:check_oem_password(693) check_oem_password: incorrect password length (-878254492). What is the oem_password? Thank you for your help! greetings Mego
Hi everyone, I've installed Samba on a Sparc/Solaris 8 system from the package file obtained from sunfreeware.com (samba version 2.2.2). I can't seem to get the unix password sync working. This machine is just using local passwd and shadow files for logins, and the passwd program is where it's supposed to be. I've attached my smb.conf file [smbconf.txt]. Running smbpasswd changes the Samba password for the user no-problem but the unix password doesn't get changed. I've also tried using my own shell script in place of the /usr/bin/passwd to echo the %u variable into a file. The script was just this: #!/bin/sh echo $1 >> /home/beau/junk/smbtest.file As far as I understand it this should echo the username of the account I am trying to set the password for with smbpasswd into the file smbtest.file, but the file remains empty. Does this mean anything???? Advice anyone? Anyway, have a look at my conf file if you like. Cheers, Beau -------------- next part -------------- # #------------------------------------------- # Normal Global Stuff #------------------------------------------- # [global] workgroup = SAMBA interfaces = 192.168.10.50/24 status = yes browseable = yes lock directory = /usr/local/samba/var/locks log file = /usr/local/samba/var/log.%m syslog = 2 # #------------------------------------------- # Performance Tuning #------------------------------------------- # getwd cache = yes socket options = TCP_NODELAY keep alive = 60 dead time = 30 locking = yes map hidden = yes map archive = yes map system = yes # #------------------------------------------- # Logon Stuff #------------------------------------------- # security = user encrypt passwords = yes smb passwd file = /usr/local/samba/private/smbpasswd passwd chat = "*New password:*" %n\r "*Re-enter new password:*" %n\r "*passwd (SYSTEM): passwd successfully changed for*" %u passwd program = /usr/bin/passwd %u os level = 34 # #------------------------------------------- # Homes #------------------------------------------- # [home] comment = "Home Directory for : %u " path = /home/%u guest ok = no read only = no
Hi,
I built a Fileserver (OS = FreeBSd 4.7) using Samba 2.2.6pre2. All the
clients are using Win2K or Win NT4.
Samba is the PDC, using many shares, roaming profiles, netlogon etc. It
works great.
At this moment I want samba to support "unix password sync".
That's why I
added these lines to smb.conf:
# Sync the SMB and UNIX password
unix password sync = true
smb passwd file = /usr/local/private/smbpasswd
passwd chat = *\n*ew\spassword* %n\n *ew\spassword*
%n\n*updating\sthe\sdata
passwd chat debug = no
passwd program = /usr/bin/passwd %u
In this situation should the unix and samba password change when the user
changes the password in Windows.
The Unix password will be changed, but the samba password won't. After the
unix password is changed I have to wait a long time till an error message
appears in windows, saying: Windows cannot change the password because the
WORKGROUP is unavailable.
An error message is visible on the server: pid 445 (smbd), uid 1000: exited
on signal 6
But no errors are visible in the server logfiles.
When I change "unix password sync" in smb.conf to false. It isn't
possible
to change the unix-password, but it is possible to change the samba
password.
Does anyone know a appropriate solution to this problem?
Thanks,
Dennis
Hi, This is my last (desperate) attempt to get the "unix password sync" working I've been trying to get it working for weeks, but it still doesn't work. Serverspecs: OS: FreeBSD 4.8-release Samba: 2.2.8 Samba is working as a PDC using roaming profiles. This works fine. If the option "unix password sync" in smb.conf (available @ http://home.studenten.net/~dknies/smb.conf)is enabled, the next situation is created: 1) Root can change the unix-and smbpasswd for all users 2) A regular user kan chage his unix password using the 'passwd' command -bash-2.05b$ passwd Changing local password for dennis. Old password: New password: Retype new password: passwd: updating the database... passwd: done This user isn't abled to change the smbpassword using the 'smbpasswd' command -bash-2.05b$ smbpasswd Old SMB password: New SMB password: Retype new SMB password: machine 127.0.0.1 rejected the password change: Error was : RAP86: The specified password is invalid. Failed to change password for dennis I'm sure the Old Password wasn't invalid. And the most strange thing is: The unixpassword is changed into the net smbpassword. 3) When a regular users wants to change his password in win2k (All the clients are win2k overhere) this error will pop up: The system cannot change your password now because the domain FreeBSDgroup is not available I can't find errors in my logfiles which tell me anything about the errors or the solutions. Because I'm _really_ desperate I deinstalled everything on my system, but the error keeps alive. Can someone tell me anything about this problem, because I really don't have a clue... Thanks in advance, Dennis Knies -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/