You are not logged in.
Hello,
I'm trying to access Samaba share using smbclient. My system is up-to-date and I installed smbclient package. When I try to run it if fails with following error:
[goofy@tjankowski-laptop ~]$ smbclient -L 192.168.11.23 -U http
directory_create_or_exist: mkdir failed on directory /var/lib/samba/private/msg.sock: Permission denied
Unable to initialize messaging context
do_connect: Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED)
[goofy@tjankowski-laptop ~]$
My smb.conf is empty. Do you have any idea what can be wrong? Should I change /var/lib/samba/private/msg.sock permissions so normal user can modify it?
Offline
Should I change /var/lib/samba/private/msg.sock permissions so normal user can modify it?
No, those files are supposed to be created by scripts / services .
post output of
$ smbtree -b -N
please.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
goofy@tjankowski-laptop ~]$ smbtree -b -N
Unable to initialize messaging context
Huh, this is even more surprising to me.
Offline
yep, unfortunately my smb knowledge is not great.
I do suggest you change the title to reflect this is probably a setup problem.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
i don't think an empty smb.conf can work
ezik
Offline
"Unable to initialize messaging context" is just [lost of swearing here] noise, there's a problem w/ the share - "NT_STATUS_CONNECTION_REFUSED" suggests there's none, so that's the side to check first.
Offline