Amahi Forums

Hi,

I have the server up and running fine, and can read/write to all the shares with finder on mac, or via ssh/scp on linux. On Windows though, and I can see and read all the shares, but I cannot write to them. It tells me I don't have permission.

I have set up samba to allow guest access for rw on all shares. I have tried using both guest login and my login on the server as the credentials for windows to use, but it always tells me I don't have permission. Is there something magical that needs to get setup on windows in order to write to any of the shares? I have tried both mapping the hda as a network drive and as a network location with same results.

Thanks,
Craig

Recommend you check out the wiki guidance.
https://wiki.amahi.org/index.php/Shares_troubleshooting

Hi there - I'm having the same issue and I didn't find anything helpful on the page linked above. I have gotten to the point where I can run chown on any one user and THEY have access, but similar commands for groups don't seem to work. The interesting thing is that this started about the time I tried to install transmission. I've tried removing transmission since, but the group still seems to exist.
My linux-fu has improved greatly in my time using amahi (which I absolutely love), but this situation is making it nearly impossible to use the file shares. Does anyone know of a way I can get these shares accessible again for all users?

Thank you!

[update] So I think I have a temp workaround - chown -r :users /var/hda/files got me most of the way. I have to edit my smb.conf to turn the writeable property of [Pictures] to yes, however, and that appears to get overwritten periodically. Is there a more permanent way to fix that?

Thanks again!

Do the following as root user: Replace 1stadminuser with the user you initially created when installing Amahi.

I have to edit my smb.conf to turn the writeable property of [Pictures] to yes, however, and that appears to get overwritten periodically. Is there a more permanent way to fix that?

You set the status of read write for shares via the dashboard Shares tab.

If this does not help, then will need more forensics to determine the problem.