similar to: Only domain admins can access shares

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

> 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

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

> 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

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

Hi. We're having a strange issue: we have several office temp files left around even when files get closed. Right now there are no open files on Samba, but there are more than twenty lock files around. So, given that the file has been accessed correctly by the user and has been correctly saved (no data loss has been reported), what could prevent Office from deleting its files? Any

> Verify dig -x $(hostname -i) > Then dig A $(hostname -f) > > As long as these match any CNAME should work. These works, but why these should match a CNAME? hostname returns the "main" host... Anyway to make a test I configured a new CNAME #?dig server.wdc.mydomain.it ;; ANSWER SECTION: server.wdc.mydomain.it. 900 IN CNAME fileserver.wdc.mydomain.it.

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 =

> 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

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

> 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

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,

> 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

About the root problem of the thread, it seems a permission problem, but again I need some help on how to investigate further. I've just been reported a share wasn't accessible, I checked on another client and I was able to enter the folder but NOT to see the content, looked like empty. I have "hide unreadable" enabled, and while entering the share several times I noticed the

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

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]

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

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

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

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