similar to: shadow:snapdir/basedir's are they used?

I have: interfaces = lo0, eth2 and: socket address = 192.168.3.1 socket address = 127.0.0.l in my smb.conf, but when I try to "net group add anything" (on server running samba 3.5.2, as a DC): <asks for current log'ed in users's password> mypwd Could not connect to server 127.0.0.1 Connection failed: NT_STATUS_CONNECTION_REFUSED So what am I missing? Shouldn't

Forgot to CC the list. -------- Original Message -------- SUBJECT: Re: [Samba] Can't add users to well known groups... DATE: Mon, 12 Sep 2011 15:51:31 +0200 FROM: Fran?ois Legal TO: Linda Walsh Not sure if this is relevant, but if (first case shown down here) "Domain Admins" is not so much a group but a map to unix group, I'm not surprised that you

I have "/home" as a logical volume. I have snapshots: LV VG Attr LSize Origin Snap% Move Log Copy% Convert 2010.02.05-01.26.19 Home swi-ao 10.00G lvol0 39.81 2010.02.06-02.37.52 Home swi-ao 5.00G lvol0 0.25 lvol0 Home owi-ao 1.00T and they are mounted:

Dear, I appreciate the initial contact. I realized these attempts, but it still fails. For testing purposes, I created 2 LVM, one for the share folder and another to store the snapshots / shadow copy. My smb.conf looked like this: [data] comment = Folder data path = /mnt/dados read only = No browseable = yes inherit acls = Yes inherit permissions = Yes guest account = guest guest

Hi all, I'm using the VFS sbadow_copy2 module, and I think I've hit a bug. This config works: mattcen at adam:SambaTest$ cat works3/smb.conf [SambaTest] comment = SambaTest writable = yes path = /srv/SambaTest/share #vfs objects = shadow_copy vfs objects = shadow_copy2 shadow:snapdir = /mnt/dates shadow:basedir = /srv mattcen

Hi! Setup: Samba version 4.5.12-Debian. smb.conf: [global] security = USER server role = standalone server log file = /var/log/samba/log.%m log level = 3 max log size = 1000 panic action = /usr/share/samba/panic-action %d map to guest = Bad User passdb backend = tdbsam username map = /etc/samba/usersgroups.map usershare path = disable spoolss = Yes load printers = No printcap name = /dev/null

Hi, Over the past several days I have been trying to get the shadow to work with samba but haven't been successful. Can someone check below config and let me know if I am missing something? We are using Equallogic SAN and iSCSI LUNS to mount volumes. I can cleanly access samba shares on Windows 7 clients but just not shadow copy. I have referred the official how-to but couldn't get it to

On Fri, Feb 23, 2018 at 02:11:50PM +0000, Tercio Gaudencio Filho via samba wrote: > Hi! > > > Setup: Samba version 4.5.12-Debian. > > smb.conf: > [global] > security = USER > server role = standalone server > log file = /var/log/samba/log.%m > log level = 3 > max log size = 1000 > panic action = /usr/share/samba/panic-action %d > map to guest = Bad User

I am trying to use shadow copy with Samba 4.0.9 on Debian 7 (wheezy), Linux kernel 3.2. Windows 7 clients on the LAN can not see Previous Verions of files stored on the server, although I believe I have set up directories with snapshots. Here are some highlights from smb.conf :- [global] server role = active directory domain controller domain logons = yes ... [Pluto] path

Dear Rowland, Follow my smb.conf The smb.conf the fileserver: # Global parameters [global] netbios name = SRV16 server string = Samba4 Server security = ADS encrypt passwords = yes realm = domain.local workgroup = DOMAIN server services = smb log file = /var/log/samba/samba.log log level = 9 # winbind enum users = yes winbind enum groups = yes winbind use default domain = Yes

