search for: reachfp

...re" read only = no [fbc$] path = /home/shared/fbc comment = "Family Bible College file share" read only = no ACL List: ====== root at fs01:~# getfacl /home/shared/staff/ getfacl: Removing leading '/' from absolute path names # file: home/shared/staff/ # owner: reachfp # group: administration # flags: ss- user::rwx user:reachfp:rwx group::rwx group:administration:rwx group:domain\040admins:rwx group:70028:rwx mask::rwx other::rwx default:user::rwx default:user:reachfp:rwx default:group::--- default:group:administration:rwx default:group:domain\040admins:rwx defau...

...y Bible College file share" >> read only = no >> >> >> >> ACL List: >> ====== >> root at fs01:~# getfacl /home/shared/staff/ >> getfacl: Removing leading '/' from absolute path names >> # file: home/shared/staff/ >> # owner: reachfp >> # group: administration >> # flags: ss- >> user::rwx >> user:reachfp:rwx >> group::rwx >> group:administration:rwx >> group:domain\040admins:rwx >> group:70028:rwx >> mask::rwx >> other::rwx >> default:user::rwx >> default:u...

...it. Now /srv is owned by root and the root group, as is /srv/samba, but they both have 755 for permissions. No ACLs exist at that level. root at ps01:~# getfacl /srv/samba/printer_drivers/ getfacl: Removing leading '/' from absolute path names # file: srv/samba/printer_drivers/ # owner: reachfp # group: domain\040admins # flags: ss- user::rwx user:reachfp:rwx group::rwx group:domain\040admins:rwx group:domain\040users:r-x group:domain\040computers:r-x mask::rwx other::--- default:user::rwx default:user:reachfp:rwx default:group::--- default:group:domain\040admins:rwx default:group:domain\...

I have a brand-new install of Debian 8 without systemd and a freshly-built Samba 4 install with issues. I created this as a standalone AD DC, setup group policies, etc and then took it to the client location. Now nothing works. I keep getting "RPC server unavailable" on Windows machines and trying to list shares on the DC itself results in NT_STATUS_INVALID_SID. I am lost as there are

I guess I should note that it seems like the high SIDs will resolve, except for 300000. Below is an example. root at dc01:~# l /var/lib/samba/sysvol/medarts.lan/ total 16 drwxrws---+ 4 MEDARTS\reachfp 3000000 4096 Oct 17 17:45 Policies drwxrws---+ 2 MEDARTS\reachfp 3000000 4096 Oct 17 17:45 scripts root at dc01:~# l /var/lib/samba/sysvol/medarts.lan/Policies total 16 drwxrws---+ 5 MEDARTS\reachfp MEDARTS\domain admins 4096 Oct 19 14:05 {31B2F340-016D-11D2-945F-00C04FB984F9} drwxrws---+ 5 MEDARTS...

...:27:37 -0400 Ryan Ashley via samba <samba at lists.samba.org> wrote: > I guess I should note that it seems like the high SIDs will resolve, > except for 300000. Below is an example. > > root at dc01:~# l /var/lib/samba/sysvol/medarts.lan/ > total 16 > drwxrws---+ 4 MEDARTS\reachfp 3000000 4096 Oct 17 17:45 Policies > drwxrws---+ 2 MEDARTS\reachfp 3000000 4096 Oct 17 17:45 scripts > root at dc01:~# l /var/lib/samba/sysvol/medarts.lan/Policies > total 16 > drwxrws---+ 5 MEDARTS\reachfp MEDARTS\domain admins 4096 Oct 19 14:05 > {31B2F340-016D-11D2-945F-00C04FB984...

...a samba <samba at lists.samba.org> wrote: > >> I guess I should note that it seems like the high SIDs will resolve, >> except for 300000. Below is an example. >> >> root at dc01:~# l /var/lib/samba/sysvol/medarts.lan/ >> total 16 >> drwxrws---+ 4 MEDARTS\reachfp 3000000 4096 Oct 17 17:45 Policies >> drwxrws---+ 2 MEDARTS\reachfp 3000000 4096 Oct 17 17:45 scripts >> root at dc01:~# l /var/lib/samba/sysvol/medarts.lan/Policies >> total 16 >> drwxrws---+ 5 MEDARTS\reachfp MEDARTS\domain admins 4096 Oct 19 14:05 >> {31B2F340-016D-...

On 03/07/15 15:58, Ryan Ashley wrote: > They left a PC on, so I got the info. The info pissed me off, but not > because of the issue. This time it worked flawlessly, but I got the > error from the event log from prior attempts. First, today's results. > > C:\Users\reachfp.KIGM>gpupdate > Updating Policy... > > User Policy update has completed successfully. > Computer Policy update has completed successfully. > > > C:\Users\reachfp.KIGM>gpupdate /force > Updating Policy... > > User Policy update has completed successfully. > Com...

On 03/07/15 15:18, Ryan Ashley wrote: > The only Unix client I can think of would be the Buffalo NAS. It runs > Samba3 and hosts various shares via SMB. DNS is handled by BIND9 on the > Samba4 DC. DNS does work and the domain name resolves to the IP address > of the server. DHCP is also handled on the DC. As for the GPO's, they're > in the correct place as far as I can tell.

They left a PC on, so I got the info. The info pissed me off, but not because of the issue. This time it worked flawlessly, but I got the error from the event log from prior attempts. First, today's results. C:\Users\reachfp.KIGM>gpupdate Updating Policy... User Policy update has completed successfully. Computer Policy update has completed successfully. C:\Users\reachfp.KIGM>gpupdate /force Updating Policy... User Policy update has completed successfully. Computer Policy update has completed successfully. C...

...3/07/15 15:58, Ryan Ashley wrote: >> They left a PC on, so I got the info. The info pissed me off, but not >> because of the issue. This time it worked flawlessly, but I got the >> error from the event log from prior attempts. First, today's results. >> >> C:\Users\reachfp.KIGM>gpupdate >> Updating Policy... >> >> User Policy update has completed successfully. >> Computer Policy update has completed successfully. >> >> >> C:\Users\reachfp.KIGM>gpupdate /force >> Updating Policy... >> >> User Policy upd...

On 6/3/2015 11:43 AM, Ryan Ashley wrote: > James, I cloned it using git. I installed it to a private partition > (/samba) back when I was first testing Samba4. It is in the path and > this worked for ages, but recently just stopped. No errors, no warnings, > nothing. Just dead. > > The GP in question is the default domain policy. I already tried > unlinking it and it fails on