similar to: samba 4.8.3 samba_dnsupdate odd long timeouts

Hello, Centos 7.5 samba 4.8.3 installation, compiled from source working as AD DC. It was an update from 4.7 (not an in place update, but added new DC's to existing domain and demoted 4.7.x DC's). After adding to my smb.conf: /apply group policies = yes/ I see errors on samba star: ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler)   /usr/local/samba/sbin/samba_gpoupdate: SID

Hello, I stumbled upon weird error/bug. My setup: 4.8.3 AD on centos 7.5 (compiled from source). BIND as dns running on AD DC with secure dns updates setup and working. Most of the DNS updates are dynamic, some added manually using windows DNS manager. One of the PTR entries in reverse lookup zone went missing. It's not visible in the windows DNS manager, it's nowhere to be found

Clearly this is some kind of bug. Can you submit a bug report or should I? Also can you elaborate why it's bad practice to create files/folders as a local Unix user/group on a Samba DC? On Thu, Aug 16, 2018 at 9:50 PM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Thu, 16 Aug 2018 21:20:29 +0200 > Kacper <kacper at kacper.se> wrote: > > > The

By primary group I mean the group that is set by chgrp. that is the group returned after the pound key (#) from getfacl. In other words the Unix group and not the one managed by ACLs. / Kacper > Hello, > > I've seem to have found what looks like a bug in Samba 4.8.3. It's > the same problem as described in > https://lists.samba.org/archive/samba/2018-March/214589.html.

Hi again, First, i revert to a snapashot with samba 4.7.7 and upgraded it to 4.7.8. I got no issue with my settings and "testparm" outputs as expected. Next i tried again upgrade to samba 4.8.3. But i got the same error like an email before. Yes i guess its a problem that "tesparm" cant read the registry. When im removing "include = registry" and add my global

On Tue, 3 Jul 2018 08:06:44 +0200 Kacper Wirski via samba <samba at lists.samba.org> wrote: > Hello, > > I've realised that there was an error on this server, wrong > idmap.ldb, 3000002 should be one of the built-in users or groups > instead of machine own account. Unfortunately fixing idmap (I > imported idmap.ldb from DC with correct mapping) didn't fix my >

I've noticed myself similiar issue. Windows 10 (v 1803) - window with security tab open crashes on certain files (yes, just the window, not whole OS). Just before crash i see unresolved SID which looks like nothing I know (doesn't look like domain SID - maybe local user SID from samba member server?). All files that cause this issue are from any of the samba servers. Same files I can

Hi guys. I'm preparing my migration from samab NT4 style to AD. I had follow some papers about, exist 1 step that I still don't if is right or don't. A lot of site show that once we run the command: samba-tool domain provision ... using BIND9_DLZ This step will create a named.conf inside ./private/named.conf I have run a lot of times the command, but won't see this file. Is

The OS is Windows 7 Enterprise (build 7601, SP1). Samba version 4.8.3, compiled on Centos 7.4. smb.conf: # Global parameters [global] dns forwarder = none log level = 1 netbios name = DC1 realm = SAMDOM.TEST server role = active directory domain controller workgroup = SAMDOM idmap_ldb:use rfc2307 = yes [netlogon] path =

Hi, I think the author meant named.conf that is to be "included" into to main named.conf. And he's right, that in samba 4.8.3 all bind related files are not in /samba/private, as it used to, but rather in /samba/bind-dns (named.keytab, named.conf that is to be included and all other bind related files). So he's right, that file "named.conf" that used to appear in

Can you try to upgrade to any 4.8 version then to 4.9.4? might work, atleast my guess this will have a better chance get passed this bug. Greetz, Louis > Op 31 dec. 2018 om 18:35 heeft Král Gergely via samba <samba at lists.samba.org> het volgende geschreven: > > 2018-12-31 17:29 id??pontban Rowland Penny via samba ezt írta: > >>> >> >> OK,

Hello, I've been setting up new file server using samba 4.8.3 (centos 7 RPM), as samba 4 AD member server using my earlier smb.conf when I realised that I was  previously somewhat circumventing the SeDiskOperatorPrivilege by using "admin users map" to SAMDOM\Domain admins" parameter in smb.conf. I decided to change my smb.conf and setup shares following samba wiki. All

On Wed, 02 Jan 2019 20:09:44 +0100 Král Gergely via samba <samba at lists.samba.org> wrote: > 2018-12-31 20:50 időpontban L.P.H. van Belle via samba ezt írta: > > Can you try to upgrade to any 4.8 version then to 4.9.4? > > might work, atleast my guess this will have a better chance get > > passed this bug. > > > > I can confirm that an upgrade to 4.7.3 to

Hello, I have an issue as stated in topic. My samba 4.8.3 file server, which is AD member frequently shows winbind errors (pasted below). From user perspective it seems to work fine, but I'm worried that I have something misconfigured and in the long run, I might run into some errors. My AD DC are running on samba 4.9.x (two of them), compiled from source with BIND as DNS backend (running on

Hello, I've seem to have found what looks like a bug in Samba 4.8.3. It's the same problem as described in https://lists.samba.org/archive/samba/2018-March/214589.html. When accessing the Security tab on files and folder from a share explorer.exe crashes. I've been able to track down that it only happens when the primary group of a file or folder is a Unix group. Using an AD group as

Ok, I finally could try it out, and it seems to actually work, but You need samba 4.7 on all machines, not only AD, but also server with freeradius. I didn't get a chance to test it locally, that is samba AD + freeradius on the same server. Setup: 4.7.6 AD server and 4.6.2 samba member + freeradius didn't work (got simple "nt_status_wrong_password") but: 4.7.6 AD and 4.7.1

I have a suspicion that it is related to the specific SPNs that hyperv uses. Hyper-v tries to register 3 spn (typing from memory so I might be a bit off): Microsoft hyper-v console/HOST.FQDN Hyper-V Replication Servive/HOST.FQDN Microsoft Hyper-V Live Migration Service/HOST.FQDN. This fails because of the spaces, that is samba being on linux, not seeing escape characters, messes up the request it

Hello, i upgraded my ctdb cluster (3 nodes) from samba 4.7.7 to 4.8.3. Followed the steps under "policy" in this wikipage https://wiki.samba.org/index.php/Upgrading_a_CTDB_cluster. I shutdown all CTDB nodes and upgraded them. After the upgrade i started all nodes and ctdb status shows: Number of nodes:3 pnn:0 192.168.199.52   OK (THIS NODE) pnn:1 192.168.199.53   OK pnn:2

Hello, I've realised that there was an error on this server, wrong idmap.ldb, 3000002 should be one of the built-in users or groups instead of machine own account. Unfortunately fixing idmap (I imported idmap.ldb from DC with correct mapping) didn't fix my original error, as it still appears each time samba is restarted. Regards, Kacper W dniu 02.07.2018 o 10:52, Kacper Wirski via

On 18/07/19 12:33, Rowland penny via samba wrote: > I would clone the DC you want keep, move the clone away from the > domain (easiest way, unplug the ethernet) then remove the old dead DC > from this and ensure it works. If you want to use Bind9 and don't have > the 'dns-*' user, then run samba-upgradedns as I said earlier. > > Once you are sure just what to do,