search for: 3000017

Hello, I am having problem setting permission on shared folder: the folder is?datasamba/common and after I set full permission for a user itester (3000017) and also?tester (3000018), I could see that it is only granting r-x to those users. but I could see from the default permissions that they have rwx. getfacl /datasamba/common # file: datasamba/common # owner: root # group: users # flags: sst user::rwx user:root:rwx group::--- group:wheel:r-x gr...

...t gmail.com> wrote: > Hi Alberto, > > No idea about your issue as I'm playing with Samba to build AD only, I can > only tell you that I did tested on my Samba AD DC and I can use upper, > lower or mixed case in user names: > > dc108:/opt/initial_setup# id mtest > uid=3000017(AD\mtest) gid=3000018(AD\not_system_users) > groupes=3000018(AD\not_system_users),3000017(AD\mtest) > dc108:/opt/initial_setup# id mTest > uid=3000017(AD\mtest) gid=3000018(AD\not_system_users) > groupes=3000018(AD\not_system_users),3000017(AD\mtest) > dc108:/opt/initial_setup# id MT...

...ervice() failed! I checked the rights which are identically on both nodes. Accessing as admin works but not as user. Rights on the working DC: root at dc01:/var/lib/samba# getfacl sysvol/ # file: sysvol/ # owner: root # group: 3000002 user::rwx user:root:rwx user:3000002:rwx user:3000017:r-x user:3000018:rwx user:3000019:r-x group::rwx group:3000002:rwx group:3000017:r-x group:3000018:rwx group:3000019:r-x mask::rwx other::--- default:user::rwx default:user:root:rwx default:user:3000002:rwx default:user:3000017:r-x default:user:3000018:rwx default:user:3000019:r-x d...

I did some experimenting on my raspberry pi with samba-4.4.2 as AD server (fresh install, no upgrade), and adding a new user: samba-tool user add grepit --gid-number=513 --login-shell=/bin/bash and then checking it: root at pi6lan:/etc# wbinfo -i grepit ROEST\grepit:*:3000017:100::/home/grepit:/bin/bash root at pi6lan:/etc# id grepit uid=3000017(ROEST\grepit) gid=100(users) groups=100(users),3000017(ROEST\grepit),3000009(BUILTIN\users) my new user's primary group is 100 ! Why? My smb.conf is really basic: [global] netbios name = PI6LAN realm = ROEST.INTERN wo...

Hi, is time to get help. I have a DOMAIN with samba3.6.23-9.el5_11 Centos 5.11 x64 Windows XP/Win7/Win8.1 domain no issues.(x32/x64) I have even 2 Linux Centos 5.x in my domain x64 Now, I have add 1 Centos 6.x x64 updated. Samba 3.6.23-35.el6_8 I had setup LDAP client on this server to get users/groups and add to my domain with net rpc join, no issue. I can see the server on my domain no

...ace_to_acl) ? add_current_ace_to_acl: malformed ACL in file ACL ! Deny entry after Allow entry. Failing to set on file test. [2012/10/10 02:41:47.861209, ?0] ../source3/modules/vfs_posixacl.c:351(smb_acl_to_posix) ? smb_acl_to_posix: ACL group:users:--- ? other::--- ? user::rwx ? group::--- ? group:3000017:rwx ? user:root:rwx ? group:users:--- ? mask::rwx ? ?is invalid for set (Success) [2012/10/10 02:42:01.876497, ?0] ../source3/modules/vfs_posixacl.c:351(smb_acl_to_posix) ? smb_acl_to_posix: ACL group:users:--- ? other::--- ? user::rwx ? group::--- ? group:3000017:rwx ? user:root:rwx ? group:users:...

Hi Alberto, No idea about your issue as I'm playing with Samba to build AD only, I can only tell you that I did tested on my Samba AD DC and I can use upper, lower or mixed case in user names: dc108:/opt/initial_setup# id mtest uid=3000017(AD\mtest) gid=3000018(AD\not_system_users) groupes=3000018(AD\not_system_users),3000017(AD\mtest) dc108:/opt/initial_setup# id mTest uid=3000017(AD\mtest) gid=3000018(AD\not_system_users) groupes=3000018(AD\not_system_users),3000017(AD\mtest) dc108:/opt/initial_setup# id MTEST uid=3000017(AD\mtest)...

