This is unbelievable! For I coundn't create usershare as i needed, I made a
share through smb.conf, that was "guest only" and "force user", and it worked.
And after I saw your message, I decided to try again and check all the
permissions and acls. I have created new usershare and it is working!
unfortunately it did not helped :( only show me this:
open_directory: unable to create Новая папка/Новая папка. Error was
NT_STATUS_ACCESS_DENIED
d'oh :(
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
i'm not just standing on one point, writing to lists, i already tried to create
new shares with another names, tried another directories, even tryed to create
not usershare, but smb.conf share:
[Shared]
path = /home/kasak/Shared
guest ok = yes
guest only = yes
writable = yes
so this is not a
Hello Fred. Of course i know about nfs and sshfs. I even know about dav,
included in gnome settings, but i have some another machines and it is more
comfortable to me, to use samba
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe
path statement should not be specified in [homes] section, this is samba built
in section, to dynamically share user home directories.
I am not logged in as kasak, samba users is not the same as system users. To
login as kasak, first I need to add kasak to samba with smbpasswd -a kasak, or
if that was that simple, I would not write to this list.
I have already diff'ed the output of testparm -v and the only difference is
"hostname". I don't think that hostname is the problem. Here is magic:
[kasak@kasakoff ~]$ smbclient kasakoff\\Shared
Enter SAMBA\kasak's password:
Try "help"
ups! Sorry for the noise, send by accident
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Hello everybody. Here is my problem. I have two computers, both with fedora
workstation 27, both with selinux disabled, both fully updated. Both have the
same configuration of samba:
[global]
workgroup = WORKGROUP
security = user
passdb backend = tdbsam
printing
