similar to: Change in smbpasswd in 3.0.6

Running into a lot of people upgrading to the 3.0.6 package that all of a sudden begin to experience the "Failed to verify incoming ticket!" errors etc., that are generally associated with a kerberos package incompatibility. However many of these people are running later versions of kerberos *and* reverting to a previous version of Samba appears to fix the issue. Is there something new

I've upgraded my samba server to 3.0.6 and without any warning the command smbpasswd no longer accepts passing the user password on the command line! This was a very bad thing for me since the scripts I use to generate all my users account stopped working :-( Anyone had the same problem? Any suggestions before rewriting everything.... Pedro Silva

I have been using (actually inheareted the system) a file for the Samba password database using since something during the 2.0 erra. New accounts have been successfully added and users are apparently logging in ok. After installing 3.0.6 I am seeing these things in my log (log level=3). mod_smbfilepwd_entry: Using old smbpasswd format. This is no longer supported.! 1. What is the

AIX 5.2 Samba 3.0.6 the smbpasswd file is showing only the nt (second) hash after a machine join. the lm hash (first) is all X's. is this expected? I also noticed in LDAP that this was the case on password changes for users. has the LM hash been dropped? Bill

One topic I can't find in either Samba 3 by Example or the Offical Samba 3 Howto & Reference Guide is that of migrating from a Samba3 server to a newer Samba 3 server (meaning newer hardware in this case). We are currently using the smbpasswd backend. I plan to move to tdbsam but that hasn't been done yet. All of the servers in question are running either whitebox 3 or redhat 9

Hello, I have defined 20.000 users on a Samba-server. The samba-server takes care of domain logons. When several users try to authenticate at THE SAME time the server can't follow: only the first users can succesfully logon. When they don't logon simultaneously there's no problem. For example: 20 users log on at exactly the same time. This situation occurs in our pc-rooms when

That was a good hint! Yes, I've installed SP2, and it realy seems to be the Problem. Now I've checked that on a machine with SP1 - and the jobs from the same printqueue are removed correctly there! -------- Original Message -------- Subject: Re: [Samba] Samba 3.0.9 doesn't remove printjobs ? (14-Dez-2004 19:13) From: novosirj@umdnj.edu To: t.pompe@architekt-prinz.at >

Hi all, Looking for a solution to the following:- # smbpasswd -x jh--- build_sam_account: smbpasswd database is corrupt! username jh--- with uid 1774 is not in unix passwd database! Failed to initialise SAM_ACCOUNT for user jh---. Does this user exist in the UNIX password database ? Failed to modify password entry for user jh--- # Ths user has already been deleted from the /etc/passwd (in

Hello world, I have a very strange update problem: this night I upgraded from 3.0.5 to 3.0.6 (debian unstable) and the system broke completely with very strange errors (I did not change anything to smb.conf) - win98 users can log in, copy and everything - xp users can log in, they see the shares but they cannot access the files (read error in xp). I have tested it with Xp-Prof SP1 und SP2

how about redirecting the smbpasswd file to the older version (assuming you have one) using smbpasswd file = /file/path/smbpasswd , I replaced my copy of smbpasswd for 3.09 with a 2.216 and the smbpasswd command stopped working, (no new entry added to the smbpasswd file), but when i used that it worked again "Izo" <I@siol.net> wrote in message news:41B8004E.8050807@siol.net...

My message is first in english (hope you'll understand it), et en fran?ais pour ceux qui le causent. --- ENGLISH --- Hi everybody, I've got a matter with my Samba server supplied by Debien 2.2r0. testparm returns there's no problem in smb.conf. It's in 'security = DOMAIN' mode. I've got 3 boxes : SERVEUR$, POSTE1$ and POSTE2$, and 6 users, all correctly added to

Hallo , when I try to change user password on samba server i become this error : error connecting to 127.0.0.1:139 (Verbindungsaufbau abgelehnt) unable to connect to SMB server on machine 127.0.0.1. Error was : code 0. Failed to change password for bukhari if any someone I have an Idea please send me an E-Mail to "ufz6@rz.uni-karlsruhe.de" Thanks to All Amir Bukhari

I installed samba 3.0.6 today. I had to upgrade samba.schema in openldap as well to include sambaPasswordHistory and sambaLoginTime, otherwise certain things would not work (e.g. smbpasswd or users changing passwords) openldap failed to start because both attributes have the same OID, ...2.1.50. In order to get started anyway, I changed the sambaPasswordHistory OID to ...2.1.52 (which, in my

Due to a config typo, I could not find any log.nmbd og log.smbd. When I realized my own error, I was able to establish the log.smbd when starting the daemon with the -l (or --logfile) parameter. This, however, works only for smbd - nmbd seems to ignore the mentioned parameter totally. Anyone else having a similar experience ? Cheers, Joern.

Hi all, I'm wondering what about machine accounts (WinXP) by migrating from Samba 2.2.8 with authentication backend /etc/smbpasswd to Samba 3.0.4 with ldapsam. Is it possible just to take NT hash from smbpasswd and paste it to ldap record as sambaNTPassword? I'm not able to login from machine vs3 to new domain. My configuration files and log files follow. The Samba-SID is the same

Hello. My unix password sync is working ok, thus when an user changes his password with "Ctrl+Alt+Del|Change Password" in Windows. However, if I run "smbpasswd" manually, I get two messages saying "password changed", but the unix password is not changed. :( Is this behaviour the right one? Thanks. - Oscar.

Dear all, We recently upgraded an old samba 3.0.10 to 3.4.6 due to broken quota when moving from Veritas to NFS mounts from a Cellera EMC. Anyway, Our samba passwd backend is a smbpasswd file. This file is generated from a database. Recently we see that some PC clients manage to change the LANMAN field in the smbpasswd file. e.g.

Hello, I have installed / configured samba-ldap (compiled SAMBA_2_2 from CVS) Whe i try to change the password for the root user, there is no problem. If i try to change the password of an ordinary user, i get the error: nas:~# smbpasswd -U william New SMB password: Retype new SMB password: No user to modify! Password changed for user william. Failed to modify entry for user william. Failed to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I try to change a userpassword with smbpasswd. But I allway get an errormessage: - ----------- root at sambabuch-c1:~# smbpasswd -U EXAMPLE\\stefan -r `nslookup _ldap._tcp.dc._msdcs.example.net | awk '{print $2;exit;}'` Old SMB password: New SMB password: Retype new SMB password: machine 192.168.56.11 rejected the password change: Error

May anyone help me solve the problem? I use samba 2.2.2 on Solaris 8 ngnvob02 [** NONE **]/export/home/sitlb $ cd /usr/local/samba/bin ngnvob02 [** NONE **]/usr/local/samba/bin $ ./smbpasswd Old SMB password: New SMB password: Retype new SMB password: machine 127.0.0.1 rejected the tconX on the IPC$ share. Error was : = ERRSRV - ERRbadpw. Failed to change password for sitlb But I can change the