...Hi Alberto, >> >> No idea about your issue as I'm playing with Samba to build AD only, I >> can only tell you that I did tested on my Samba AD DC and I can use upper, >> lower or mixed case in user names: >> >> dc108:/opt/initial_setup# id mtest >> uid=3000017(AD\mtest) gid=3000018(AD\not_system_users) >> groupes=3000018(AD\not_system_users),3000017(AD\mtest) >> dc108:/opt/initial_setup# id mTest >> uid=3000017(AD\mtest) gid=3000018(AD\not_system_users) >> groupes=3000018(AD\not_system_users),3000017(AD\mtest) >> dc108:/opt/...

...x default:group:3000005:rwx default:group:3000011:r-x default:group:3000018:rwx default:group:3000019:r-x default:mask::rwx default:other::--- dc2 (bdc) # file: {31B2F340-016D-11D2-945F-00C04FB984F9}/ # owner: 3000005 # group: 3000005 user::rwx user:root:rwx user:3000000:rwx user:3000011:r-x user:3000017:r-x user:3000018:rwx group::--- group:3000000:rwx group:3000011:r-x group:3000017:r-x group:3000018:rwx mask::rwx other::--- default:user::rwx default:user:root:rwx default:user:3000000:rwx default:user:3000011:r-x default:user:3000017:r-x default:user:3000018:rwx default:group::--- default:group:3...

...read only = No I have also setup ntp like howto. At this point, in this test environment, all work fine, I can manage users, groups and dns entry, and join for test some windows client to it, the new samba users are recognized from Linux: [ root at fedora-addc ~]# id ospite uid=3000017(SOLINOS\ospite) gid=100(users) gruppi=100(users),3000017(SOLINOS\ospite),3000009(BUILTIN\users) Now my question is: There are other thinks I must to do on AD DC? What parameter is better add to smb.conf? Why administrator is mapped like root?: [ root at fedora-addc ~]# id adm...

...roup: 3000000 --> dn: CN=S-1-5-32-544 >>>> user::rwx >>>> user:root:rwx >>>> user:3000000:rwx --> dn: CN=S-1-5-32-544 >>>> user:3000009:r-x --> dn: CN=S-1-5-11 >>>> user:3000016:r-x --> dn: CN=S-1-5-32-549 >>>> user:3000017:rwx --> dn: CN=S-1-5-18 >>>> group::rwx >>>> group:3000000:rwx --> dn: CN=S-1-5-32-544 >>>> group:3000009:r-x --> dn: CN=S-1-5-11 >>>> group:3000016:r-x --> dn: CN=S-1-5-32-549 >>>> group:3000017:rwx --> dn: CN=S-1-5-18 >...

...pi with samba-4.4.2 as AD >> server (fresh install, no upgrade), and adding a new user: >> >> samba-tool user add grepit --gid-number=513 --login-shell=/bin/bash >> >> and then checking it: >> >> root at pi6lan:/etc# wbinfo -i grepit >> ROEST\grepit:*:3000017:100::/home/grepit:/bin/bash >> >> root at pi6lan:/etc# id grepit >> uid=3000017(ROEST\grepit) gid=100(users) >> groups=100(users),3000017(ROEST\grepit),3000009(BUILTIN\users) >> >> my new user's primary group is 100 ! Why? >> >> My smb.conf is rea...

...ction of home drive, etc.)? > > > Regards, > Marc hi, i see nothing in the eventviewer, and no errors in the samba logs. With samba 4.1.17 i can see a lot of rpc commands: ... 100.1.254.101 (ipv4:100.1.254.101:56215) connect to service IPC$ initially as user KLINGONS\PRAXIS$ (uid=3000017, gid=3000018) (pid 3787) api_pipe_bind_req: winreg -> winreg rpc service check_bind_req for \winreg check_bind_req: winreg -> winreg rpc service ldb_wrap open of secrets.ldb check_bind_req for \winreg check_bind_req: winreg -> winreg rpc service ldb_wrap open of privilege.ldb...

...amba/sysvol/ >> # owner: root >> # group: 3000000 --> dn: CN=S-1-5-32-544 >> user::rwx >> user:root:rwx >> user:3000000:rwx --> dn: CN=S-1-5-32-544 >> user:3000009:r-x --> dn: CN=S-1-5-11 >> user:3000016:r-x --> dn: CN=S-1-5-32-549 >> user:3000017:rwx --> dn: CN=S-1-5-18 >> group::rwx >> group:3000000:rwx --> dn: CN=S-1-5-32-544 >> group:3000009:r-x --> dn: CN=S-1-5-11 >> group:3000016:r-x --> dn: CN=S-1-5-32-549 >> group:3000017:rwx --> dn: CN=S-1-5-18 >> mask::rwx >> other::--- >&...

