search for: 2000513

Hi, When using AD authentication from a rhel8.1 environment with samba-4.10.4 installed, information on the primary group group01 set on the AD side for any user user01 cannot be obtained. [root @ rhel8_1 ~] # id user01 uid=2001107(user01) gid=2000513(domain users) groups=2000513(domain users),2001107(oec0814e),2001103(group01) If you perform the same operation on the same AD from the samba-3.6.23 rhel6.6 environment, you will get the correct information as follows: [root @ rhel6_6 ~] # id user01 uid=2001107(user01) gid=2001103(group01) groups=2...

...nt passwd or id, then you could try the unix tools > i.e. usermod -G urbanweb ADDOMAIN\\1001362 > > Rowland Greetings, Thank you for the response. the matching UNIX group exists. Been using local groups on Samba for years. # getent passwd "ADDOMAIN\\1001362" 1001362:*:2091888:2000513:Robert M Martel:/home/1001362:/usr/bin/bash wbinfo returns useful information # wbinfo -i 1001362 1001362:*:2091888:2000513:Robert M Martel:/home/1001362:/usr/bin/bash I can "su" to an AD user without a problem. I can access shared folders as that user, I just cant add anyone to a s...

...or very easy-to-understand and courteous advice. I reread your initial post and noticed something that I missed earlier, you had in smb.conf: ??????? idmap uid = 16777216-33554431 ??????? idmap gid = 16777216-33554431 Yet, you were getting results like this: id user01 uid=2001107(user01) gid=2000513(domain users) groups=2000513(domain users),2001107(oec0814e),2001103(group01) '2000513' is less than '16777216' Are you sure that you do not have sssd installed ? On top of the Samba packages you have installed, I would also expect: samba.x86_64 samba-client-libs samba-common s...

...1362 >>> >>> Rowland >> Greetings, >> >> Thank you for the response. >> >> the matching UNIX group exists. Been using local groups on Samba for >> years. >> >> # getent passwd "ADDOMAIN\\1001362" >> 1001362:*:2091888:2000513:Robert M Martel:/home/1001362:/usr/bin/bash >> >> wbinfo returns useful information >> >> # wbinfo -i 1001362 >> 1001362:*:2091888:2000513:Robert M Martel:/home/1001362:/usr/bin/bash >> >> >> I can "su" to an AD user without a problem. >&...

Additionally if I authenticate to user using wbinfo -a it seems to works correctly: root at root:~$ id DEV2+guest uid=2000501(DEV2+guest) gid=2000513(DEV2+domain users) groups=2000513(DEV2+domain users),2000501(DEV2+guest),2000514(DEV2+domain guests) root at root:~$ wbinfo -a DEV2+guest Enter DEV2+guest's password: plaintext password authentication succeeded Enter DEV2+guest's password: challenge/response password authentication succeed...

...gt;> Greetings, > >> > >> Thank you for the response. > >> > >> the matching UNIX group exists. Been using local groups on Samba > >> for years. > >> > >> # getent passwd "ADDOMAIN\\1001362" > >> 1001362:*:2091888:2000513:Robert M > >> Martel:/home/1001362:/usr/bin/bash > >> > >> wbinfo returns useful information > >> > >> # wbinfo -i 1001362 > >> 1001362:*:2091888:2000513:Robert M > >> Martel:/home/1001362:/usr/bin/bash > >> > >> >...

...s is not the point because that's true and known, the problem seems that samba simply discard or not manage to apply these sticky bits at all ( at least regarding latest v4.7.4 ), I grabbed from the log following excerpt: [2018/01/30 19:05:17.994374,  5, pid=3294, effective(2002158, 2000513), real(2002158, 0)] ../source3/smbd/dosmode.c:206(unix_mode)   unix_mode: unix_mode(sharetest/A/X/New folder (10)) returning 02770 ... [2018/01/30 19:05:18.064582,  5, pid=3294, effective(2002158, 2000513), real(2002158, 0)] ../source3/smbd/dosmode.c:206(unix_mode)   unix_mode...

...testpermissions2" >> /testfile bash: /testfile: Permission denied On 30.05.2017 16:02, aluno3 at poczta.onet.pl wrote: > Additionally if I authenticate to user using wbinfo -a it seems to works > correctly: > > root at root:~$ id DEV2+guest uid=2000501(DEV2+guest) > gid=2000513(DEV2+domain users) groups=2000513(DEV2+domain > users),2000501(DEV2+guest),2000514(DEV2+domain guests) > > root at root:~$ wbinfo -a DEV2+guest > Enter DEV2+guest's password: > plaintext password authentication succeeded > Enter DEV2+guest's password: > challenge/respo...

Greetings, I have Samba 4.4.7 running on several Sparc boxes running Solaris 9 as member servers in an Active Directory environment. (I do not control the AD configuration) I am able to connect to the servers using windows clients and smbclient - the problem I have run into is when I try to add domain users to local groups on the Samba servers I am told the users do not exist. As these

On 29.05.2017 12:03, Rowland Penny via samba wrote: > On Mon, 29 May 2017 11:33:21 +0200 > aluno3--- via samba <samba at lists.samba.org> wrote: > >> My configuration for idmap backend is: >> >> idmap config dev2 : range = 65536-19999999 >> idmap config dev2 : backend = rid >> idmap config * : range = 20000000-39999999 >> idmap config * : backend

