similar to: winbind behavior question

2018-07-19 23:18 GMT+08:00 Rowland Penny via samba <samba at lists.samba.org>: > On Thu, 19 Jul 2018 23:06:50 +0800 > d tbsky via samba <samba at lists.samba.org> wrote: > >> Hi: >> >> I have one samba 4.7/4.8 DC, one samba member file server (rhel 7.5 >> with samba 4.7.1), and one windows 7 member PC. >> >> if I create an account

2018-07-19 23:59 GMT+08:00 Rowland Penny via samba <samba at lists.samba.org>: > > Please see inline comments. > > On Thu, 19 Jul 2018 23:44:48 +0800 > d tbsky <tbskyd at gmail.com> wrote: > >> thanks a lot for the quick help. I remember in old days it happened >> sometimes. but after upgrade rhel 7.5 (from samba 4.6.x to 4.7.1) and >> samba DC

On Mon, 23 Jul 2018 14:48:00 +0800 d tbsky <tbskyd at gmail.com> wrote: > 2018-07-22 17:44 GMT+08:00 d tbsky <tbskyd at gmail.com>: > > 2018-07-19 23:59 GMT+08:00 Rowland Penny via samba > > <samba at lists.samba.org>: > >> > >> Please see inline comments. > >> > >> On Thu, 19 Jul 2018 23:44:48 +0800 > >> d tbsky

On Mon, 23 Jul 2018 16:46:50 +0800 d tbsky <tbskyd at gmail.com> wrote: > 2018-07-23 16:04 GMT+08:00 Rowland Penny via samba > <samba at lists.samba.org>: > >> >>> idmap config SAMDOM:range = 1000-999999 > >> idmap config SAMDOM:unix_primary_group = yes > > > > That isn't a bug, it is a feature ;-) > > Before 4.6.0

2018-07-23 16:04 GMT+08:00 Rowland Penny via samba <samba at lists.samba.org>: > On Mon, 23 Jul 2018 14:48:00 +0800 > d tbsky <tbskyd at gmail.com> wrote: > >> 2018-07-22 17:44 GMT+08:00 d tbsky <tbskyd at gmail.com>: >> > 2018-07-19 23:59 GMT+08:00 Rowland Penny via samba >> > <samba at lists.samba.org>: >> >> >> >>

> 2018-07-23 18:38 GMT+08:00 Rowland Penny via samba <samba at lists.samba.org>: >> Then it looks like I need to add something to the Samba wiki about this. > > Hi: > maybe. please wait a moment. I will re-setup the environment to > check it the theory is correct. Hi: the theory seems correct. although I don't have windows with ADUC for my testing domain, I

2018-07-22 17:44 GMT+08:00 d tbsky <tbskyd at gmail.com>: > 2018-07-19 23:59 GMT+08:00 Rowland Penny via samba <samba at lists.samba.org>: >> >> Please see inline comments. >> >> On Thu, 19 Jul 2018 23:44:48 +0800 >> d tbsky <tbskyd at gmail.com> wrote: >> >>> thanks a lot for the quick help. I remember in old days it happened

On Mon, 23 Jul 2018 18:22:55 +0800 d tbsky <tbskyd at gmail.com> wrote: > 2018-07-23 18:01 GMT+08:00 Rowland Penny via samba > <samba at lists.samba.org>: > > On Mon, 23 Jul 2018 17:19:07 +0800 > > When I said 'ignored', I should have said 'ignored by Unix', if your > > users are logging into Windows, then they are not using the > >

