Samba stopped working?

Configuration
1

Hey guys, I am very new to HA, just working on configuring my RPI for the first time.

I am not sure how this happened, but Samba stopped working - I can no longer see or access it from my windows 10 desktop.
The last thing I was working on yesterday was adding DuckDNS and LetsEncrypt, which both now work correctly and today when working on something else I’ve noticed Samba is down and am unable to get it working again.

Please help me, I don’t know how to solve this.

status check
● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2019-03-31 16:46:51 CEST; 7s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 1404 (smbd)
Status: “smbd: ready to serve connections…”
CGroup: /system.slice/smbd.service
├─1404 /usr/sbin/smbd
├─1405 /usr/sbin/smbd
├─1406 /usr/sbin/smbd
└─1408 /usr/sbin/smbd

Mar 31 16:46:51 hassbian systemd[1]: Starting Samba SMB Daemon…
Mar 31 16:46:51 hassbian systemd[1]: smbd.service: Supervising process 1404 which is not our child. We’l
Mar 31 16:46:51 hassbian smbd[1404]: [2019/03/31 16:46:51.863365, 0] …/lib/util/become_daemon.c:124(da
Mar 31 16:46:51 hassbian smbd[1404]: STATUS=daemon ‘smbd’ finished starting up and ready to serve conn
Mar 31 16:46:51 hassbian systemd[1]: Started Samba SMB Daemon.
lines 1-19/19 (END)

conf
[global]
netbios name = Hassbian
server string = Hassbian
workgroup = WORKGROUP
hosts allow = 192.168.0.52
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536
remote announce =
remote browse sync =

[HOMEPI]
path = /home/pi
comment = No comment
browsable = yes
only guest = no
read only = no
valid users =
writable = yes
guest ok = yes
public = yes
create mask = 0777
directory mask = 0777
force user = root
force create mode = 0777
force directory mode = 0777
hosts allow =

[HOME ASSISTANT]
path = /var/opt/homeassistant
comment = No comment
browsable = yes
read only = no
valid users =
writable = yes
guest ok = yes
public = yes
create mask = 0777
directory mask = 0777
force user = root
force create mode = 0777
force directory mode = 0777
hosts allow =

[ROOT]
path = /home/
comment = No comment
browsable = yes
read only = no
valid users =
writable = yes
guest ok = yes
public = yes
create mask = 0777
directory mask = 0777
force user = root

[share]
Comment = Pi shared folder
Path = /share
Browseable = yes
Writeable = Yes
only guest = no
create mask = 0777
directory mask = 0777
Public = yes
Guest ok = yes

2

running
sudo /etc/init.d/samba start
fixed it

3

Hi guys

Rather than start a new thread, I thought I would add onto this one as it’s a similar (if not the same) issue.

I haven’t touched my Home Assistant for a while, so therefore no changes have been made.

A few days ago, there was a major Windows update. I mention this as I don’t know if it’s related or the cause.

I have just noticed that in Windows Explorer on my Windows 10 PC, under Network, I can’t see my Raspberry PI.

I can PuTTY into the unit and my web front end is working and I’ve run the above command that MartinB2 said fixed his issue, but I still can’t see it in Windows 10 File Explorer.

Is it something I need to do in Windows or within the Putty window to get this working so I can access my configuration.yaml files (and the other files)?

I’ve gone to the “i” part of the Developer Tools on the Web front end and it says the path to my configuration file is:

/home/homeassistant/.homeassistant

If I copy and paste that into the path bar of Windows Explorer, it opens a tab in Chrome (my default browser) and says:

This site can’t be reached

home ’s server IP address could not be found.

Try:

ERR_NAME_NOT_RESOLVED

One of the messages that came up in the final reboot during the last major Windows 10 update was something about “Home Groups” no longer existing. Does this help?

Thanks in advance.

4

Hi,

check your ipV6-Konfiguration in your Network-Settings.
I deactivated it and did not have access to the RPi via Samba

5

Check if smb1 is still enabled as the windows update may have disabled it as its deemed insecure.

6

(sorry for the delay, been busy)

That looks a bit confusing to someone like me who’s not technical.

The first part talks about disabling it and talks about Windows 10, but the later part that talks about “How to detect status, enable, and disable SMB protocols on the SMB Server” only talks about other OS’s other than Windows 10.

My Windows Explorer shows my Fritzbox router under “network” so would that mean my SMB is working??

network
network885×498 127 KB

7

No that doesnt mean its enabled

open control panel
select program and features

on left hand menu select "turn windows features on of off
when feature list appears, scroll down to "smb 1.0/cifs file sharing support and see if its selected
if not selected SMB1 isnt enabled

8

Thanks for showing me where to go. I checked and it’s turned on.

smb

I am seriously thinking of starting again, only this time installing Hass.IO. I think if I did do this, I would get a Z-wave USB dongle so I can get rid of my Vera Hub (I only got the Vera hub as I wanted to get some Z-wave switches) and the other Rasberry Pi that runs Vera Assistant. The only issue now is that without a network path to my files, I can’t back up my files.

Plus, I was waiting for more video instructions following on from BRUH Automation, but his promised part 2 video hasn’t eventuated.