...details (set using chown and chmod)* /srv/samba/users/ drwxrwx---+ 2 root FTLC\domain admins. /srv/samba/shares/Operations/ drwxrwx---. 2 root FTLC\domain admins *# Output from getfacl* # file: users/ # owner: root # group: FTLC\134domain\040admins user::rwx user:root:rwx user:2000512:rwx user:2000513:r-x group::rwx group:FTLC\134domain\040admins:rwx group:FTLC\134domain\040users:r-x mask::rwx other::--- default:user::rwx default:user:root:rwx default:user:2000512:rwx default:group::--- default:group:FTLC\134domain\040admins:rwx default:mask::rwx default:other::--- # file: shares/Operations/ #...

...rict,multiuser,domain=CARLSON.LAB,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.52,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,noperm,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,_netdev) CARLSON\peter at u2gui:~$ id uid=2001107(CARLSON\peter) gid=2000513(CARLSON\domain users) groups=2000513(CARLSON\domain users),10000(BUILTIN\administrators),10001(BUILTIN\users),2000512(CARLSON\domain admins),2000572(CARLSON\denied rodc password replication group),2001107(CARLSON\peter),2001108(CARLSON\linux admins),2001120(CARLSON\videoadmin),2...

...config TJSC : range = 2000000-2999999 idmap config TJSC : backend = rid This will take any AD users (and groups), extract the RID and then calculate the Unix ID using the lower range, so from what you have posted, I am very sure that 'getent group Domain\ Users' will return the ID '2000513'. So to cut to a shorter version, create your users in AD and delete them from /etc/passwd. Your way is not supported. Rowland

...rator > > > TC83\administrator:*:1200500:1200513::/home/administrator at TC83 > :/bin/bash > > > > And here's the same config on a samba 4.9 system: > > > > [root at kvm7246-vm008 ~]# wbinfo -i TC84\\administrator > > > TC84\administrator:*:2000500:2000513::/home/administrator at TC84 > :/bin/bash > > [root at kvm7246-vm008 ~]# wbinfo -i TC83\\administrator > > TC83\administrator:*:10000:10000::/home/administrator at TC83:/bin/bash > > > > The UID 10000 is not within the idmap configured range! > > > > I looked...

...ferent across domains, > > but they > > shouldn't change if Samba is upgraded and this is what has > > happened for > > the OP. > Right, the mappings in the samba 4.8 case quoted look right to me too. What I don'd understand is this: TC84\administrator:*:2000500:2000513::/home/administrator at TC84:/bin/bash TC83\administrator:*:10000:10000::/home/administrator at TC83:/bin/bash I thought that because I have "idmap config * : range = 1000000-19999999", that the lowest UID that idmap would allocate would be 1000000 (but here we have 10,000 which is much...

Hello samba gurus, I have a couple of questions regarding Linux file systems, and their ability to mimic NTFS, and the other question is regarding winbind and its uncanny ability to virtually lock up a samba AD member server once connectivity to the AD is lost. I apologize if anyone gets annoyed by this question. Environment: I am using samba 3.2 with XFS+ACL support joined as a AD domain member

...ot at kvm7246-vm005 ~]# wbinfo -i TC83\\administrator > TC83\administrator:*:1200500:1200513::/home/administrator at TC83:/bin/bash > > And here's the same config on a samba 4.9 system: > > [root at kvm7246-vm008 ~]# wbinfo -i TC84\\administrator > TC84\administrator:*:2000500:2000513::/home/administrator at TC84:/bin/bash > [root at kvm7246-vm008 ~]# wbinfo -i TC83\\administrator > TC83\administrator:*:10000:10000::/home/administrator at TC83:/bin/bash > > The UID 10000 is not within the idmap configured range! > > I looked a the idmap_autorid(8) manpage, and...

...9999 idmap config QA2K3192:base_rid = 0 idmap config QA2K3192:backend = rid And had the following results: Linux:~ # wbinfo --group-info='qa2k3192\domain users' QA2K3192\domain users:x:1000513 Linux:~ # wbinfo --group-info='qa2k3sub192\domain users' QA2K3SUB192\domain users:x:2000513 Which is correct and reports the correct information consistently for this configuration. ------------------------------------------------------------------------------------------------ We do not obtain the same idmap results with the same idmap backend (RID) with samba 3.4: idmap backend =...

...0000-2999999 > idmap config TJSC : backend = rid > > This will take any AD users (and groups), extract the RID and then > calculate the Unix ID using the lower range, so from what you have > posted, I am very sure that 'getent group Domain\ Users' will return the > ID '2000513'. > > So to cut to a shorter version, create your users in AD and delete them > from /etc/passwd. > > Your way is not supported. > > Rowland > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists...

...ey >> > shouldn't change if Samba is upgraded and this is what has >> > happened for >> > the OP. >> > > Right, the mappings in the samba 4.8 case quoted look right to me too. > What I don'd understand is this: > > TC84\administrator:*:2000500:2000513::/home/administrator at TC84:/bin/bash > TC83\administrator:*:10000:10000::/home/administrator at TC83:/bin/bash > > I thought that because I have "idmap config * : range = 1000000-19999999", > that the lowest UID that idmap would allocate would be 1000000 (but here we > ha...