Samba not working

DKrics · March 6, 2020, 3:12am

I’m using the Samba Share plug-in. I am running HA on RPi3B+. I’m now on version 0.106.4.
I’m not certain when this last worked, but it had worked previously for me. I haven’t changed any settings. The only change other than the occasional updating of the HA version is that work upgraded my laptop from Windows 7 to Windows 10.
Here’s the log from when I start the plug-in:

[21:01:10] INFO: Hostname: hassio
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
No builtin backend found, trying to load plugin
tdbsam_open: Converting version 0.0 database to version 4.0.
tdbsam_convert_backup: updated /var/lib/samba/private/passdb.tdb file.
tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_open_ex: could not open file /var/lib/samba/winbindd_idmap.tdb: No such file or directory
tdb(/var/lib/samba/account_policy.tdb): tdb_open_ex: could not open file /var/lib/samba/account_policy.tdb: No such file or directory
account_policy_get: tdb_fetch_uint32_t failed for type 1 (min password length), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password history), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 3 (user must logon to change password), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 4 (maximum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 5 (minimum password age), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 6 (lockout duration), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 7 (reset count minutes), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 8 (bad lockout attempt), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 9 (disconnect time), returning 0
account_policy_get: tdb_fetch_uint32_t failed for type 10 (refuse machine password change), returning 0
Added user hassio.
nmbd version 4.10.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
smbd version 4.10.8 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
Processing section "[config]"
Processing section "[addons]"
Processing section "[ssl]"
Processing section "[share]"
Processing section "[backup]"
added interface docker0 ip=172.17.0.1 bcast=172.17.255.255 netmask=255.255.0.0
added interface docker0 ip=172.17.0.1 bcast=172.17.255.255 netmask=255.255.0.0
added interface hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0
added interface hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0
added interface eth0 ip=192.168.86.36 bcast=192.168.86.255 netmask=255.255.255.0
added interface eth0 ip=192.168.86.36 bcast=192.168.86.255 netmask=255.255.255.0
making subnet name:192.168.86.36 Broadcast address:192.168.86.255 Subnet mask:255.255.255.0
making subnet name:172.30.32.1 Broadcast address:172.30.33.255 Subnet mask:255.255.254.0
INFO: Profiling support unavailable in this build.
making subnet name:172.17.0.1 Broadcast address:172.17.255.255 Subnet mask:255.255.0.0
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0
load_lmhosts_file: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
No builtin backend found, trying to load plugin
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
tdb(/var/lib/samba/registry.tdb): tdb_open_ex: could not open file /var/lib/samba/registry.tdb: No such file or directory
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
waiting for connections
check_for_master_browser_fail: Forcing election on workgroup WORKGROUP subnet 172.17.0.1
check_for_master_browser_fail: Forcing election on workgroup WORKGROUP subnet 172.30.32.1
check_for_master_browser_fail: Forcing election on workgroup WORKGROUP subnet 192.168.86.36
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.86.36
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.86.36
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.86.36
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.86.36
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.17.0.1
run_elections: >>> Won election for workgroup WORKGROUP on subnet 172.17.0.1 <<<
become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 172.30.32.1
run_elections: >>> Won election for workgroup WORKGROUP on subnet 172.30.32.1 <<<
become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 192.168.86.36
run_elections: >>> Won election for workgroup WORKGROUP on subnet 192.168.86.36 <<<
become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 192.168.86.36
*****
Samba name server HASSIO is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
*****
*****
Samba name server HASSIO is now a local master browser for workgroup WORKGROUP on subnet 172.30.32.1
*****
*****
Samba name server HASSIO is now a local master browser for workgroup WORKGROUP on subnet 192.168.86.36
*****

Here’s my config for the plug-in:

workgroup: WORKGROUP
username: hassio
password: samba
interface: ''
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
  - 192.168.10.0/24
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes

I added that last host address after searching the message boards on this topic.
Any advice you have is appreciated.

DavidFW1960 · March 6, 2020, 3:28am

that is covered by 192.168.0.0/16

Maybe try this How to access files on network devices using SMBv1 on Windows 10 | Windows Central

EDIT: It’s probably not that. I disabled SMB1 on my Win10 computer and it still connects fine to HA shares. (My old Stora NAS… not so much lol)

tom_l · March 6, 2020, 4:35am

Is your new windows 10 install a member of WORKGROUP?

I don’t think it creates them by default after v1803.

It also appears to be complaining about the insufficient length and complexity of your password.

DKrics · March 6, 2020, 4:44am

I don’t even know what Workgroup is! I just used this default setting, as it previously worked that way.

tom_l · March 6, 2020, 4:57am

But then you upgraded and the new operating system does not function the same way ‘out of the box’.

EDIT: actually it was HomeGroup file sharing that got dropped. Still, check that your computer is a member of the workgroup.

DKrics · March 6, 2020, 5:43am

DavidFW1960 adding the SMB1 (clicking the checkbox) now allows my computer to recognize and connect. I additionally lengthened my password. Next, I unchecked the SMB1 box and kept the complex password, then restarted the computer, but the computer again wouldn’t recognize my home assistant.
So, I think that solved the problem. Thanks!