similar to: winbindd losing track of RFC2307 UIDs

On Tue, 4 Oct 2016 02:35:21 +0200 Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > Am 03.10.2016 um 18:57 schrieb Rob via samba: > > Hi all, > > > > I've been experiencing an intermittent problem where some UIDs on a > > member server spontaneously change from being their AD-derived > > values to being allocated from the default

On Tue, 4 Oct 2016 15:16:17 +0200 Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > Am 04.10.2016 um 10:21 schrieb Rowland Penny: > > On Tue, 4 Oct 2016 02:35:21 +0200 > > Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > >> > >> Am 03.10.2016 um 18:57 schrieb Rob via samba: > >>> Hi all, >

On Tue, 4 Oct 2016, Achim Gottinger wrote: > Am 03.10.2016 um 18:57 schrieb Rob via samba: >> [...] >> >> This generally works fine... user mappings are like: >> >> $ wbinfo -i auser >> auser:*:10028:10000:User Name:/home/auser:/bin/bash >> $ id auser >> uid=10028(auser) gid=10000(agroup) groups=10000(agroup),10007(othergroup) >>

On Tue, 4 Oct 2016 16:09:40 +0200 Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > Am 04.10.2016 um 15:43 schrieb Rowland Penny via samba: > > On Tue, 4 Oct 2016 15:16:17 +0200 > > Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > >> > >> Am 04.10.2016 um 10:21 schrieb Rowland Penny: > >>> On

Am 03.10.2016 um 18:57 schrieb Rob via samba: > Hi all, > > I've been experiencing an intermittent problem where some UIDs on a > member server spontaneously change from being their AD-derived values > to being allocated from the default idmap space, even when there is no > change to the AD user information. > > Specifically, I have a member server running Samba

Am 04.10.2016 um 10:21 schrieb Rowland Penny: > On Tue, 4 Oct 2016 02:35:21 +0200 > Achim Gottinger via samba <samba at lists.samba.org> wrote: > >> >> Am 03.10.2016 um 18:57 schrieb Rob via samba: >>> Hi all, >>> >>> I've been experiencing an intermittent problem where some UIDs on a >>> member server spontaneously change from

Am 04.10.2016 um 15:43 schrieb Rowland Penny via samba: > On Tue, 4 Oct 2016 15:16:17 +0200 > Achim Gottinger via samba <samba at lists.samba.org> wrote: > >> >> Am 04.10.2016 um 10:21 schrieb Rowland Penny: >>> On Tue, 4 Oct 2016 02:35:21 +0200 >>> Achim Gottinger via samba <samba at lists.samba.org> wrote: >>> >>>> Am

Am 21.10.2016 um 18:40 schrieb Rob via samba: > On Tue, 4 Oct 2016, Achim Gottinger wrote: > >> Am 03.10.2016 um 18:57 schrieb Rob via samba: >>> [...] >>> >>> This generally works fine... user mappings are like: >>> >>> $ wbinfo -i auser >>> auser:*:10028:10000:User Name:/home/auser:/bin/bash >>> $ id auser >>>

Am 04.10.2016 um 17:05 schrieb Rowland Penny via samba: > On Tue, 4 Oct 2016 16:09:40 +0200 > Achim Gottinger via samba <samba at lists.samba.org> wrote: > >> >> Am 04.10.2016 um 15:43 schrieb Rowland Penny via samba: >>> On Tue, 4 Oct 2016 15:16:17 +0200 >>> Achim Gottinger via samba <samba at lists.samba.org> wrote: >>> >>>>

On Mon, 3 Oct 2016 12:57:54 -0400 (EDT) Rob via samba <samba at lists.samba.org> wrote: > Hi all, > > I've been experiencing an intermittent problem where some UIDs on a > member server spontaneously change from being their AD-derived values > to being allocated from the default idmap space, even when there is > no change to the AD user information. > >

On Tue, 4 Oct 2016 12:29:19 -0400 (EDT) Rob via samba <samba at lists.samba.org> wrote: > > On Tue, 4 Oct 2016, Rob wrote: > > > On Mon, 3 Oct 2016, Rowland Penny wrote: > > > >> On Mon, 3 Oct 2016, Rob wrote: > >>> # idmap config for domain > >>> idmap config MY.AD.REALM.COM:backend = ad > >>>

Am 05.10.2016 um 22:12 schrieb Rob via samba: > On Tue, 4 Oct 2016, Rowland Penny wrote: > >> This is very strange, have you tried running 'net cache flush' on the >> domain member ? >> >> Have you compared the users AD objects ? > > Running 'net cache flush' on the member does fix things, albeit only > for a while: > > # wbinfo -i

On Wed, 5 Oct 2016 16:12:41 -0400 (EDT) Rob via samba <samba at lists.samba.org> wrote: > On Tue, 4 Oct 2016, Rowland Penny wrote: > > > This is very strange, have you tried running 'net cache flush' on > > the domain member ? > > > > Have you compared the users AD objects ? > > Running 'net cache flush' on the member does fix things,

Hi All I have done as much as I can to try and figure out what is going wrong with my samba migration by googleing and reading mailing list archives and reading documentation etc. I have an existing SAMBA 3.0.5 domain running on suse linux 9.3. I am trying to migrate this setup to a new server which is running Fedora Core 6 smbd 3.0.24-7.fc6 I have migrated the data across to the new system

Hi, I have simple installation, using mostly defaults, of two mirrored servers. One brick, one volume. GlusterFS version is 3.12.1 (server and client). All hosts involved are Debian 9.1. On another host I have mounted two different directories from the cluster using /etc/fstab: gfs1,gfs2:/vol1/sites-available/ws0 /etc/nginx/sites-available glusterfs defaults,_netdev 0 0 and

Hi, I''d like to be able to deploy a skeleton directory through puppet, i.e. puppet deploys it only if it does not exist. I tried this : file {"/path/to/this/directory": source => "puppet:///files/path/to/the/skeleton", ensure => directory, recurse => true, owner => auser, group => agroup } But I have 2 problems for the moment : - if I

I have a server 192.168.0.14 and the directory I wish to share is /home/photo I can mount from 192.168.0.1 with mount -t smbfs -o "username=photo" //192.168.0.14/photo /mnt/smbshare it prompts me for a password and I can see the contents of the share but I cannot write to it. Any pointers gladly recieved kind regards Kevin -- "Democracy is two wolves and a lamb voting on what to

Dear all, I freshly installed a new smb-server that should act as file server with some smb-shares. The pdc is a Windows 2008 r2 server. My smb.conf is as follows: [global] workgroup = agroup server string = ssmbserver #passdb backend = tdbsam map to guest = Bad User usershare allow guests = No security = domain wins support = No

On 25/10/2024 14:03, Havany via samba wrote: > Did you try 133 mask instead of 0133 ? > > We use to disable acl for this kind of share and do something like that : > > [share] > path = /a/share/path > create mask = 133 > directory mask = 022 > valid users = @agroup > write list = @sagroup > force group = @agroup > nt acl support = No Still no go: It's rwx

Hi, I've done a classic upgrade to from samba 3.6.23 to samba 4.6.5 bringing across all the user accounts. The samba 3.6.23 we set up with smbldap as an NT Domain with OpenLDAP. After a lot of effort the classic upgrade worked well but now I'm a bit stuck with idmapping. The new AD DC is running 4.6.5 on CentOS7 and I can connect using ADUC. I set up a separate AD DM on a another CentOS7