similar to: passdb requires /etc/passwd entry?

It's exactly the same. Except that I use tdbsam instead of ldap and the error message therefore also is different in the log file. But the example and result is the same. Do you have any idea of workaround or fix? Cheers, Joel -----Ursprungligt meddelande----- Fr?n: Doug Campbell [mailto:doug@bpta.net] Skickat: den 11 maj 2005 10:49 Till: Joel Larsson, PF, Posten; samba@lists.samba.org

On Fri, Mar 04, 2016 at 04:16:44PM +0000, Rowland penny wrote: > On 04/03/16 09:58, Volker Lendecke wrote: > >On Fri, Mar 04, 2016 at 10:53:17AM +0100, Volker Lendecke wrote: > >>On Wed, Mar 02, 2016 at 09:23:34AM +0000, Rowland penny wrote: > >>>OK, here is the output: > >>Can you try the attached (UNTESTED!) patch? > >> > >>Thanks, >

On Fri, Mar 04, 2016 at 10:53:17AM +0100, Volker Lendecke wrote: > On Wed, Mar 02, 2016 at 09:23:34AM +0000, Rowland penny wrote: > > OK, here is the output: > > Can you try the attached (UNTESTED!) patch? > > Thanks, Gna, should have at least compiled it.... New patch :-) Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-370000-0, fax:

On Fri, Aug 26, 2016 at 06:33:26PM +0200, Ralph Böhme via samba wrote: > On Thu, Aug 25, 2016 at 12:14:00PM -0700, Jeremy Allison wrote: > > On Wed, Aug 24, 2016 at 04:06:42PM +0200, Ralph Böhme via samba wrote: > > > > > > Yeah, as much as I'd like to avoid adding a new option, I guess we > > > have to do something about it, my latest take on this is >

On Fri, Aug 26, 2016 at 04:03:49PM -0700, Jeremy Allison wrote: > On Fri, Aug 26, 2016 at 02:46:19PM -0700, Jeremy Allison via samba wrote: > > On Fri, Aug 26, 2016 at 06:44:05PM +0200, Ralph Böhme wrote: > > > > > > Cheerio! > > > -slow > > > > Still reviewing this - but a few things that will need changing: > > > > When adding the

On 01/03/16 21:35, Garming Sam wrote: > Hi Rowland, > > This new segfault seems unrelated to the previous one. It's probably > something like a double free, which typically shouldn't be that hard to > fix. If you try running the tool under valgrind, it should provide > enough information to fix the issue. > > > Cheers, > > Garming > Who or what is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I had a problem with smbpasswd -m The man pages says: -m This option tells smbpasswd that the account being changed is a MACHINE account. Currently this is used when Samba is being used as an NT Primary Domain Controller. This option is only available when

Hello! Jerry you are right about script and permissions! I'm looking again to usrmgr.exe and has corrected most of the problems of which I spoke earlier This patch is corrected most problems, but i can't fixed, current moment, problems where "not root" create "global group" ... sorry :( This patch not create security holes and another holes ... :) I'm testing

Hello I would like to use plaintext backend with a simple Samba 3.0.6 configuration to get rid of the system of double passwords and rely just on the plain old unix /etc/passwd ones. However I couldn't find any information about it in 1) man smb.conf 2) online Samba official HOWTO I tried putting passdb backend = plaintext into a smb.conf file with security=share and the Samba server

Hi list, Since I've upgraded from samba 3.0.23c to 3.0.25c my ACL's don't work as expected anymore. I'm not sure where the problem is, however. The symptoms are simple: with 3.0.23c, I could grant and revoke user, group and world write access to and from files in a share. With 3.0.25c, I can't do that anymore. When I deselect group or world read access and apply the

OS platform: FreeBSD 10.1-RELEASE-p25 Filesystem: ZFS Samba version: upgraded from 4.1.17 to 4.1.22 Problem: I have been using the shadow_copy2 and zfsacl VFS modules to enable access control and the Previous Versions feature for Windows clients. With /usr/local/etc/smb4.conf configured this way (excerpt): vfs objects = shadow_copy2 zfsacl shadow:snapdir = .zfs/snapshot

We looked at this some more, and Andrew seemed to understand and wrote the attached patch. > > We got the logs by forcing smbd to run with -d10 by patching > file_server/fileserver.c. The issue appears to be in this call: 3638 /* Ensure there was no race condition. */ 3639 if (!check_same_stat(&smb_dname->st, &fsp->fsp_name->st)) { 3640

I created the well known group Domain Admins pointing to a local group, but I am not able to add users to the group -- it claims I can only add users to local or global groups... But I only see local, domain ,well-known, builtin. There are no global groups unless one would include all groups that are not local (i.e. domain, well-known, and builtin).... So why doesn't it want to let me add

Hello all, after the upgarde from Samba 4.10.7 to 4.11.2 we get lots of these in our logfiles: 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: [2019/11/28 20:40:44.886615, 1] ../../source3/locking/share_mode_lock.c:597(get_share_mode_lock) 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY There are no symptoms accept

Hi list, My case : Local UNIX user : ZTEST domain : uuq.ork domain user : UUQ\ztest smb.conf for standalone samba : /home/hywu/smb.conf [/home/hywu] # cat /home/hywu/smb.conf [global] passdb backend = smbpasswd workgroup = WORKGROUP security=user Smbpasswd fail to change local UNIX user password (ZTEST) when samba role is DC. I want to change password of local UNIX user "ZTEST" but

Hi, I'm using samba-4.7.x I have some confusions over "map to guest=" options with setting SMB Signing 1. Set "*Server signing =auto*", "*map to guest=bad uid*" and set "client signing in windows 2k12 server group policy" to "Microsoft network client: Digitally sign communications (Always)” = *Disable*" SMB_Server is joined to Windows 2k12

Is behavior of ACLs under Samba 3.3.0 (Sernet) completely different from that under version 3.2.7? The release notes only talks about some "fixes". I installed version 3.3.0 and got completely different result with the same filesystem and the exact same samba configuration. The ACLs behaved strangely and appeared very different under Windows ACL editor. Users were now unable to

After upgrading to samba-3.0.30 on domain member servers using NT4 as PDC and running winbind users can no longer access the shares, they get prompted for passwords (which shouldn't happen) yet still cannot connect. Dropping back to 3.0.28a works (even after adding the recent security patch) fine. What can I provide to get this fixed? Thank you, -- Chris

On Thu, 25 Jan 2024 18:27:48 +0800 hhyy ww via samba <samba at lists.samba.org> wrote: > Hi list, > > My case : > Local UNIX user : ZTEST > domain : uuq.ork > domain user : UUQ\ztest > smb.conf for standalone samba : /home/hywu/smb.conf > > [/home/hywu] # cat /home/hywu/smb.conf > [global] > passdb backend = smbpasswd > workgroup = WORKGROUP >

> I've now managed to replicate the error on my test setup. I added a > third host and all hell broke loose - no locking at all when opening > Excel files apart from same-host. It seemed fine with two. > > I then downgraded to 4.4.5 and the problem persisted. So it cannot be > a regression from that patch. > > Regards, > > Alex > Here you go: Locked files: