similar to: pdbedit and smbpasswd

Hi there, I'm trying to import a smbpasswd-file into a Samba 3.0 installation on Debian Sarge using tdbsam as sole passdb backend. Copying pdbedit's documentation I used pdbedit -i smbpasswd:/root/smbpasswd.old The error message returned was tdb_update_sam: Failing to store a SAM_ACCOUNT for [foo] without a primary group RID where foo is the username to be imported. This message was

I'm using samba 2.2.3a with OpenLDAP server. My smbd(8) is working fine, that is, it can find user when user is opening some share on w2k boxes: (ldap log - local4) Feb 21 17:21:17 click.crol.net slapd[20169]: conn=30 op=1 BIND dn="SMBSERVER=CLICK,OU=SAMBA,OU=SERVERS,DC=CROL,DC=NET" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ And this entity has ability to

Hello Group, I've been reading many posts but i still don't have the answer to how to force a password change or set a password lifetime. I'm using w2k clients which connect to a samba PDC version 3.0.10 on a basic SunOS 5.8 system, no ldap or so. syncing the ux-passwords and the smb-passwords works perfect, but i can't get it working to force users to change passwords. The

Thank you very much for your answer. It's the default, internal backend. (smbpasswd) a) If I do : tdbdump schannel_store.tdb dump | grep BWPC |grep SECRET | wc I get 95 machines (this number looks good). b) smbpasswd is a text file that looks good. c) I can also do "tdbdump secrets.tdb dump" Thanks a lot in advance for any advice, Denis Le 15.12.2014 22:00, Gaiseric

the testparm command will show you the location of the password file and the backend type e.g. smb passwd file = /etc/samba/private/smbpasswd passdb backend = tdbsam The backend file should be a TDB database file , not a plain text file (unless left over from an older version.) You may have users or computers with duplicated SIDs. You should also use "getent

Hallo, I'm trying to convert smbpasswd to passdb.tdb. cd /etc/samba/private # (where smbpasswd lies) pdbedit -i smbpasswd -e tdbsam:/etc/samba/private/passdb.tdb converts all human users, but it converts (or transfers) no machine account. In "smbpasswd" are many entries beginning with (p.e.) mac001$ for these accounts, pdbedit -L -v | grep -i mac shows

Hi All Have recently moved from a machine running 2.2 to a new machine running 3.0.10-1. I've just converted the smbpasswd database to tdbsam as I understand password ageing etc does not work with smbpasswd. I've set the line 'passdb backend = tdbsam' in the smb.conf, restarted the daemon and now I'm trying to force a user account to have to change his password the next time

Hello, I'm using samba 3.2.41 at Debian Lenny. I have some users in my smbpasswd file, now I'm trying to force them to change password once a given period. #pdbedit -P "maximum password age" -C 300 Above-mentioned command is affecting ONLY "new" users (users created after first first launch of this command), "old" users are not affected, passwords

Hi all Maybe a stupid question, but I'm not able to figure this out from the manpage nor from the HOWTOs... How can I force a user to change his password at next logon? I tried: # pdbedit -P "user must logon to change password" -C 0 -u username # pdbedit -u username -P "user must logon to change password" -C 0 # pdbedit -P "user must logon to change password"

Hi ! This is my firs post here. I've got a problem with password history policy -C 3 which doesn't work !! I set policy pdbedit -P "maximum password age" -C 777600 (90days) pdbedit -P "minimum password age" -C 691200 (80days) "user must logon to change password" -C 2 "password history" -C 3 On clients (XP PRO) some of people

I've searched google and the samba archives to no avail (appologies if I've missed something), so I will ask the community directly: I am trying to convert a fully populated smbpasswd file to the tdbsam backend: # pdbedit -i smbpasswd:./smbpasswd -e tdbsam:./passdb.tdb This seems to work, on the surface, but upon inspection I find that # pdbedit -Lw username

Dear all, I have a very strange problem with "pdbedit -Lv" under Samba 3.3.10, a lot of users and machines are missing ! Strangely, all these missing machines and users are working perfectly well. The problem is that I need to get their SID to be able to migrate to a new server... TECHNICAL DETAILS : * Samba 3.3.10 * Number of machines : * Unix : 128 machines * pdbedit

Hi, I'm trying to migrate from a SME server to an Ubuntu 10.04 Domain names are the same (domain SID already retrieved) example User john on SME server has SID S-1-5-21-1222067456-3914006320-3959678504-11026 User john on Ubuntu server has SID S-1-5-21-1222067456-3914006320-3959678504-3010 Not to loose Windows profiles, I'm trying to modify john's SID on Ubuntu server : pdbedit -u

Hi All, I just added three users to my tdbsam with "pdbedit -a -u username" (had to do "useradd" first). All three appeared in tdbsam as they should, as verified with "pdbedit -L". But, all three also appeared in /etc/samba/smbpasswd. This is not a mistake, they were not there before. Are "tdbsam" and "smbpasswd" linked? I am confused.

hi list, we want to migrate all our users from smbpasswd into ldap, but first test it so the current samba server in production should not be changed. to achieve this i created a smb.conf file with the following content: --- [smb.conf] [global] workgroup = mpi netbios name = sandy01 netbios aliases = sandy02 sandy03 interfaces = 10.4.0.106/255.255.0.0 bind interfaces only = yes socket

I have a couple of questions about pdbedit. I am having trouble using pdbedit in shell scripts. First, on a freshly installed system with no-one in the tdbsam database, trying to add multiple machine accounts via a loop construct in a shell script fails with a message that the database can't be found/doesn't exist. I then added root manually just to get the system going, which solves

Hi guys/girls, How are you ? I've been struggling to get my users' passwords to expire. My configuration is samba-3.0 running with the standard smbpasswd back-end. Everything that I can find on the web says I should set the following to expire my users passwords after 28 days.: pdbedit -v -P 'minimum password age' -C 300 pdbedit -v -P 'maximum password age' -C 2419200

Dear Samba Users, I have a Samba 3.2.5 Server running on Debian. I use tdbsam as a password database and wonder how I can change the "Workstations" value in order to control the allowed workstations for a particular user. Last year I had a configuration with ldap using the smbldap tools where it was possible to set this value. But how can I set it without LDAP just using pdbedit?

Who wins the fight for the roaming profile path, "logon path" in smb.conf or "profile path" set by pdbedit? How do you force the "profile path" in pdbedit to get its value from "logon path" in smb.conf? Is it possible to disable roaming profiles by user with pdbedit and leave "logon path" set in smb.conf? Thanks.

I have Samba and LDAP up and running, but I'm having problems editing the password policy using pdbedit. (I'm running 3.0.22) I've had a look at the man page for pdbedit but I don't really fully understand what it does in relation to passwd backends. Does pdbedit update just one backend and expect a user to export the updates to other backends? I think I've set up ldap as