...;>>>> user::rwx >>>>>> user:root:rwx >>>>>> user:3000000:rwx --> dn: CN=S-1-5-32-544 >>>>>> user:3000009:r-x --> dn: CN=S-1-5-11 >>>>>> user:3000016:r-x --> dn: CN=S-1-5-32-549 >>>>>> user:3000017:rwx --> dn: CN=S-1-5-18 >>>>>> group::rwx >>>>>> group:3000000:rwx --> dn: CN=S-1-5-32-544 >>>>>> group:3000009:r-x --> dn: CN=S-1-5-11 >>>>>> group:3000016:r-x --> dn: CN=S-1-5-32-549 >>>>>> group...

...dded the following parameters in the global-Section of /etc/samba/smb.conf: winbind nss info = rfc2307 idmap_ldb:use rfc2307 = yes Also I set the attributes for a test-user (called tim) with some values. But when calling "getent passwd" I got the following result: ... SHADOW\tim:*:3000017:100:Tim Testinger:/home/SHADOW/tim:/bin/false So it seems that winbind is ignoring AD attributes. Is this a bug or did I misconfigure my samba installation? Best Regards Markus

...But that's when I don't get the expected ACL inheritance. I just trimmed the share definition down again to the above, and when I created a dir, the mask kicks in again: # file: test3 # owner: root # group: HEBI\\domain\040users # flags: -s- user::rwx user:root:rwx #effective:r-x user:3000017:r-x group::rwx #effective:r-x group:HEBI\\domain\040users:rwx #effective:r-x group:HEBI\\domain\040computers:r-x mask::r-x other::--- default:user::rwx default:user:root:rwx default:user:3000017:r-x default:group::rwx default:group:HEBI\\domain\040users:rwx default:group:HEBI\\domain\040computers...

...e experimenting on my raspberry pi with samba-4.4.2 as AD > server (fresh install, no upgrade), and adding a new user: > > samba-tool user add grepit --gid-number=513 --login-shell=/bin/bash > > and then checking it: > > root at pi6lan:/etc# wbinfo -i grepit > ROEST\grepit:*:3000017:100::/home/grepit:/bin/bash > > root at pi6lan:/etc# id grepit > uid=3000017(ROEST\grepit) gid=100(users) > groups=100(users),3000017(ROEST\grepit),3000009(BUILTIN\users) > > my new user's primary group is 100 ! Why? > > My smb.conf is really basic: > > [global] &g...

...r: root >>> # group: 3000000 --> dn: CN=S-1-5-32-544 >>> user::rwx >>> user:root:rwx >>> user:3000000:rwx --> dn: CN=S-1-5-32-544 >>> user:3000009:r-x --> dn: CN=S-1-5-11 >>> user:3000016:r-x --> dn: CN=S-1-5-32-549 >>> user:3000017:rwx --> dn: CN=S-1-5-18 >>> group::rwx >>> group:3000000:rwx --> dn: CN=S-1-5-32-544 >>> group:3000009:r-x --> dn: CN=S-1-5-11 >>> group:3000016:r-x --> dn: CN=S-1-5-32-549 >>> group:3000017:rwx --> dn: CN=S-1-5-18 >>> mask::rwx &...

...Removing leading '/' from absolute path names # file: var/lib/samba/sysvol/ # owner: root # group: 3000000 --> dn: CN=S-1-5-32-544 user::rwx user:root:rwx user:3000000:rwx --> dn: CN=S-1-5-32-544 user:3000009:r-x --> dn: CN=S-1-5-11 user:3000016:r-x --> dn: CN=S-1-5-32-549 user:3000017:rwx --> dn: CN=S-1-5-18 group::rwx group:3000000:rwx --> dn: CN=S-1-5-32-544 group:3000009:r-x --> dn: CN=S-1-5-11 group:3000016:r-x --> dn: CN=S-1-5-32-549 group:3000017:rwx --> dn: CN=S-1-5-18 mask::rwx other::--- default:user::rwx default:user:root:rwx default:user:3000000:rwx --&...