I’ll share my smb.conf when I get home
[hass]
comment = HomeAssistant
path = /home/rob/.homeassistant/
force user = rob
force group = rob
read only = No
guest ok = YesGreat, thank you!
How did you get on?
Struggling to get SSH working. I’m sure I’ll get it to work, but I’m having trouble to find enough time. Maybe this weekend 
I managed to get Samba working.
I was unable to get it working using NAT settings for my VM so I went back to bridged. First this didn’t work, but I found out that I had to choose the network adapter that my host PC (NUC) uses for its current internet connection. After that my hassio installation appeared in my router with its own IP adress. I was then able to reserve the IP address. Now it’s all working fine.
Connecting to Samba worked instantly using \hassio\share. It seems to be impossible to get it working using NAT.
SSH is working fine too now.
Conclusion: NAT makes life harder.
So NAT is good for somethings. But I think the issue is the VMs could not talk to the rest of your network.
With NAT on VMs your creating another network under the host and typically the routing isn’t there to route traffic from outside in. NAT blocks this.
In bridged mode your VM network is visable to the rest of the lan.
Well done for preserving!
1 Like
I know it is an old post but I have exactly the same issue with Roy and I am following your instructions. Sorry for the possibly silly questions but I am very new to HomeAssistant.
I am able to log in with SSH using putty and see the directories like /config /addons etc. Now I guess that I have to install Samba following the instructions (https://www.hiroom2.com/2017/08/02/fedora-26-samba-en/) but it seems that the bash shell is not equipped with the necessary instructions.
sudo dnf install -y samba returns “-bash : sudo command not found”. Without sudo the result is dnf command not found. Also assuming that the os below is ubuntu based, I tried apt-get install samba smbfs but apt-get also fails. It seems that I am missing something important.