similar to: Delegating administrative permissions via CLI

hi , thank's for your reply . no , current DC doesn't have that GUID: samba-tool spn list zimbra$ zimbra$ ... ldap/3ecb2a51-b21d-4bef-84ed-700db7963ff4._msdcs.domain.lan samba-tool spn list landc$ landc$ ... ldap/5bf8cf1f-1e35-40c6-a20d-0abc88238d92._msdcs.domain.lan that GUID is of the machine we are trying to join to: samba-tool spn list nextcloud$ nextcloud$ ...

> samba-tool domain: no such subcommand: provision Are you sure there's no typo or hidden character? provision command is still there in 4.18.2 :) # samba-tool domain provision ERROR: No domain set! -- Lorenzo Milesi - lorenzo.milesi at yetopen.com CTO @ YetOpen Srl Corso Martiri della Liberazione 114 - 23900 Lecco - ITALY - | 4801 Glenwood Avenue - Suite 200 - Raleigh, NC 27612 - USA

> Yes you can use the Ubuntu 22.04 packages if you really must, but this > will only get you Samba 4.15.3 > On the other hand, Using Samba from backports on Debian bullseye will > get you 4.17.8 and is, in my opinion, easier to use. Both for Debian and Ubuntu it's better to use Michael repos, to get consistent minor release updates: http://www.corpit.ru/mjt/packages/samba/README

> As I understand it, you only need Michael's repo for Ubuntu, The Debian > backport repo gets updated with the same Samba packages as his repo (or > is it the other way around ?). He is the Debian Samba maintainer. With the repos you can select several minor versions (from 4.16 to .18), while backports only contains the latest (currently 4.18) IIRC. -- Lorenzo Milesi -

> That all smells quite similar to what I were seeing > here before, and what someone else were seeing too, > all with 4.17[.4]. This famouse WERR_FILE_NOT_FOUND > error too. We upgraded one more domain, and in the hope to avoid this error, we remained on 4.16. So we deployed a new 4.16.9 DC, joined, everything is fine. Remove the old DC, upgrade OS, install 4.16.10 (which was

I am quite confident about the command I was typing. :) And I copied from yours and tried it again. == [root at dc ~]# samba-tool domain provision samba-tool domain: no such subcommand: provision Usage: samba-tool domain <subcommand> Domain management. Options: -h, --help show this help message and exit Available subcommands: info - Print basic info about a domain and the DC

Hi I've set up a domain with 2 dc (samba 4.16.10 - debian 11) a fileserver ( 4.15.13 ubuntu 22) , and 50 windows client. fileserver has a few share with win ACL ( I follow [ https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs | https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs ] ) . Everythings works fine and I can setup security access for that

Hi. As happened some weeks ago, here I am again updating an old Samba 4.14.x network to a current version. The server hosting the FSMO roles is a Debian10 with 4.14.14, while the third node is a Ubuntu 18 running LinuxSchools build 4.14.8. We started from a Ubuntu 20.04 server running Louis builds. We demoted the node and joined it back to the domain with 4.17.5 from Michael. Although on the

hi all I have 2 DC joined to the same domain . both with ubuntu 20 and samba 4.17 ( MichaelTokarev repos) with Bind9 as dns. After Upgraded the first dc to ubuntu 22 and 4.18 I' m not able to start bind9 . Also the second DC has been broken DNS , and after a BIND9 restart It wont start anymore. any help? thanks rf here my syslog : Jul 21 23:49:14 dc-cloud named[637]: starting BIND

----- Messaggio originale ----- Da: "Rowland Penny via samba" <samba at lists.samba.org> A: "samba" <samba at lists.samba.org> Cc: "Rowland Penny" <rpenny at samba.org> Inviato: Mercoled?, 8 marzo 2023 17:01:34 Oggetto: Re: [Samba] Unable to "rejoin" existing DC after upgrade (infamous WERR_FILE_NOT_FOUND) Please do not 'cc' me or

Looks like a known issue when running samba as AD DC: https://bugzilla.samba.org/show_bug.cgi?id=9673 Perhaps try logrotate service to help rotate log.samba: https://linux.die.net/man/8/logrotate -- Regards, Jones Syue | ??? QNAP Systems, Inc. On Fri, May 22, 2020 at 12:26 PM Lorenzo Milesi via samba <samba at lists.samba.org> wrote: > > I know about this param, I configured it and

Samba 4.12.1 installed from source following the wiki. I noticed /usr/local/samba/var/log.samba is not being rotated at all, it starts since the day I installed and it's still growing (500M so far). Is this something which must be handled manually with a logrotate entry? What signalling does samba require after the file has been rotated? I didn't find anything on the wiki, is it worth

> which share isn't working ? > is it 'CONDIVISIONE' ? What is really weird is: Computer01, Win10, user1 logged in as local (not using domain user), share mapped with domain user. In the path I've posted in the first message the user can access BUT cannot write. Computer01, Win10, user1 logged in as domain user: same as above, user can access the folder but cannot write.

I never said the team does recommend it, still I don't see the purpose of saying "it's possible" when can be "fraught with problems". Maybe the wiki [1] should be more explicit on this, despite discouraging and suggesting better options it doesn't say it's highly problematic, it's still offered as an option.

> By setting this: vfs objects = recycle , you have turned of 'acl_xattr'. Ouch! :( Is there a way to keep acl_xattr and recycle? Shall I specify both of them? > You should also be aware that the permissions set from Windows (you are > setting them from Windows, aren't you ?) are stored in an EA. Yes, we're using RSAT from Windows. I see ea support has been set to yes

> Can I suggest you upgrade to Ubuntu 20.04 and use Louis's repo: > http://apt.van-belle.nl/ Unfortunately it's not a viable solution in the short period... Is there any problem with S4.12 and Ubuntu 18.04? Or with the default compile options on 18.04? thanks -- Lorenzo Milesi - lorenzo.milesi at yetopen.it YetOpen S.r.l. - https://www.yetopen.it/ Via Salerno 18 - 23900 Lecco -

> I would expect to only see that on a machine with the MIT kdc installed, > try this > > apt-get -s remove krb5-kdc > > This will prove one way or other if it is installed and what it wants to > remove along with it, it will not remove anything. Apparently nothing requires it: The following packages were automatically installed and are no longer required:

We've recently upgraded a S3 to Samba4 with AD (4.3.11-Ubuntu). The access control on the old installation was done with "valid users" and "write list". We've ported this to ACL, but for some path users are denied access and we cannot understand why. I.e. for a generic share, user "user1" can browse and access almost everything except for directory

Attaching logs during an attempt of browsing \\server from CM-WM-W7$ thanks ----- Original Message ----- > From: "samba" <samba at lists.samba.org> > To: "Alex MacCuish" <alex at maccuish.org.uk>, "samba" <samba at lists.samba.org> > Sent: Saturday, May 9, 2020 12:03:58 AM > Subject: Re: [Samba] Unable to access shares by server

> Can I suggest you read 'man smb.conf' Thanks, but on what "topic"? Is there a specific param or config you think could be relevant? > Try adding 'server max protocol = NT1' and ensure SMBv1 is running on > all machines. Is this just for SMBv1 or because you think could be related to the login problem? > Also, is the ldap server really running on port