search for: 30033

...> # file: Policies/{0F1E5B10-3640-4FFE-AA6B-5DE4CFF73625} > > # owner: 10060 > > # group: 30028 > > user::rwx > > user:10060:rwx > > user:3000002:rwx > > user:3000010:r-x > > group::rwx > > group:30028:rwx > > group:30032:r-x > > group:30033:rwx > > group:3000002:rwx > > group:3000010:r-x > > mask::rwx > > other::--- > > default:user::rwx > > default:user:10060:rwx > > default:user:3000002:rwx > > default:user:3000010:r-x > > default:group::--- > > default:group:30028:rwx >...

I'm having problems with GPO in Samba 4.2.1 I created a GPO to Block Control Panel and applied in my Domain OU. In desktop client I typed "gpupdate /force" and appear a success message that to ask reboot my system. After rebuot the GPO don't work. Other GPOs as WSUS update, Wallpaper and others, don't work too. Following is the result of command: GPRESULT /H

Hi Rowland Following the results to: *USER:* wbinfo --uid-info=10060: bacci:*:10060:30049:bacci:/home/EMPRESA/bacci:/bin/false *GROUP:* wbinfo --gid-info=30028: Domain Admins wbinfo --gid-info=30032: Domain Users wbinfo --gid-info=30033: Enterprise Admins "I don't see user:3000003" root at dc1:~# wbinfo -G 3000003 S-1-5-11 root at dc1:~# wbinfo -s S-1-5-11 failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND Could not lookup sid S-1-5-11 I have in my network two DC (Samba 4) and one member File Server (Samba 4)...

...01 > > Following the result of command: > > # file: Policies/{0F1E5B10-3640-4FFE-AA6B-5DE4CFF73625} > # owner: 10060 > # group: 30028 > user::rwx > user:10060:rwx > user:3000002:rwx > user:3000010:r-x > group::rwx > group:30028:rwx > group:30032:r-x > group:30033:rwx > group:3000002:rwx > group:3000010:r-x > mask::rwx > other::--- > default:user::rwx > default:user:10060:rwx > default:user:3000002:rwx > default:user:3000010:r-x > default:group::--- > default:group:30028:rwx > default:group:30032:r-x > default:group:30033:...

Hi list, I just received a storage array and created a 3TB LUN with a block/sector size on the disks of 4096. When I boot the our centos-4.4 box attached to this array I get the "unsupported sector size 4096" message: Remounting root filesystem in read-write mode: [ OK ] ERROR: unsupported sector size 4096 on /dev/sda. No RAID disks Setting up Logical Volume Management: [ OK ]

...Using closest match instead (Spanish keyboard layout) for scancode mapping. Please define your layout in windows/x11drv/keyboard.c and submit them to us for inclusion into future Wine releases. See the Wine User Guide, chapter "Keyboard" for more information. err:win:WIN_FindWndPtr window 30033 belongs to other process err:win:WIN_FindWndPtr window 20035 belongs to other process err:win:WIN_FindWndPtr window 20030 belongs to other process err:win:WIN_FindWndPtr window 50027 belongs to other process err:win:WIN_FindWndPtr window 5002b belongs to other process err:win:WIN_FindWndPtr window...

...-auth account required pam_stack.so service=system-auth session required pam_mkhomedir.so skel=/etc/skel umask=0002 session required pam_stack.so service=system-auth password required pam_stack.so service=system-auth -- Fabio Corazza - Prosa s.r.l. Via Polanzani, 74 - 30033 Noale Venice - Italy Phone: +39.041.5897009 - e-mail: corazza@prosa.com

...need to give 'Domain Admins' a gidNumber to be visible to Unix, but if > you do, it looses the 'ID_TYPE_BOTH' from idmap.ldb that means it can > own dirs & files in sysvol. > > > > > wbinfo --gid-info=30032: Domain Users > > > > wbinfo --gid-info=30033: Enterprise Admins > > > > > > "I don't see user:3000003" > > > > root at dc1:~# wbinfo -G 3000003 > > S-1-5-11 > > > > root at dc1:~# wbinfo -s S-1-5-11 > > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > > Could not...

...bit of a catch 22 problem, you need to give 'Domain Admins' a gidNumber to be visible to Unix, but if you do, it looses the 'ID_TYPE_BOTH' from idmap.ldb that means it can own dirs & files in sysvol. > > wbinfo --gid-info=30032: Domain Users > > wbinfo --gid-info=30033: Enterprise Admins > > > "I don't see user:3000003" > > root at dc1:~# wbinfo -G 3000003 > S-1-5-11 > > root at dc1:~# wbinfo -s S-1-5-11 > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > Could not lookup sid S-1-5-11 > You will need to l...

...; a gidNumber to be visible to Unix, but if > > you do, it looses the 'ID_TYPE_BOTH' from idmap.ldb that means it can > > own dirs & files in sysvol. > > > > > > > > wbinfo --gid-info=30032: Domain Users > > > > > > wbinfo --gid-info=30033: Enterprise Admins > > > > > > > > > "I don't see user:3000003" > > > > > > root at dc1:~# wbinfo -G 3000003 > > > S-1-5-11 > > > > > > root at dc1:~# wbinfo -s S-1-5-11 > > > failed to call wbcLookupSid:...

...37403 e95bd520 e9b5e000 0 103 103 000084 3 piperd e9440540 cron 31158 e95bc680 e9ba8000 8 727 727 004085 2 overchan 31157 e95bcea0 e9b68000 8 727 727 004084 3 sbwait e554e888 perl 31156 e95c0ac0 e95e2000 8 727 727 004484 2 innfeed 30033 e95bc340 e9bc1000 8 30031 30031 004086 3 ttyin c882b430 zsh 30031 e95c02a0 e9907000 0 30021 30031 004086 3 wait e95c02a0 sh 30021 e33fe380 e95b6000 0 30019 30021 2004086 3 pause e95b6260 zsh 30019 e95bc820 e9b99000 0 992 30019 000584 2 sshd 6279 e33fe040 e...

...; a gidNumber to be visible to Unix, but if > > you do, it looses the 'ID_TYPE_BOTH' from idmap.ldb that means it can > > own dirs & files in sysvol. > > > > > > > > wbinfo --gid-info=30032: Domain Users > > > > > > wbinfo --gid-info=30033: Enterprise Admins > > > > > > > > > "I don't see user:3000003" > > > > > > root at dc1:~# wbinfo -G 3000003 > > > S-1-5-11 > > > > > > root at dc1:~# wbinfo -s S-1-5-11 > > > failed to call wbcLookupSid:...