similar to: Error changing server IP address: ERROR: Connecting to DNS RPC server

> 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

> 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

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 =

> 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

> What OS is this ? Ubuntu 18.04.4 > Can you run the attached script on the DC and copy the output into a > post (sanitised if required) I don't see any attachment. -- Lorenzo Milesi - lorenzo.milesi at yetopen.it YetOpen S.r.l. - https://www.yetopen.it/ Via Salerno 18 - 23900 Lecco - ITALY - Tel +39 0341 220 205 - Fax +39 178 6070 222 Think green - Non stampare questa e-mail

> You missed that using a DC as a fileserver isn't recommended. It was between the lines of "I followed all the guidelines for doing things correctly in this specific situation" :) > From reading the samba log, it looks like Samba logons are not working, > but ldap connections are. This means Win clients are logging in via LDAP? Can this be related to the inaccessible

I'm having a weird situation with a freshly installed Samba v4.12.1 compiled from source. This is a single server with DC and fileserver, I followed all the guidelines for doing things correctly in this specific situation and I hope I haven't missed anything. The server works correctly as expected, I'm managing all the permissions from Windows. Unfortunately users occasionally

I've set up a single server with a DC and fileserver. I've read through all docs and the warnings on the wiki (VERY well done, many thanks to all the contributors) more than once so I hope I haven't missed anything. smb.conf: # Global parameters [global] netbios name = FILESERVER realm = WDC.DOMAIN.IT server role = active directory domain controller

I'm pasting below the output of the debug script you sent me some time ago. Other than this Samba has been compiled with standard options, just ./configure, following the wiki guide with the offered bootstrap file for ubuntu18.04. root at fileserver:~# smbd -b Paths: SBINDIR: /usr/local/samba/sbin BINDIR: /usr/local/samba/bin CONFIGFILE: /usr/local/samba/etc/smb.conf

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

> 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

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

> 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

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 {

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

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

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

Samba 4.12.1, single server with AD+DC on Ubuntu 18.04. Filesystem: /dev/sdb1 on /home type ext4 (rw,relatime,stripe=32750,data=ordered) It all work as expected, but I occasionally get the error in subject which denies access to shares. Restarting Samba will restore functionality. What can be the cause of this problem? Thanks. [2020/05/27 18:24:35.795379, 8]

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

On 14/04/2023 12:13, Lorenzo Milesi via samba wrote: > >> 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,