Samba & HassOS not working on Windows 10

Configuration
1

Hi, two days I am struggling with the Samba Share addon, and still not work. I tryed connect to server with address in file explorer \\192.168.100.103\config but nothing happened. Already tryed change 128bit to 40-56bit encryption with same result. Samba v1 is manualy installed on Win 10.

Hardware
Raspberry Pi 4 Model B 2GB
PC - Windows 10 Pro 1909

HassOS

  • version: 3.12 - 32 bit
  • deployment: production
  • hostname: homeassistant

Home Assistant

  • version: 0.106.5

Samba Share

  • version - 9.0
  • samba config:
workgroup: HOME
username: Suggorath
password: hass
interface: ''
allow_hosts:
  - 10.0.0.0/8
  - 172.16.0.0/12
  - 192.168.0.0/16
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes

Note: Already tryed “interface: eth0” without success.

  • samba log:
[21:30:42] INFO: Hostname: homeassistant
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 Suggorath.
nmbd 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
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.100.103 bcast=192.168.100.255 netmask=255.255.255.0
making subnet name:192.168.100.103 Broadcast address:192.168.100.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
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
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
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
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 hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0
added interface eth0 ip=192.168.100.103 bcast=192.168.100.255 netmask=255.255.255.0
INFO: Profiling support unavailable in this build.
No builtin backend found, trying to load plugin
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 HOME subnet 172.17.0.1
check_for_master_browser_fail: Forcing election on workgroup HOME subnet 172.30.32.1
check_for_master_browser_fail: Forcing election on workgroup HOME subnet 192.168.100.103
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 192.168.100.103
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 192.168.100.103
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 192.168.100.103
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 192.168.100.103
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.17.0.1
run_elections: >>> Won election for workgroup HOME on subnet 172.17.0.1 <<<
become_local_master_browser: Starting to become a master browser for workgroup HOME on subnet 172.17.0.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 172.30.32.1
run_elections: >>> Won election for workgroup HOME on subnet 172.30.32.1 <<<
become_local_master_browser: Starting to become a master browser for workgroup HOME on subnet 172.30.32.1
send_election_dgram: Sending election packet for workgroup HOME on subnet 192.168.100.103
run_elections: >>> Won election for workgroup HOME on subnet 192.168.100.103 <<<
become_local_master_browser: Starting to become a master browser for workgroup HOME on subnet 192.168.100.103

System log:

