(in both cases you should be asked for the password, use the same username and password you used originally)Ĭ.-Make sure the shared folder you're sharing has permissions to share with the newly-created user. Sudo /opt/local/bin/smbpasswd -e username Sudo /opt/local/bin/smbpasswd -a username Only do this if you don't have any other accesses or shared folders, since essentially it's opening up your shared folders to the network (if it makes them work you can disable one or the other to find which one did it).ģ.-If the above doesn't help you (although #1 should be mandatory) you can try creating a share-only user and use that to connect:Ī.-In the Accounts system preferences sections create a new user as "sharing only", take note of the short username and password.ī.-Open the terminal and create the special user for Samba: The former forces all connections to your shared disk to be mapped to your user and the latter forces all "guests" to be mapped to your user. In case it's falling back to guest access you can change the "force user" line in the "Advanced Shared Disk Settings" to be "cjdery" and the "guest user" in the "Advanced Server Configuration" to "cjdery". This means that either it's falling back to a "guest" account or failing to connect. You are using a local user ("cjdery") but Samba doesn't know about it. If you were sharing "/Users/cjdery/Public" then the destination path should be "/Scans".Ģ.-User permissions are sort of weird for Samba, in the sense that you have to create local users for Samba but they must be shared with the local users. When you're sharing "/Users/cjdery/Public/Scans" then for the remote machine this whole path is "/". 1.-The "remote path" you're defining (destination) is specifying a path that doesn't match the folder you're sharing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |