similar to: pdbedit

Having some major troubles with smb and making it a PDC For 2 weeks now I have been testing, and retesting. At one point I had it all working except for password changing. Has anyone goten Samba 3.0.4 to work correctly as a PDC with an smbpasswd back ground (not pam or ldap). If so could you please send me a working copy of your SMB file (only core components needed, no need for shares or

I have just implemented an NT Domain using samba 3.0.4 on Slackware 9.1, a very simple LAN with 4 or 5 clients. Clients: Win XP Pro. Everything looks OK so far, apart from this issue: I create machine accounts for existing client machines using their existing names ... works fine, they can join domain. Except that we want to rename the existing machines using a new consistent format (client1,

Hi Folks, I would really appreciate any words of wisdom people here could provide me. I have Samba 2.2.7a, as shipped with RH 9.0, running on a server, supporting about 25 W2k clients. The linux kernel is running in SMP mode to use the Hyper-Threaded Pentium-4 CPU. I have tried to create the simplest SAMBA setup possible, so have no LDAP, ACLS, etc. The 25 w2k clients are all architects

Interesting question. I'm not complaining, I find that the Linux/OSS world is in general amazingly helpful, and people do find answers on this list. However, I must say that several of my own questions here never got answered, and many others go unanswered. The samba team is doing a fantastic job, but yes, this list does seem short of people who have the time or expertise to provide answers.

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

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.

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

Greetings, I am running samba-3.0.10-1.4E.9 installed from rpm on CentOS 4.4. I have it configured as a PDC. It is using the /passdb backend = tdbsam/ backend. I am using /pdbedit/ to make some configuration changes to user passwords. I would like to expire a users password, so that they are required to change it the next time they log in. From all that I have read in on-line resources

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

Hello! Rowland Penny via samba <samba at lists.samba.org> schrieb am 01.10.16 um 22:11:22 Uhr: > > when I do a pdbedit -a -u andreas where is the result > > stored? > > > > In whatever Samba database you have set in smb.conf This is the global part of smb.conf, its the standard part of a fresh openSUSE installation: [global] workgroup = WORKGROUP

question on pdbedit - when using it for a migration - existing data is stored in tdbsam. pbdedit -i tdbsam -e ldapsam It wants to take existing machine accounts and put them into an ou=Computers. I'd rather it put them in ou=People. Samba version is 3.09 Thanks....... Jon Johnston Creative Business Solutions IBM, Microsoft, Novell/Suse, Sophos Consultants http://www.cbsol.com

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

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

Hello! This is /etc/samba on an openSUSE 13.2: -rw-r--r-- 1 root root 249 8. Jul 15:47 lmhosts -rw-r--r-- 1 root root 1238 8. Jul 15:47 smb.conf -rw-r--r-- 1 root root 379 8. Jul 15:47 smbusers when I do a pdbedit -a -u andreas where is the result stored? # pdbedit -L andreas:1000:Andreas The content of /etc/samba did not change after editing a user. # whereis samba samba:

I would like to be able to change between backends but I'm worried that my users will encounter trouble loggin in. So I'm looking for reassurance that my command is ok. My current configuration is: passdb backend = ldapsam:ldap://10.10.10.10 smbpasswd guest I would like to change from ldap to tdbsam. Is this the command to use: # pdbedit -i ldapsam:ldap://10.10.10.10 -e tdbsam I

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

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"

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

Hi folks. I discovered this odd behaviour a few days ago while playing with SAMBA_3 for the first time. The following points apply to samba-3.0.0beta and to cvs-20030807. 1. (tested with tdbsam) If I create a user entry with pdbedit, the domain name field is not set to the domain specified in the configuration file. For me it's getting set to the local machine name. If I logon to a