[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] udev.sh: executing... 
[19:34:03] INFO: Update udev informations
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
20-03-10 19:34:06 INFO (MainThread) [__main__] Initialize Supervisor setup
20-03-10 19:34:06 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attach to Supervisor homeassistant/armv7-hassio-supervisor with version 209
20-03-10 19:34:07 INFO (MainThread) [__main__] Setup Supervisor
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: de.pengutronix.rauc - /
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.NetworkManager - /org/freedesktop/NetworkManager/DnsManager
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.info] Update local host information
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.services] Update service information
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
20-03-10 19:34:07 INFO (MainThread) [supervisor.host.services] Reload local service hassos-apparmor.service
20-03-10 19:34:07 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1
20-03-10 19:34:07 INFO (SyncWorker_1) [supervisor.docker.interface] Attach to homeassistant/armv7-hassio-dns with version 1
20-03-10 19:34:07 INFO (SyncWorker_2) [supervisor.docker.interface] Attach to homeassistant/armv7-hassio-audio with version 8
20-03-10 19:34:07 INFO (MainThread) [supervisor.misc.forwarder] Start DNS port forwarding to 172.30.32.3
20-03-10 19:34:07 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-10 19:34:07 INFO (MainThread) [supervisor.audio] Start Audio plugin
20-03-10 19:34:07 INFO (SyncWorker_2) [supervisor.docker.interface] Clean hassio_audio application
20-03-10 19:34:07 INFO (SyncWorker_4) [supervisor.docker.interface] Clean hassio_dns application
20-03-10 19:34:09 INFO (SyncWorker_4) [supervisor.docker.dns] Start DNS homeassistant/armv7-hassio-dns with version 1 - 172.30.32.3
20-03-10 19:34:09 INFO (SyncWorker_2) [supervisor.docker.audio] Start Audio homeassistant/armv7-hassio-audio with version 8 - 172.30.32.4
20-03-10 19:34:09 INFO (SyncWorker_1) [supervisor.docker.interface] Attach to homeassistant/raspberrypi4-homeassistant with version 0.106.5
20-03-10 19:34:09 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /
20-03-10 19:34:09 INFO (MainThread) [supervisor.hassos] Detect HassOS 3.12 / BootSlot A
20-03-10 19:34:09 INFO (SyncWorker_0) [supervisor.docker.hassos_cli] Found HassOS CLI homeassistant/armv7-hassio-cli with version 21
20-03-10 19:34:10 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/a0d7b954 repository
20-03-10 19:34:10 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/core repository
20-03-10 19:34:10 INFO (MainThread) [supervisor.store] Load add-ons from store: 64 all - 64 new - 0 remove
20-03-10 19:34:10 INFO (MainThread) [supervisor.addons] Found 2 installed add-ons
20-03-10 19:34:10 INFO (SyncWorker_4) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-configurator with version 4.7
20-03-10 19:34:10 INFO (SyncWorker_9) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-samba with version 9.0
20-03-10 19:34:10 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-03-10 19:34:10 INFO (MainThread) [supervisor.snapshots] Found 0 snapshot files
20-03-10 19:34:10 INFO (MainThread) [supervisor.discovery] Load 0 messages
20-03-10 19:34:10 INFO (MainThread) [supervisor.ingress] Load 2 ingress session
20-03-10 19:34:10 INFO (MainThread) [supervisor.secrets] Load Home Assistant secrets: 1
20-03-10 19:34:10 INFO (MainThread) [__main__] Run Supervisor
20-03-10 19:34:10 INFO (MainThread) [supervisor.api] Start API on 172.30.32.2
20-03-10 19:34:10 INFO (MainThread) [supervisor.utils.gdbus] Call de.pengutronix.rauc.Installer.Mark on /
20-03-10 19:34:10 INFO (MainThread) [supervisor.hassos] Rauc: A - marked slot kernel.0 as good
20-03-10 19:34:10 INFO (MainThread) [supervisor.addons] Phase 'initialize' start 0 add-ons
20-03-10 19:34:10 INFO (MainThread) [supervisor.addons] Phase 'system' start 0 add-ons
20-03-10 19:34:10 INFO (MainThread) [supervisor.addons] Phase 'services' start 1 add-ons
20-03-10 19:34:11 INFO (SyncWorker_12) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-samba with version 9.0
20-03-10 19:34:16 INFO (SyncWorker_15) [supervisor.docker.interface] Start homeassistant/raspberrypi4-homeassistant
20-03-10 19:35:15 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-03-10 19:35:15 INFO (MainThread) [supervisor.addons] Phase 'application' start 1 add-ons
20-03-10 19:35:16 INFO (SyncWorker_3) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-configurator with version 4.7
20-03-10 19:35:21 INFO (MainThread) [supervisor.tasks] All core tasks are scheduled
20-03-10 19:35:21 INFO (MainThread) [supervisor.hwmon] Started Supervisor hardware monitor
20-03-10 19:35:21 INFO (MainThread) [supervisor.core] Supervisor is up and running
20-03-10 19:35:21 INFO (MainThread) [supervisor.host.info] Update local host information
20-03-10 19:35:21 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-03-10 19:35:21 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-03-10 19:35:22 INFO (MainThread) [supervisor.host.services] Update service information
20-03-10 19:35:22 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-03-10 19:35:22 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-03-10 19:35:22 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-03-10 19:35:22 INFO (MainThread) [supervisor.host.sound] Update PulseAudio informationSystem log

01
011500×1270 440 KB

2

Works fine for me, I access it with

\\hassio

I didn’t change any settings in Windows at all.

3 
interface: ''

You should use ‘eth0’ for ethernet cable, and something else for wifi. Can’t remember.
That is why it’s not working.

Is your workgroup called ‘Home’?
I’m not sure by the images.

4

Yes I tryed blank interface: ‘’ and with eth0 as interface: eth0, but both not working for me. Name of my workgroup is for now HOME, but I already tryed default name WORKGROUP, ofc I changed names in Samba config and in Windows.

5

Is any of the IPs in “allow_hosts” your computer?
I changed those to my routers IP and my computers IP

6

