Cannot access Samba share on Windows 10

1

Hi,
I have tried every thing mentioned in different forums to access Samba share via windows 10 but still getting error
cannot access \192.168.1.3 ( note I have used double back slash, this editor doesn’t show double back slash!)

Error code: 0x80004005

Note that the following cmd gives error on raspberry pi that no directory exists. Rest I have followed all the steps on OpenHAB
sudo chown -R openhab:openhab /opt /etc/openhab2

See the output for ```
openhab-cli info

Version:     2.4.0 (Build)

User:        openhab (Active Process 518)
User Groups: openhab tty dialout audio bluetooth gpio

Directories: Folder Name      | Path                        | User:Group
             -----------      | ----                        | ----------
             OPENHAB_HOME     | /usr/share/openhab2         | openhab:openhab
             OPENHAB_RUNTIME  | /usr/share/openhab2/runtime | openhab:openhab
             OPENHAB_USERDATA | /var/lib/openhab2           | openhab:openhabian
             OPENHAB_CONF     | /etc/openhab2               | openhab:openhab
             OPENHAB_LOGDIR   | /var/log/openhab2           | openhab:openhabian

URLs:        http://192.168.1.3:8080
             https://192.168.1.3:8443
2

Please follow the docs as this should work without any problems:

Also don’t mix up manual and repository installation:

That command is nowhere in the docs, so why would you execute this? The part

/opt/openhab2/conf

is for manual installations only.
If you are on a openHABian install you can open the Configuration Tool and setup samba:

1 Like
3

It looks like a window issue as I was able to access the share via Andorid device SMB apps.
Not sure what needs to done to make it work.

4

Re-install OpenHabian and at least start seeing openhabianPi in network. Added settings in Firewall. All good now.

5

Anybody aware of some changes? Can’t access my openhab smb shares anymore from my win10 pc. Works from mac. It used to work on the same win10 pc (enabled smb v1 in the past), but perhaps with some of the latest updates something broke again?