[Samba] Windows 10 clients unable to work on domain after update of windows (on client) and samba on dc

Rowland Penny rpenny at samba.org
Thu Aug 17 08:52:53 UTC 2023

On Thu, 17 Aug 2023 10:25:39 +0200
Fabio Fantoni via samba <samba at lists.samba.org> wrote:

> Hi, update after other tests:
> The samba_dnsupdate issue above was because on this dc there was
> itself as first dns in /etc/resolv.conf but as not pdc anymore fails
> to update dns record, after set new pdc as first dns server in
> resolv.conf worked. is it correct that samba_dnsupdate works only
> with pdc?

No, it isn't correct, samba_dnsupdate is supposed to run on all DCs, in
fact it runs every 10 minutes.
Each DC is supposed to use itself as its first nameserver, by changing
that to another DC, your DC is now using that DC and is probably making
all changes on it, which may, or may not, replicate back.

> Another issue solved was not related to samba
> Remain the netlogon and sysvol share not accessible from windows 10 
> client using the filemanager, group policy are still working anyway;
> I not understand why these share are not accessible, someone know the 
> cause please?

Because you have problems other than the samba_dnsupdate one, it looks
like you may have database problems, have you tried running
'samba-tool dbcheck' ?

If all else fails, I suggest you demote this DC (provided that the
other DC doesn't have any problems) and then join another one.


More information about the samba mailing list