Well, this is strange but happened to me quite a lot of time now…
Sometimes, after enabling shared folders and starting Samba, if you start Adguard Home it’s impossible to access shared folders.
This happens usually after a while (1/2 hour-1 hour).
Intrestingly, you can sometimes access shared folders from a Windows 10 pc, but folder access is terribly slow and doesn’t work everytime… No way to access folders from my Android phone (Using File Manager + or Xiaomi file manager).
If you stop Adguard Home, shared folders are immediately accessible again, and re-enabling Adguard dosn’t stop samba anymore…
This happened a lot of time on Release 2, just upgraded to release 3 and it happened again soon after I reconfigured the router and re-enabled Samba & Adguard Home.
Option I have Activated:
On the shared folder I set up write permissions for 1 user with a password.
Override DNS Settings for All Clients is activated.
On Adguard Home, I use NextDNS (tls://)
All default blocking lists are activated except AdAway Default Blocklist
Wireguard client is running with VPN policies enabled (MAC address)
DLNA is enabled, sharing 1 subfolder of Samba Directory
When this happens the following appears often on system log:
Tue Jun 7 20:33:58 2022 daemon.err nmbd[5730]: [2022/06/07 20:33:58.308492, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Tue Jun 7 20:33:58 2022 daemon.err nmbd[5730]: *****
Tue Jun 7 20:33:58 2022 daemon.err nmbd[5730]:
Tue Jun 7 20:33:58 2022 daemon.err nmbd[5730]: Samba name server ROUTER-SALOTTO is now a local master browser for workgroup WORKGROUP on subnet 192.168.8.1
Tue Jun 7 20:33:58 2022 daemon.err nmbd[5730]:
Tue Jun 7 20:33:58 2022 daemon.err nmbd[5730]: *****