Samba share not working

Third party integrations
1

Thanks in advance for your help, i have struggled at every point with using homeassistant every instructional video is different probabaly as a lot changed in 108, but have managed to battle my way through, but i cannot get samab share to work. everybody says check the my log, but non of the insatll videos check the log or tell you what to look for.
my log has come back with a few different errors depending on my settings .
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] samba.sh: executing…
[20:23:15] INFO: Hostname: homeassistant
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.
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 homeassistant.
[cont-init.d] samba.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
nmbd version 4.11.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface eth0 ip=2a02:c7f:8687:fc00:983a:e036:d4b5:7cef bcast= netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=fd76:3b82:1d67:0:73f7:1264:c154:4448 bcast= netmask=ffff:ffff:ffff:ffff::
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 eth0 ip=192.168.0.46 bcast=192.168.0.255 netmask=255.255.255.0
making subnet name:192.168.0.46 Broadcast address:192.168.0.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
making subnet name:172.17.0.1 Broadcast address:172.17.255.255 Subnet mask:255.255.0.0
create_subnets: ignoring non IPv4 interface.
create_subnets: ignoring non IPv4 interface.
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
daemon_ready: daemon ‘nmbd’ finished starting up and ready to serve connections
smbd version 4.11.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
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 eth0 ip=2a02:c7f:8687:fc00:983a:e036:d4b5:7cef bcast= netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=fd76:3b82:1d67:0:73f7:1264:c154:4448 bcast= netmask=ffff:ffff:ffff:ffff::
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 eth0 ip=192.168.0.46 bcast=192.168.0.255 netmask=255.255.255.0
INFO: Profiling support unavailable in this build.
No builtin backend found, trying to load plugin
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.0.46
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.0.46
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.0.46
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.0.46
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.0.46
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.0.46
run_elections: >>> Won election for workgroup WORKGROUP on subnet 192.168.0.46 <<<
become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 192.168.0.46

Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1

Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 172.30.32.1

Samba name server HOMEASSISTANT is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.46

my setup is a pi4 connected by ethernet
pc is windows 10pro

2

My first guess would be to check the workgroup name along with User/Password.

Go to the configuration tab for the Samba plugin. The workgroup name should match whatever your PC is using.

3

^^^^this

The username and password you configure in the addon will also be the username and password you enter when you try and connect to the HA share on your computer.

4

Workgroup is correct but i am not sure i understand the username password issue as i cant even see the file on my network in explorer. Is the username/password for me to acess the file aftr if shows on my netwok

5

Have you checked your IP subnet? Samba is set up by default to use - - 192.168.0.* - - , but in my experience the more normal default subnet is - - 192.168.1.* - - . That was the issue that solved it for me. I didn’t notice the pesky 0 instead of 1 issue amongst all the setup parameters.

6

I went to my Windows 10 Network and i explorer typed in my homeassistant password ip \192.168… and there was my homeasistant folders, so i can accesss them now i have maped this config folder it shows as a network location, but i dont know why i could not already see it on my network? hopefull thats it sorted. do i need to map any other folders or is the configuration the important one if i get locked out?

1 Like
7

thanks for this. I had the exact same situation. Typing in windows file explorer: ‘\\192.168 […]’ saved my problem. And I had to typ two times the backslash ‘\\’.