Windows 10 can't access HASSIO through Samba

[Tomahawk]

Asking as a total N00b, using a RPI3/HassOS.

Can I use the “How to configure Samba to SMBv2…” this when using the addon "Samba share"?

[stevedn3 (steve welch)]

BOOM!! after about 6 hours of stress this worked. I’ve been trying the same config settings but no luck. the issue was not using map network drive.

[Klagio]

@Martwall

My Hassio Samba settings are as follows:

{
  "workgroup": "HASSIO_HOME",
  "name": "hassio",
  "guest": false,
  "map": {
    "config": true,
    "addons": true,
    "ssl": false,
    "share": true,
    "backup": true
  },
  "username": "************",
  "password": "*************",
  "interface": "eth0",
  "allow_hosts": [
    "10.0.0.0/8",
    "172.16.0.0/12",
    "192.168.0.0/32"
  ]
} 

If I use your configuration I receive this in log

19-01-23 09:11:29 WARNING (MainThread) [hassio.addons.validate] Unknown options map

[Klagio]

My Samba works sometimes and sometimes not, I don’t know how to replicate when is working and when is not … seems to me totally random

[Martwall]

I noticed now that I get that as well. This also applies for guest: and name:. I removed the map, guest and name options and the setup still works. They are no longer valid or never where valid options according to the github add-on specification so that the reason for the warning, but having the options should not cause the samba share to not work, only that you wont be able to select which folders to map. Configuration now looks like this:

{
“workgroup”: “HASSIO_HOME”,
“username”: “",
“password”: "***”,
“interface”: “wlan0”,
“allow_hosts”: [
“10.0.0.0/8”,
“172.16.0.0/12”,
“192.168.0.0/16”
]
}

If your RPI is connected via WiFi, try to change "interface:" from "eth0" to "wlan0".

[Rockel83 (Cor)]

Well, It’s not ideal, but this workes for me for the time being:

SMB / SAMBA share inaccessible

Well It seems I have the same problem when trying to reach my Hassio on a Windows machine using Samba. Searched on the web and came across a lot of possible sollutions like enabeling and disabling Samba via regestry etc. but nothing seemed to work for me. At least, the root of Hassio was unreachable. It turned out that when I made an network share directly to a sub directory, it worked. It’s however not ideal, but it’s something at least. So I made 2 network shares of the Hassio directories I…

[Piggyback (René)]

@ArpiHA

“password”: “”,
“interface”: “eth0”

Hi,
Looking at your configuration, it assumes you connect through ethernet cable. Could it by any chance be that you are connecting through wifi?

I followed these instructions:

home-assistant/addons/blob/master/samba/README.md

this worked completely for me and I was able to connect at the first attempt. I see you are not using a user and a password. Have you given that a try to see if that helps? My windows 10 gives me a popup to enter the mapping details after connecting \IP_ADDRESS and you can store the user/password.

[Tomahawk]

What finally solved my Windows 10/Samba connection problem, deselect 128 bit … and select 40- 56 bit…:

[tom_l]

Weird. 128 is working for me.

[Piggyback (René)]

Same here.

[Vennerberg (Patrik Vennerberg)]

Try setting password and user.
Your samba config looks different from mine though…

{
“workgroup”: “WORKGROUP”,
“username”: “user”,
“password”: “password”,
“interface”: “eth0”,
“allow_hosts”: [
“10.0.0.0/8”,
“172.16.0.0/12”,
“192.168.0.0/16”
]
}

[DavidFW1960 (David)]

It’s funny… my computer screwed the pooch and I put a new HDD in and setup Win10 from scratch… not I can’t access unless I use the IP address (for samba). I can in web browser do http://hassio:8123 or http://hassio.local:8123 but only the IP address for samba.

[Illes_Eszterhas (Illés Eszterhás)]

In my case the solution was to modify the config to allow all hosts. The issue is that Windows 10 will try to use ipv6 aggressively. And of-course the default ipv4 allow list will not let it go through. In my case the symptoms were that the network tab contained the HASSIO but when connecting I got an error.

[Klagio]

I can access HASSIo (and also the host outside HASSIO) from windows 10 file explorer. What I cannot do is modify files from Windows, while I can modify them if I use WInscp or SSH with terminal. The username used in both cases is the same, I put also the same username/password as samba user.

Any clue?

[farlock85 (Roger)]

Thanks @Illes_Eszterhas, this was the solution for me.

For a fresh Win10 + HASSIO install I did: enable SMB1 and allow all hosts.

[jo-me (Jochen Mehlhorn)]

Thanks for the hint @Illes_Eszterhas !
I did not notice that Windows 10 started to resolve the hostname of my ubuntu server to its ipv6 address after the update to 1809.
I had the allow host setting set to the ipv4 range and was therefore denied access since the windows update. The Samba log showed this as well.

Solution? Disable ipv6 in ubuntu or remove the allow host samba setting. Disabling ipv6 in windows 10 does not seem to be a good idea. Apparently, at least edge and store apps demand it.

[bitli]

My problem was IPV6 too. You can see it in the log of Samba:

Connection denied from ipv6:2a02:1206:456d:9600:792b:d9ef:646:d894:50935 to ipv6:2a02:1206:456d:9600:a58d:3f63:43e:4282:445

[Phill_Healey]

Add one of the folders to the end eg:

\[hassio-ip]\config
\[hassio-ip]\addons
\[hassio-ip]\share
\[hassio-ip]\backup

It’s not ideal having to map each folder individually but it’s the only way that I can get it to work.

[Coedy (Peter Ebenezer)]

Has anyone got an example of a config to allow all? Or do you just remove the whitelist and it will just assume the connection is allowed?

One of my Win10 PCs can’t access it, but my laptop is fine. I believe its because the PC is a much newer install despite it’s IP being on the whitelist (a month or two old install vs a year or two on the laptop).

[neonowhere (Will Della-Libera)]

Good lord, what a pain in the ass that was. In case it helps anyone - the problem for me was finally unsupported characters in my password. Dumbed it down a little and voila! I’m in.