search for: 3000048

Hello again, no idea!? Both my DCs running now 4.3.4, but there is a strange behaviour, Ex.: First DC root at s4master wingroup]# id maurerp uid=90036(TPLK\maurerp) gid=100(users) Gruppen=100(users),3000048(TPLK\schreiben),3000038(TPLK\orbis),3000023(TPLK\ agfa),3000009(BUILTIN\users) Second DC [root at s4slave ~]# id maurerp uid=90036(TPLK\maurerp) gid=100(users) Gruppen=100(users),3000048(TPLK\aerzte08$),3000038(TPLK\reserve09$),3000023( TPLK\agfa),3000001(BUILTIN\users As you see group with ID 3...

On 09/02/16 09:26, Mueller wrote: > Hello again, > no idea!? > > Both my DCs running now 4.3.4, but there is a strange behaviour, > Ex.: > First DC > root at s4master wingroup]# id maurerp > uid=90036(TPLK\maurerp) gid=100(users) > Gruppen=100(users),3000048(TPLK\schreiben),3000038(TPLK\orbis),3000023(TPLK\ > agfa),3000009(BUILTIN\users) > > Second DC > > [root at s4slave ~]# id maurerp > uid=90036(TPLK\maurerp) gid=100(users) > Gruppen=100(users),3000048(TPLK\aerzte08$),3000038(TPLK\reserve09$),3000023( > TPLK\agfa),3000001(BUI...

Hello! I have 2 Samba 4 server (4.3.3) as VC and other Samba 4 (4.3) as Fileserver, until now all ok, but I'm one doubts, how to validate that in both servers the domain IDs of the users of this identical, a simple way to do this validation? I wanted to make sure it is a DC die fileserver has to go 100%. thank you

...rade to Samba-4.3.4 On 09/02/16 09:26, Mueller wrote: > Hello again, > no idea!? > > Both my DCs running now 4.3.4, but there is a strange behaviour, > Ex.: > First DC > root at s4master wingroup]# id maurerp > uid=90036(TPLK\maurerp) gid=100(users) > Gruppen=100(users),3000048(TPLK\schreiben),3000038(TPLK\orbis),3000023 > (TPLK\ > agfa),3000009(BUILTIN\users) > > Second DC > > [root at s4slave ~]# id maurerp > uid=90036(TPLK\maurerp) gid=100(users) > Gruppen=100(users),3000048(TPLK\aerzte08$),3000038(TPLK\reserve09$),30 > 00023( > TPLK\agfa...

.... Both DCs have the same ids. > On your memberservers this will be mapped by winbind(d) > EX: > > [root at s4master ~]# id tester > uid=90000(TPLK\tester) gid=100(users) > Gruppen=100(users),3000051(TPLK\TerminalServer > User),3000027(TPLK\Dienstplan),3000028(TPLK\Direktionv),3000048(TPLK\Schre > iben),3000045(TPLK\pflege),3000038(TPLK\orbis),3000023(TPLK\agfa),3000033( > TPLK\HS3) > > [root at s4slave ~]# id tester > uid=90000(TPLK\tester) gid=100(users) > Gruppen=100(users),3000051(TPLK\TerminalServer > User),3000027(TPLK\Dienstplan),3000028(TPLK\Direkti...

...d <user>*. For example, I remove the template shell option from smb.conf, restart samba-ad-dc.service and run the below command: samba-tool user add adam --given-name=Adam --surname=Cook > --login-shell=/bin/bash Then observe the below: root at DC:~# getent passwd adam > LAB\adam:*:3000048:100:Adam Cook:/home/LAB/adam:/bin/false Am I missing something? I'm conscious of giving all domain users by default a shell. I know I can limit SSH access by AD group but my train of thought is that if the --login-shell parameter exists in samba-tool then it could work somehow. Best, Adam

...this will be mapped by winbind(d) > >> EX: > >> > >> [root at s4master ~]# id tester > >> uid=90000(TPLK\tester) gid=100(users) > >> Gruppen=100(users),3000051(TPLK\TerminalServer > >> > User),3000027(TPLK\Dienstplan),3000028(TPLK\Direktionv),3000048(TPLK\Schre > >> > iben),3000045(TPLK\pflege),3000038(TPLK\orbis),3000023(TPLK\agfa),3000033( > >> TPLK\HS3) > >> > >> [root at s4slave ~]# id tester > >> uid=90000(TPLK\tester) gid=100(users) > >> Gruppen=100(users),3000051(TPLK\TerminalServe...

...t; >>>> > >>>> [root at s4master ~]# id tester > >>>> uid=90000(TPLK\tester) gid=100(users) > >>>> Gruppen=100(users),3000051(TPLK\TerminalServer > >>>> > >> > User),3000027(TPLK\Dienstplan),3000028(TPLK\Direktionv),3000048(TPLK\Schre > >> > iben),3000045(TPLK\pflege),3000038(TPLK\orbis),3000023(TPLK\agfa),3000033( > >>>> TPLK\HS3) > >>>> > >>>> [root at s4slave ~]# id tester > >>>> uid=90000(TPLK\tester) gid=100(users) > >>>> Grupp...

...;>>>> >>>>>> [root at s4master ~]# id tester >>>>>> uid=90000(TPLK\tester) gid=100(users) >>>>>> Gruppen=100(users),3000051(TPLK\TerminalServer >>>>>> >> User),3000027(TPLK\Dienstplan),3000028(TPLK\Direktionv),3000048(TPLK\Schre >> iben),3000045(TPLK\pflege),3000038(TPLK\orbis),3000023(TPLK\agfa),3000033( >>>>>> TPLK\HS3) >>>>>> >>>>>> [root at s4slave ~]# id tester >>>>>> uid=90000(TPLK\tester) gid=100(users) >>>>>>...

...ation operators:x:3000042: BUILTIN\incoming forest trust builders:x:3000043: BUILTIN\performance monitor users:x:3000044: BUILTIN\performance log users:x:3000045: BUILTIN\windows authorization access group:x:3000046: BUILTIN\terminal server license servers:x:3000047: BUILTIN\distributed com users:x:3000048: BUILTIN\iis_iusrs:x:3000049: BUILTIN\cryptographic operators:x:3000050: BUILTIN\event log readers:x:3000051: BUILTIN\certificate service dcom access:x:3000052: SAMDOM\cert publishers:x:3000053: SAMDOM \ras and ias servers:x:3000054: SAMDOM \allowed rodc password replication group:x:3000055: SAMDOM...