For the last several days the Home Assistant Samba share has not shown in any of my Windows(10/11) File Explorer Network views. However, the Samba shares are accessible by either adding network locations or drive mappings.
This is the error I’m seeing in the Samba log:
INFO: Profiling support unavailable in this build.
become_local_master_fail2: failed to register name CORRALES<1d> on subnet 192.168.1.11. Failed to become a local master browser.
standard_fail_register: Failed to register/refresh name CORRALES<1d> on subnet 192.168.1.11
If I look at previous logs I find this statement:
INFO: Profiling support unavailable in this build.
Samba name server AMERIDROID is now a local master browser for workgroup CORRALES on subnet 192.168.1.11
AMERIDROID is my Home Assistant’s name. Home Assistant is running on a dedicated Odroid N2+ device.
I’m sure they were configured because it’s been working for at least a year until a few days ago. Perhaps a Windows update made a change unknownn to me. I’ll take a look.
Samba Share 12.4.0 was released today but that didn’t help remedy my issue.
What I did find is, if I enter \\ameridrod into the file explorer address bar it will open the Samba share on my HA instance and then it adds ameridroid under Network. So that was what I was looking for. I still don’t know why it isn’t listed automatically and why I’m getting this error in the Samba log.
become_local_master_fail2: failed to register name CORRALES<1d> on subnet 192.168.1.11. Failed to become a local master browser.
As I expected though this will disappear when the Explorer is closed and reopened.