similar to: Unix password sync problems with Linux - almost there

I have samba-1.9.18p7-2 smb.conf says: # Configure smbpasswd passwd chat debug = yes # Default passwd chat = *old*password* %o\n *new*password* %n\n *new*password* %n\n *changed* passwd program = /usr/bin/yppasswd Using smbpasswd, my encrypted password is changed, but yppasswd is not even touched (as per ls -lu /usr/bin/yppasswd). Furthermore, running smbd with -d 100 didn't seem to show

Hello again, I would like to thank Giant Wang and Miquel Bonastre for their responses to my query in "Samba Digest 1734" regarding simultaneous passwd changing for users via Samba. Their comments were helpful, but have not solved the problem. For those who do not have a back log of the Digests, the problem is that with unix password sync=yes, users are not able to change their own

I'm trying to figure out how I can change to SMB password and UNIX password together. On the Win98 I change the password via : Control Panel - Passwords - Change Windows password (select also Microsoft Networking) After a few seconds I get the message 'The password you typed is not correct for MS Networking' Are there any known problems with password sync ? I read the digest 2112 till

Dear all, I have a problem synchronizing my Windows98 network password (i.e. samba password) with my Unix NIS+ password. The Unix station is running Solaris 2.6. This is a copy of what I have in smb.conf to enable password change: password level = 2 domain logons = yes logon script = %U.bat debug level = 100 encrypt passwords = yes unix password sync = yes passwd program = /usr/bin/passwd -r

Hello, I finally switched to the samba-1.9.18p4, and got all my files on this server. But now I have a big problem, all our NT machines can't access the server. They tell wrong user or password. In the debugging mode I see, that the NT machines come to the server and find the right user, then they tell me: lp_file_list_changed() file /usr/local/samba/lib/smb.conf ->

Hi, I have a problem with Samba on an OSF1 v4.0d machine. I get an "INTERNAL ERROR" and a core dump when trying to connect to a share from an NT 4.0 SP3 or W95 machine. I configured Samba to use encrypted password and I set the parameter "security=user". My Samba server is in a workgroup on its own, no PDC and BDCs around. I can see it in my Computer Neighborhood from the NT

I've been running SAMBA 1.9.14 and 1.9.17p4 for successfully for some time. Recently I thought it would be useful to update to the latest SAMBA version 1.9.18p7. This is the first time we are using Samba with the built-in DES. Here is our configuration: Machines: IBM RS/6000 AIX 4.1.4.0 or AIX 4.2.1.0 Compiler: xlC 3.1.4.0 My smb.conf file: [global] printing = aix print command

Server: Slakware Linux 2.0.30, GNU C 2.7.2.1 Samba 18p7 Server is not using PAM and is a ypclient. Client PC's are DOS 6.20 with MS Client 3.0 and Windows 95. I am having trouble changing passwords using the "net password \\<server>" command from either DOS or Win95 command prompt. Changing passwords worked fine using Samba 17p3. The compile switch -DALLOW_CHANGE_PASSWORD

-----BEGIN PGP SIGNED MESSAGE----- Hi, I''ve got several replies, thank you for them. Let me summarize: o Many people say there is a PAMified version of ssh available at ftp://ftp.replay.com/pub/crypto/redhat/SRPMS (the source) ftp://ftp.replay.com/pub/crypto/redhat/i386 (Intel binaries) (there are analogous paths for the other architectures). The packages are made by Jan

>No. ssh-keygen should never be pamifed. It is worthless to do so. > >If we are going to enforce passphrase quality it should be for all OSes. >The world does not revolve around Linux. No matter what the press may >think. The Linux community didn't invent PAM, Sun did. Many more systems than Linux have PAM, Solaris, HP-UX some BSDs for a start. Having said that I agree with

I'm having problems with the username map feature of Samba. Everything was running fine in 1.9.18p7. After the upgrade to 1.9.18p8, the mapping no longer occurs, and I see errors in the log file: password server CSUNTS rejected the password get_smbpwd_entry: unable to open file /usr/local/samba/private/smbpasswd I tried going back to 1.9.18p7, and sure enough things work like a charm. I

Hello! I'm trying to use unix password sync = true on an Intel-RedHat 5.1 samba server, because I want to have one program (e.g. smbpasswd on the unix comand prompt) to change unix and "encrypted samba" passwords; changing passwords from clients is nice but secondary. I used FLAGSM = -DLINUX -DALLOW_CHANGE_PASSWORD -DFAST_SHARE_MODES -DNO_ASMSIGNALH -DGLIBC2 -DQUOTAS LIBSM =

Hi, There have been a bunch of useful submissions for the compare /contrast thread. To reduce the load on your mailbox, they are gathered here in one go... Roger. Date: Wed, 28 Oct 1998 15:11:37 +0000 From: "David L. Sifry" <dsifry@linuxcare.com> To: "Matthew S. Crocker" <matthew@crocker.com> CC: Rob Bringman <rob@trion.com>,

Hi all. I'm experiencing long connect delays due to password file locking errors. For each connection samba logs the following errors: do_pw_lock: failed to lock SMB passwd file. mod_smbpwd_entry: unable to lock file /usr/local/samba-1.9.18p10/private/smbpasswd In the archives I found some other messages reporting the problem (on May this year), but no solution. Did I

Hi I am trying to change the password of an User in an Active Directory using the samba client tools (samba 3.0.7). A normal user can change the password using smbpasswd -r ADSERVERNAME But now a user forgetts his password, and I want to change it as an user "ADMINUSER", who has admin rights in the domain. Is there a command, weher I can do something like this: smbpasswd -r

Hello Samba Users, I cannot change a user's Samba password from a Windoze client or from the Unix Samba server when "unix password sync = True". Any ideas what/where I screwed up? AtDhVaAnNkCsE - Samba version 1.9.18p10 on a Solaris 2.5 box. - compiled with the following flags: FLAGSM = -DSUNOS5 -DSHADOW_PWD -DNETGROUP -DFAST_SHARE_MODES -DALLOW_CHANGE_PASSWORD - global

It would appear that Samba <-> Samba across subnets works fine, but Samba <-> NT is a problem. Does anybody else concur with this statement? Specifically, running Samba 1.9.18p10 (Solaris) and directing all password authenication to an NT server on a subnet causes the following output in the log file: ---------------------------------------------------------------------------

Hi! I know this is about the most asked question on these lists. I've been searching the archives looking for an answer, but all I can find is the same question over and over... I'm trying to get the Unix Password Sync option to work on my server. I'm running RH 6.0, with MD5 and shadowed passwords enabled, and Samba 2.0.5a (the RPM version). When I try to change passwords using

Hi! When I enter smbpaswd as a normal user iget the following error: Connecting to 127.0.0.1 at port 139 machine 127.0.0.1 rejected the password change: Error was : The specified password is invalid. Failed to change password for mgoeben and in the logs I got: ==> /var/log/samba/log.smb <== [2000/08/16 18:39:57, 3] locking/shmem_sysv.c:sysv_shm_open(707) Initialised IPC area of size

Hi! I'm trying to use a printer connected to a Win95 box from Linux but when I try 'smbclient -L win95_machine' I get the following message: SMBnegprot failed. myname=TARKUS destname=WIN95 - ERRSRV - 1311 I'm using samba-1.9.18p5. The access in the other way (W95 to Linux shares) works without any problems. When I set the printer as shared in the W95 box it is possible to