My IP addresses are follow:

  • PC - 192.168.100.100 - set to DHCP Static IP
  • rPI - 192.168.100.103 - set to DHCP Static IP
  • router - 192.168.100.1

ipconfig -all:

PS C:\Users\Hydro> ipconfig -all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Suggorath
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
   Physical Address. . . . . . . . . : 1C-XX-XX-XX-XX-XX
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::1c90:23b5:73fb:b402%15(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.100.100(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : fe80::1%15
                                       192.168.100.1
   DHCPv6 IAID . . . . . . . . . . . : 102526821
   DHCPv6 Client DUID. . . . . . . . : 00-XX-XX-XX-XX-XX-XX-XX-1C-XX-XX-XX-XX-XX
   DNS Servers . . . . . . . . . . . : 8.8.8.8
                                       8.8.4.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Interesting part is, I can see HASS in my network as you can see in image bellow, but when I click on HOMEASSISTANT nothing is opened, just endless spining and then I get network error with message. Windows cannot access (Network path not found).

00
00919×754 116 KB

7

As I see it then, this should work:

workgroup: HOME
username: Suggorath
password: hass
interface: 'eth0'
allow_hosts:
  - 192.168.100.100
  - 192.168.100.1
veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - icon?
  - .Trashes

But that is based on that the workgroup name is correct and that you are using cable.
Add any other devices that need rights to use samba as I did.

8

I finally found solution, I just fast recap all things, which is needed to do.

  1. Install Samba version 1 in Windows

    • Press Windows Key + R and in pop-up window type optionalfeatures and run
    • Expand the SMB 1.0/CIFS File Sharing Support option.
    • Check the SMB 1.0/CIFS Client option and restart PC

    or alternative you can run PowerShell as administrator and type:

    • DISM /Online /Enable-Feature /All /FeatureName:SMB1Protocol and restart PC

  2. Check or Set workgroup for you network

    • Press Windows Key + R and in pop-up window type SystemPropertiesAdvanced and run
    • In new displayed window System Properties switch to the Computer Name tab
    • Click on the Change button and in Workgroup under Member of check or set your network workgroup name

    or alternative you can run PowerShell as administrator and type:

    Check name of workgroup

    • (Get-WmiObject Win32_ComputerSystem).Workgroup

    Set name of workgroup

    • Add-Computer -WorkGroupName “YOUR_NEW_WORKGROUP_NAME” and restart PC

  3. Enable services for network discovery

    • Press Windows Key + R and in pop-up window type services.msc and run
    • Enable/Start following services and change Startup type: to Automatic
      • Function Discovery Provider Host
      • Function Discovery Resource Publication
      • UPnP Device Host
      • SSDP Discovery
      • TCP/IP NetBIOS Helper (this was my problem, I have it disabled)

After this you can see your HOMEASSISTANT in your network and you can manualy map your network drive, for example: \\192.168.100.1\config, but you can’t just click on HOMEASSISTANT icon to see your shared folders, you must do one more thing.

  1. Enable Insecure Quest Logons

    • Press Windows Key + R and in pop-up window type gpedit.msc and run
    • In new displayed window Local Group Policy Editor go to in menu:
    • Local Computer Policy -> Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation
    • Then double click on option Enable Insecure quest logons and select Enable and press OK.
1 Like
9

Is this windows 10 home or pro?

10

I have just gone through multiple threads, and as of MAY 2021, I am able to get into the HOMEASSISTANT network folder on WIN10 (OS Build 19042.985) by doing the following:
-enabling SMB 1.0 in optional features
-using the following configuration in HA/Samba (add your computer logon data, remove the +, make sure you have the apostrophe surrounding the password field):

workgroup: WORKGROUP
username: +your Windows logon user+
password: +‘your Windows logon password’+
allow_hosts:

  • ‘*’
    veto_files:
  • ._*
  • .DS_Store
  • Thumbs.db
  • icon?
  • .Trashes
    compatibility_mode: false

It seems Windows is too stupid to prompt you with a logon window, and just blindly uses your Windows username and password. I found no way to actually fix this behavior, so you just have to set Samba in HA to use the same login info. Stupid I know but whatever… just needs to be done

11

Sigh :unamused:

Quadruple Posting the same content witinin four threads …

quatruple
quatruple1471×953 187 KB

12

Thanks, I have tried the steps above. However my computer does not have a login password, is there a way to set the password field as null?