> It was just a guess that it was a DC, but it was based on this: > I was experiencing problems when I simultaneously enabled shadow_copy2 and full_audit modules. > When enabled, problems occurred in the sysvol folder. > So how can you be having problems in 'sysvol' if this is a domain > member ? > I think you should post your smb.conf. > Rowland As for the

Gentlemen, I am struggling to solve this problem. My file server Samba 4.4.5. Even the administrator user (domain admin) could not write to the share. Could someone give me a hint, in order to solve this problem? shared folder: /mnt/data Folder permissions: # getfacl /mnt/data/teste/ getfacl: Removing leading '/' from absolute path names # file: mnt/data/teste/ # owner: ricardo

On Thu, 2 Aug 2018 11:17:47 -0400 pisymbol <pisymbol at gmail.com> wrote: > On Thu, Aug 2, 2018 at 11:11 AM, Rowland Penny via samba < > samba at lists.samba.org> wrote: > > > On Thu, 2 Aug 2018 11:02:45 -0400 > > pisymbol <pisymbol at gmail.com> wrote: > > > > > Whoops! Replying to all! > > > > > > On Thu, Aug 2, 2018 at

Hello, i installed zfs-auto-snapshot with Samba/Windows Shadow Copy. If the share contains "path = /srv/userdata/" it runs for me. But if I use "path = /srv/userdata/%U" I get no "Previous Versions" on my Win10 Client. I think the problem is the variable "shadow: snapdir = .zfs/snapshot". I tried with "shadow: snapdir = ../.zfs/snapshot" and

Hi, I notice you're using 4.6.2 and I'm using 4.6.11. I made the following comment at some point within [global]:   #disable "unix extensions" to avoid using "allow insecure wide links"   #  for access to ../xxxx_SNAPS for BTRFS "previous versions" snapshots   #  --it seems to have reverted once more to not need the below two settings   ##unix

Hi Alexander # net conf delparm projects shadow:snapprefix does not change a thing. The error persists. (I killed my smb session before trying again). log still says: [2023/05/22 15:23:23.324179,? 1] ../../source3/modules/vfs_shadow_copy2.c:2222(shadow_copy2_get_shadow_copy_data) ? shadow_copy2_get_shadow_copy_data: SMB_VFS_NEXT_OPEN failed for

Hello I'm having a problem using the virusfilter and shadow_copy2 modules which, unless I'm mistaken, seems like a conflict between these modules. If I use the virusfilter, acl_xattr, recycle, shadow_copy2 and full_audit modules together, everything works perfectly, if I use the NOTHING, RENAME or DELETE actions of the virusfilter module. If I choose to use the QUARANTINE action for the

Hi, I'm running samba 3.6.7 on a linux server: root at SRVUBUNTU:/btrfs/samba/.btrfs# smbd -V Version 3.6.7 root at SRVUBUNTU:/btrfs/samba/.btrfs# uname -a Linux SRVUBUNTU 3.5.2 #1 SMP Fri Aug 17 15:26:57 CEST 2012 x86_64 x86_64 x86_64 GNU/Linux I have a base dir to share with samba on /btrfs/samba root at SRVUBUNTU:/btrfs/samba# ls -l total 0 -rw-r--r-- 1 root root 0 Aug 24 13:07 a

On Thu, Aug 2, 2018 at 11:11 AM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Thu, 2 Aug 2018 11:02:45 -0400 > pisymbol <pisymbol at gmail.com> wrote: > > > Whoops! Replying to all! > > > > On Thu, Aug 2, 2018 at 10:55 AM, Rowland Penny via samba < > > samba at lists.samba.org> wrote: > > > > > On Thu, 2 Aug 2018

If I’m not confused though, I believe pisymbol CAN get a mount. It’s just that the mount has read-only access despite the file ownership and modes being set to give full read-write? -E > On Aug 2, 2018, at 8:56 AM, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Thu, 2 Aug 2018 11:17:47 -0400 > pisymbol <pisymbol at gmail.com <mailto:pisymbol at