similar to: Unable to access shares by server alias

I know about this param, I configured it and log.smbd, log.nmbd and others are rotated, log.samba is not. ----- Original Message ----- > From: "samba" <samba at lists.samba.org> > To: "Lorenzo Milesi" <maxxer at yetopen.it>, "samba" <samba at lists.samba.org> > Sent: Thursday, May 21, 2020 7:29:04 PM > Subject: Re: [Samba] log.samba

Latest Samba4 upgrade (4.3.11+dfsg-0ubuntu0.16.04.26) broke external LDAP auth probably with the following error: LDAP request size (81) exceeds (0) samba-tool outputs the following when ran: Unknown parameter encountered: "ldap max anonymous request size" Ignoring unknown parameter "ldap max anonymous request size" Unknown parameter encountered: "ldap max authenticated

Can you try this and adjust the path's in it. #/etc/logrotate.d/samba /var/log/samba/log.smbd { weekly missingok rotate 7 postrotate [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ] || /usr/bin/smbcontrol smbd reload-config endscript compress delaycompress notifempty } /var/log/samba/log.nmbd {

> The latest Samba version is 4.10.6 and there have been numerous updates > since 4.3.11, but you shouldn't be having the problem you have, so lets > start be you posting your smb.conf Thank you very much. Here it is: [global] server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate realm = domain.lan ldap server require strong auth =

> Not sure, but that is the way it looks, just a thought, are you using > sssd ? no, not even installed > Just like a normal share, '[homes]' is a special share that doesn't use > 'path. There used to be something on the wiki about using '[home]' on a > DC, I didn't know it had gone until you mentioned it ;-) So if I use [home] it would be a normal

Hai, Verify dig -x $(hostname -i) Then dig A $(hostname -f) As long as these match any CNAME should work. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marco Gaiarin via samba > Verzonden: maandag 11 mei 2020 9:21 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Unable to access shares by server

I've just deployed an AD DC fileserver with Samba4 but the server itself is not available when browsing network computers from a Windows PC. Is it because of this [1][2] or did I misconfigure it? Thanks my config: # Global parameters [global] netbios name = FILESERVER realm = WDC.MYDOMAIN.IT server role = active directory domain controller server services =

> 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

On 07/02/2023 18:35, Lorenzo Milesi via samba wrote: > > >> A little more context, manual replication unfortunately doesn't help: > > Last (sorry for the spam, I'm starting to forget things): > > # dig _ldap._tcp.pdc._msdcs.wdc.domain.it srv > > ;; ANSWER SECTION: > _ldap._tcp.pdc._msdcs.wdc.domain.it. 900 IN SRV 0 100 389 dc1.wdc.domain.it. > >

> 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

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

> trying again. here's the output. thanks! Config collected --- 2020-05-18-23:08 ----------- Hostname: fileserver DNS Domain: wdc.mydomain.it Realm: WDC.MYDOMAIN.IT FQDN: fileserver.wdc.mydomain.it ipaddress: 10.0.0.3 ----------- This computer is running Ubuntu 18.04.4 LTS x86_64 ----------- running command : ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc

Thanks for the suggestions! > The latter is easiest to deal with, replace it with a CNAME in the AD dns. I did the CNAME, but when I remove the netbios alias I can see the shares list when accessing \\aliasname, but then I'm not allowed into any of them. I tried rebooting the client but same result, and I also don't see anything in the logs :( > The first will require a bit more

> 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:

On 01/07/2020 20:16, Lorenzo Milesi via samba wrote: > For the record, with the support of TranquilIT we added a new server for DC an "demoted" this one to fileserver only and it's working like a charm. > > So I suppose the "single server" solution is not viable anyomre, or at least it doesn't seem so. > We have never recommended using a DC as a fileserver,

Samba Version 4.12.1 I'm trying to change server IP address from 10.0.0.69 to .3 on a single AD DC running also as fileserver (very small situation). I'm following this [1] guide, I have no interface restrictions in samba or in bind. I stop samba, change IP address, restart bind, start samba, but when I run samba_dnsupdate I get some messages until: 5 DNS updates and 5 DNS deletes

> 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.

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

> 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

> Can I suggest you keep upgrading, Samba 4.3.11 is EOL and I suppose the > version of Ubuntu you are running it on will be as well ;-) It's Ubuntu 16 LTS, so it's supported until 2021. > Probably because that is the old way of doing things ;-) I said that's the old installation, in the new one we remapped all the single user entries to the new ACL from RSAT. So we opened