similar to: Samba 4: 'Access denied' error when accessing user profile during logon

Hai, Now, i did not know you used the DC for the profiles here but yes it looks good. Small comment on point 3 and 4. 3) Its good, you might notice a few more rights there compaired to what i posted, thats because you have your profiles on the DC but the settings are good. 4) yes, the security is ok, i like the higher security setting and try to mimic the windows settings as much as

Hello Louis, In fact, the shares mentioned in my original messages are used in Windows-only. The accounts, however, are used in both Windows and Unix-type environments (we have quite a zoo of OSes in active use); so we actually use the Posix part of accounts for attributes and Kerberos component to authenticate in all non-Windows use. So my primary intent is to make the homes/profiles shares

Hai, Sorry to say but.. > The solution (following the default how-to directories structure): No, the solution is to setup correctly. Just do a a small test here to see if its all correct. With a windows computer, browse to \\server Right klik the profiles share, check security. If this is set correct, the user should not be able to see the rights. Repaet, now as Adminsitrator.

I have a Samba AD running Samba 4.7.5. Everything was working fine, when, seemingly out of the blue, the users started to be denied access to all shares. If I try from a Windows 7 or Windows 10 machine, logged in as a user in "Domain Uses", I get: "Windows cannot access \\server-name\share_name. You do not have permission to access \\server-name\share_name" If I use

L.P.H. van Belle via samba писал 2018-12-04 15:59: > Hai, > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens >> Konstantin Boyandin via samba >> Verzonden: dinsdag 4 december 2018 6:35 >> Aan: samba at lists.samba.org >> Onderwerp: [Samba] WinbinD no longer available in Samba 4.7.6 >> >>

> > What is in the username map ? > !root = NAME\Administrator NAME\administrator Administrator administrator

On Tue, Jun 13, 2017 at 1:17 PM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Tue, 13 Jun 2017 12:25:32 +0200 > Neil <nwilson123 at gmail.com> wrote: > > > Hi Rowland, > > > > Thank you for the reply and info. > > > > On Tue, Jun 13, 2017 at 11:19 AM, Rowland Penny <rpenny at samba.org> > > wrote: > > >

On 12/03/18 11:28, Rowland Penny via samba wrote: > On Mon, 12 Mar 2018 11:11:44 +0000 > Sebastian Arcus via samba <samba at lists.samba.org> wrote: > >> I have a Samba AD running Samba 4.7.5. Everything was working fine, >> when, seemingly out of the blue, the users started to be denied >> access to all shares. If I try from a Windows 7 or Windows 10 >>

> > On the file serever: > > Collected config --- 2019-07-03-10:27 ----------- > > > > Hostname: srv > > DNS Domain: a.b.hu > > FQDN: srv.a.b.hu > > ipaddress: 10.0.3.15 192.168.0.8 > > ----------- > > Samba is running as a Unix domain member > > ----------- > > > > This computer is running Debian 10.0 x86_64 > >

Hi all, Sorry to repost about this same issue once again, but I'm really at a complete loss as to how to solve the problem with ownership being changed after I've set it. I've set ownership as follows... ( set this by chmod -R 0770 HR, as well as chgroup -R HR-Group, I then signed into a Windows PC that was part of the domain, went to computer management as per the WIKI and chose

On Tue, 4 Dec 2018 09:59:14 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, > > > -----Oorspronkelijk bericht----- > > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > > Konstantin Boyandin via samba > > Verzonden: dinsdag 4 december 2018 6:35 > > Aan: samba at lists.samba.org > > Onderwerp:

On Tue, 04 Dec 2018 16:44:55 +0700 Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > Rowland Penny via samba писал 2018-12-04 16:28: > > On Tue, 4 Dec 2018 09:59:14 +0100 > > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > > > >> Hai, > >> > >> > -----Oorspronkelijk bericht----- >

Greetings! I'm running domain member fileservers on Samba 4.3.6.. During my backup window (backups are performed via Bacula, running on the fileserver) I tend to receive spurts of the following log message: Apr 10 16:55:18 smbfs1 winbindd[2376]: [2016/04/10 16:55:18.111192, 0] ../source3/winbindd/winbindd_group.c:45(fill_grent) Apr 10 16:55:18 smbfs1 winbindd[2376]: Failed to find domain

Hello, Using Samba 4.7.6 (from standard repository) on Ubuntu 18.04. After recent update, winbind failed to update, until I disabled it (it didn't start anyway). When run as # winbindd -d 9 -i it prints in the end: server role = 'active directory domain controller' not compatible with running the winbindd binary. You should start 'samba' instead, and it will control

Hello! I am following the how to https://wiki.samba.org/index.php/User_home_drives But even though there reported a process for User X does not access the home of Y User, this is happening root at fileserver:/srv/samba# getfacl home/ # file: home/ # owner: root # group: root user::rwx user:root:rwx user:administrator:rwx group::r-x group:root:r-x group:5007:r-x group:domain\040admins:rwx

On 12/03/18 12:56, Rowland Penny via samba wrote: > On Mon, 12 Mar 2018 11:36:47 +0000 > Sebastian Arcus via samba <samba at lists.samba.org> wrote: > >> >> On 12/03/18 11:28, Rowland Penny via samba wrote: >>> On Mon, 12 Mar 2018 11:11:44 +0000 >>> Sebastian Arcus via samba <samba at lists.samba.org> wrote: >>> >>>> I have a

Hi, sometimes my Roaming Profile gets buggy and i cant use the Reboot Shutdown ... function all other works. When i make a new users.v6 folder the Profile works again very well. I tried all GPOs i found for energy settings but nothing helps if the Profile is broken. Only delete and make a new one works Samba 4.11.2 Win10 1803-1903 any ideas? or Workarounds? Ren? Mit freundlichen Gr??en,

Rowland Penny via samba писал 2018-12-04 17:17: > On Tue, 04 Dec 2018 16:45:43 +0700 > Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > >> >> Are there possibly missing some winbind settings (the smb.conf has >> been generated by domain upgrade process). >> > > Sorry, but I do not believe that is true: True. The configuration

I believe I have found either a bug or something I do not understand. I recently had a file-share issue and the resolution was to set the "others" permissions to 5, read and execute. The problem with this is that once I am in Windows on a workstation, this appears to allow "Everyone", "CREATOR OWNER", and "CREATOR GROUP" access. We normally setup our

On Thu, 14 Jun 2018 09:39:46 +0200 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > And i did read the Comment to for Rowland below, > On debian you need : > libnss-winbind libpam-winbind to be installed. > I think you miss one of these. They are the glue that connects Samba to nsswitch and allows 'getent passwd username' to work. Without