I have today the OpenHAbian on a Raspi 3B+.
It works fine, but I can’t access to the config-folder via samba share.
In the docu writes " If you are not able to connect, try with the IP of your device (e.g. smb://openhab@192.168.0.2 or \\192.168.0.2 )."
So I have tried to access from my file-explorer (client Windows 10) with \192.168.178.158 but my computer can’t connect to the server “… no folder found”
I have googled and found a solution, that I must activate SMB 1.0. I do it, but I can’t also not connect to samba share.
ad 1) I have tried with \\192.168.178.158\openHAB2-conf -> error: “The file could not found.”
ad 2) “See also this link:” -> error: “The input folder is wrong. Please you another folder”
Exist an analysing program for Linux or Windows that can I step-by-step check to find the missing link?
Thanks
Nov 20 22:15:12 openHABianPi smbd[1072]: pam_unix(samba:session): session closed for user nobody
Nov 20 22:15:13 openHABianPi smbd[1077]: pam_unix(samba:session): session closed for user nobody
Nov 20 22:15:16 openHABianPi smbd[1081]: pam_unix(samba:session): session closed for user nobody
Nov 20 22:15:17 openHABianPi smbd[1085]: pam_unix(samba:session): session closed for user nobody
Nov 20 22:15:27 openHABianPi smbd[1099]: pam_unix(samba:session): session closed for user nobody
Nov 20 22:15:27 openHABianPi smbd[1103]: pam_unix(samba:session): session closed for user nobody
Nov 20 22:15:28 openHABianPi smbd[1107]: pam_unix(samba:session): session closed for user nobody
Nov 20 22:15:28 openHABianPi smbd[1111]: pam_unix(samba:session): session closed for user nobody
Nov 20 22:15:29 openHABianPi smbd[1115]: pam_unix(samba:session): session closed for user nobody
Nov 20 22:15:29 openHABianPi smbd[1119]: pam_unix(samba:session): session closed for user nobody
[22:15:57] openhabian@openHABianPi:~$
I have installed with openHABian Config Tool 66 (not 67) and I have no edit an additional config file.
I have installed followed the docu OpenHABian -> Quick Start -> Raspberry Pi
And here is writting: "Connect to the Samba network shares with username openhabian and password openhabian" and the link jump direct to “Mounting Locally”. There is no hint to configure someone else!??
I’m getting out of ideas. Try to reinstall the samba service using openhabian-config tool. If it doesn’t help, show us your /etc/samba/smb.conf file. You can upload it somewhere if you can’t post it here.
I have reinstalled with the openhabian-config tool and get followed output:
2018-11-20_23:20:28_CET [openHABian] Checking for root privileges... OK
2018-11-20_23:20:28_CET [openHABian] Loading configuration file '/etc/openhabian.conf'... OK
2018-11-20_23:20:42_CET [openHABian] openHABian configuration tool version: [master]v1.4.1-418(d84ba3b)
2018-11-20_23:20:42_CET [openHABian] Checking for changes in origin... OK
2018-11-20_23:22:05_CET [openHABian] Setting up Samba network shares... Copying over custom 'smb.conf'...
Writing authentication data to openHABian default...
$ systemctl enable smbd.service
Synchronizing state of smbd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable smbd
$ systemctl restart smbd.service
OK
2018-11-20_23:22:12_CET [openHABian] Checking for default openHABian username:password combination... FAILED
2018-11-20_23:22:14_CET [openHABian] We hope you got what you came for! See you again soon ;)
What he mean with “Checking for default openHABian username:password combination… FAILED”. The system is a new OpenHABian installation on a Raspi 3B+ and I have not change the openhabian password.
Here my smb.conf file in txt format: smb.conf.txt (9.3 KB)
But I think the problem is Windows 10. I have installed a VirtualBox VM with ubuntu 18.04 and if I input “smb://192.168.178.158” in the file-explorer and put my username and password, the folder are prompt displayed.
Only Windows 10 do not work with “smb://192.168.178.158” in the file-explorer.
Have you an idea?
Windows uses back slashes, not forward slashes so that’s why “smb://192.168.178.158” wont work. And I’m quite sure “smb:” prefix is not needed.
So it’s definely a problem with your windows os then. Have you checked your firewall settings? One weird solution what I found was changing the host name of your windows machine. Can’t remember why it helped though.
SMBv3 is used. Here’s a picture how to enable v1 support in win 10. You can try aso this.