Samba config keeps changing?

Configuration
21

I think something is broken.
Either the addon page is outdated or something is not working, because I can’t save the config with only username and password (The only required fields as seen in the addon page)

I get this error

22

Sorry for reviving this relatively old thread, but I’m having all kinds of problems getting the Samba addon to work on HASSIO 0.94.4. I’m currently running HASSIO on a Raspberry Pi 2 and want to move my installation to a Raspberry Pi 3 B+. I saved a snapshot from my Pi 2 installation, and downloaded onto my PC. Now I want to upload the saved snapshot onto the Pi 3 B+ HASSIO. I don’t really need Samba except I read that’s the only way to get a snapshot from my PC onto the new install.

All my computers are on network 192.168.31.0/16. The Pi 3 B+ ip address is 192.168.31.44.

My Samba configuration looks like this:

> {
>   "workgroup": "WORKGROUP",
>   "username": "hassio",
>   "password": "pi3",
>   "interface": "",
>   "allow_hosts": [
>     "10.0.0.0/8",
>     "172.16.0.0/12",
>     "192.168.0.0/16"
>   ]
> }

Starting the Samba addon, the last few lines of my log file looks like this:


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
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 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 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 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 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
*****
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
*****

I still don’t understand what the deal is with the 172.30.32.1 ip address. 172.30.32.1 is on a different subnet than my Pi 3. How exactly do I map to this?

Update
I figured it out. All I had to do was to enable SMB 1.0 / CIFS File Sharing Support in Windows 10. Everything's working now. I still don't understand the 172.30.32.1 ip address, but don't really care at this point since file sharing is working.

23

What’s your hostname? Use that instead of the IP.

24

So I found the issue for me.
If I tried to change the password it would always fail.
Then after googling around I noticed that when I try to set the password I was missing the Double Quotes - the default password is set at null but if you want to put a password in there you need the Double Quotes. - Actually you don’t need a username and password at all - you can just enter “” with any space between them - hope this is helpful

3 Likes
26

That helped for me. Thank you so much.

27

This is precisely the issue I had.

As soon as I created my own Username and Password, saved the file and started the service it worked flawlessly.