similar to: pdbedit -x -m fails to delete one machine account on samba 4.6.5 install

Doing some test i've done, as root, in one DC: root at vdcpp1:~# smbpasswd gaio New SMB password: Retype new SMB password: root at vdcpp1:~# pdbedit -v gaio Unix username: gaio NT username: Account Flags: [U ] User SID: S-1-5-21-160080369-3601385002-3131615632-1105 Primary Group SID: S-1-5-21-160080369-3601385002-3131615632-513 Full

You think Microsoft's mailing lists and forums are better? Just wait (and wait, and and ...). Oh, that's right, you can call Microsft for help ,,, and shell out $295 per. Dimitri John McLoskey wrote: > Thanks everyone for your lack of any response whatsoever, I find it builds > character to be ignored throughout challenges I encounter in my life. Since > I was unable to

I have am hitting a wall with pdbedit, as shown below. Any workarounds would be greatly appreciated. I am encountering the inability to change any users (profile) SID on Samba 3.x for Linux and BSD, which causes the accounts to no longer recognize their local Samba 2 profiles once they join Samba 3 domain. If I add a new user and pdbedit -a user -U SID it ignores the -U. The old profiles appear

In my current ''production'' NT-like domain (samba 4.2, OpenLDAP backend), password policies seems to ''get written'' to user data. EG, if i set: pdbedit -P "maximum password age" -C 7776000 and i change my password, 'Password must change' have a meningful value, eg 90 days more then the last password change: root at armitage:~# pdbedit -v

Samba version 3.0.9 on Red Hat 9.0 workstations: NT 4.0 SP6 When I took over this project, there were two domains connected by a VPN. For reasons that I'm unable to understand, some new users wound up with the intended domain of SATA and some wound up in SATB (even though they joined the SATA domain. Recently, all kinds of problems have materialized and the only thing I can find wrong is

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

Hi samba list, I'm using samba 3(.0.13) with OpenLDAP and I have a strange problem: the variables %U and %G don't seem to be replaced by their values. I get nothing in my logs, so I don't know where is the problem... In fact, in my smb.conf, I have something like: logon home = logon path = \\server\profiles\prof.%G logon drive = h: The profiles are loaded if I use logon

Any ideas why this is not working? [root at host67 ~]# pdbedit -u testuser -h \\\\five-68\\testuser -p \\\\five-68\\testuser\\profile Unix username: testuser NT username: Account Flags: [U ] User SID: S-1-5-21-369316088-3201261441-1704813131-2216 Primary Group SID: S-1-5-21-369316088-3201261441-1704813131-513 Full Name: Home Directory: \\host67\testuser

Samba Version 3.6.3 on Ubuntu 12.04 tbdsam back end. I discovered a couple of accounts we created before the Domain was configured was was an account named "administrator" intended to be the Smaba Administrator account. In order to change the domain ai ran this command # pdbedit -I "DOMAINNAME" -U username it worked on a number of accounts when I tried it on administrator

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, I have set up samba with ACL Support. I have set up Groups and users: #net groupmap list Domain Admins (S-1-5-21-3027381482-3940328739-3509331320-512) -> ntadmin Domain Guests (S-1-5-21-3027381482-3940328739-3509331320-514) -> nobody Domain Users (S-1-5-21-3027381482-3940328739-3509331320-513) -> users #pdbedit -L -v sambasven Unix username: sambasven NT username:

Hi, i'm running a samba PDC on samba 3.0 and just had to reinstall the server because of a dead cpu causing corruption. luckily i had complete backups of the samba-files, so i copied them back to /etc/samba, /var/lib/samba and /var/cache samba. (tdb-files) i had one workstation (xp) removed from the domain and wanted to add it again, but then the station always gives me an error that i

Hello Lads, I have a PDC & BDC / Master & Slave; I regularly make backups of the LDAP database: Slapcat ¡Vv ¡Vl backupallusers.txt. Both my PDC & BDC have been rebuilt from scratch, I slapadd ¡Vv ¡Vl backupallusers.txt and I net set localsid domainsidhere for the PDC << I get that from the backupallusers.txt. Smbpasswd ¡Vw secret < on both PDC & BDC Net rpc getsid

Hi, When i put the command pdbedit plus any user name show the message user not found. Only user root is exibited. Why the others not show? the service smbd winb nmbd slapd is running without problem. Example *root at AbramisSRV smbldap-tools]# pdbedit -Lv teste* Username not found! *[root at AbramisSRV smbldap-tools]# pdbedit -Lv root* Unix username: root NT username: root

Hello, We have been running Samba 2.2.x/Sun ONE LDAP on a particular machine for about 3 years now and I recently upgraded it to 3.0.14a with ldapsam compatibility (I can mess with the directory later if necessary). Now when users try to connect to the server their accounts get disabled unless I have specifically enabled them using smbpasswd -e username (which is kind of tough because I have to

dear list, in the output of pdbedit -L -v heupink I'm getting these errors: convert_string_allocate: Conversion error: Illegal multibyte sequence(???p? ????????) Any ideas where to look..? Are these serieus errors..? (it looks as if the errors occur BEFORE the actual ldap connection is opened, so I guess they're not ldap related...) My samba is 3.0.14a, and system is sles9 Below find

I'm finally near the end (I hope) of setting samba 3.0.14a as a PDC on a debian sarge, but I (and google, and list archive) can't manage to find a solution. When I add user with the help of usrmgr on my XP box, user is created both in linux and samba (thanks user add script), but lacks profile info (I mean Home Directory, HomeDir Drive, Logon Script and Profile Path), so roaming profile

Hello Lads, Problem could be smbldap-tools, im using 0.97. I have manually set the sid on the bdc which seems to work. I am confused because I thought net rpc getsid stored the sid from the pdc on the bdc in secrets. I wasn't aware that net getlocalsid should return identical results on both pdc & bdc. Please explain this - why isnt the BDC obtaining the sid automatic as it should

I have quite a few samba installations, and I've had problems with roaming profiles when upgrading from Samba 2.2 to 3.0. My servers run Debian stable, which uses Samba 2.2.3, with security patches. At some point Debian will release a new stable version with a recent Samba 3.0 release. Right now I'm testing a few servers with a samba 3.0.10 backport to make sure the transition will go

Hi All, I have just upgraded from Samba 3.0.7 to 3.0.20 on mandrake 10.1 Before upgrading I could add a machine account and admin (root) user to the password backend, join to the domain and check the trust secret. All was well. wbinfo -a name%password would authenticate, as I require for ntlm_auth with squid (which was working well). Now with the same layout, I do this :- Add unix account