Hi: I have a samba dc and a samba member file server. I use rfc2307 id mapping and posix acl share for windows/linux client for many years. they are simple and work fine. however in older versions of samba (maybe 5 years ago). sometimes after I create a user account at samba dc, the member file server can not recognize it (eg: "getent passwd xxxx" or "id xxxx" return

On Mon, 23 Jul 2018 17:19:07 +0800 d tbsky <tbskyd at gmail.com> wrote: > 2018-07-23 17:02 GMT+08:00 Rowland Penny via samba > <samba at lists.samba.org>: > > On Mon, 23 Jul 2018 16:46:50 +0800 > > d tbsky <tbskyd at gmail.com> wrote: > > > >> 2018-07-23 16:04 GMT+08:00 Rowland Penny via samba > >> <samba at lists.samba.org>: >

Hi: I want to convert our samba file server from rfc2307 to rid backend. the configuration looks like: idmap config *:backend = tdb idmap config *:range = 5000-9999 idmap config SAMDOM:backend = rid idmap config SAMDOM:range = 10000-999999 idmap config SAMDOM:unix_primary_group = yes Most things work fine. normal user-id and group-id changed. so we change owners and acls to

hi: at RHEL 7.4 we had used "map untrusted to domain = yes". so users can login with "username" instead of "sam-dom\username". after upgrade to RHEL 7.5, samba version upgrade from 4.6 to 4.7. now "map untrusted to domain = yes" or "map untrusted to domain = auto" are not working. can we still let user to use "usename" instead

2018-06-29 15:12 GMT+08:00 Rowland Penny via samba <samba at lists.samba.org>: > On Fri, 29 Jun 2018 12:56:33 +0800 > d tbsky via samba <samba at lists.samba.org> wrote: > >> hi: >> >> at RHEL 7.4 we had used "map untrusted to domain = yes". so users >> can login with "username" instead of "sam-dom\username". >>

Hi folks, AD server CentOS 7-1804, Samba 4.9.1 compiled from source, only used as AD server, with netlogon and sysvol, just like any Windows AD server AD member server CentOS 7-1804, Samba 4.7.1 installed from CentOS repositories, intended for use as a file server, with shares for roaming profiles, home directories, and data shares. I know that the getent problem has been discussed ad

On Mon, 23 Jul 2018 18:34:36 +0800 d tbsky <tbskyd at gmail.com> wrote: > 2018-07-23 18:01 GMT+08:00 Rowland Penny via samba > <samba at lists.samba.org>: > > On Mon, 23 Jul 2018 17:19:07 +0800 > > d tbsky <tbskyd at gmail.com> wrote: > > If, as it sounds, you were altering the users primaryGroupID > > attribute, then you should not have been doing

Hi: I tried to use samba 4.8.1/4.8.2 to join windows domain as DC. and saw warning message like "Unable to determine the DomainSID, can not enforce uniqueness constraint on local domainSIDs" I didn't get that message when using samba 4.7.7. is the message safe to ignore? the complete join message below: [root at samba-dc ~]# /usr/local/samba/bin/samba-tool domain join

Hello list Samba newbie here, loolking for help. I am trying to follow the samba wiki to setup a domain controller and an attendant file server. I built samba from 4.7.1 source and I am installing on a set of Centos 7 VMs. So far everything looks ok, but when I run smbclient on the DC I get the following, and cant see the domain presented: [root at testbox ~]# smbclient -L localhost -U%

On 10/1/18 10:02 AM, Rowland Penny via samba wrote: > On Sun, 30 Sep 2018 23:25:48 +0200 > Peter Milesson via samba <samba at lists.samba.org> wrote: > >> Hi folks, >> >> AD server CentOS 7-1804, Samba 4.9.1 compiled from source, only used >> as AD server, with netlogon and sysvol, just like any Windows AD >> server >> >> AD member server

Dear Rowland, our windows admin assured me that they have set uidNumber and gidNumber in the range. I have requested screenshots for confirmation. Now we are one step further: "getent passwd | grep mdecker" now lists the AD account. mdecker:*:13667:7142:Decker, Martin:/home/MYDOM/mdecker:/bin/false With "getent passwd mdecker" however, it shows

2018-07-23 17:02 GMT+08:00 Rowland Penny via samba <samba at lists.samba.org>: > On Mon, 23 Jul 2018 16:46:50 +0800 > d tbsky <tbskyd at gmail.com> wrote: > >> 2018-07-23 16:04 GMT+08:00 Rowland Penny via samba >> <samba at lists.samba.org>: > > >> >> >>> idmap config SAMDOM:range = 1000-999999 > >> >> idmap