Shares troubleshooting

Trying Various Ways

In windows 7, you can try various things in the Credential manager under Control Panel -> Al Control Panel Items -> Credential Manager. See this thread in the forums.

Access Problems

Access issues are caused by two things, one on top of each other: Linux access and if that works, Windows (SMB/Samba) access

So, to diagnose things, make sure you can access the files you are interested in from Linux. If that works, make sure then that the share pointing to your files is accesible to the user that is trying to access it via Samba

• First make sure that your workgroup or domain match between your HDA and your clients. For your HDA's workgroup/domain, go to Setup -> Settings and turn on advanced settings, after that, go to Setup -> Shares -> Settings and check the workgroup name.
• Make sure the user has permissions to at least read the share (of course)
• In at least Windows 7, we have observed that the operating system tries to use a "Domain" of the name of the computer, which is wrong! Try typing this in the Username field:

      YOURWORKGROUP\username

• So, if your username is jdoe and the workgroup is HOME, try HOME\jdoe
• Some windows clients for some reason may require the whole DNS path, so if your internal domain is, say, home.com, try:

           \\hda.home.com

Permission Problems

If you cannot write to the shares, there are two things to check.

• Permissions at the SAMBA level
• Permissions at the Linux level

At the SAMBA level, check Setup -> Shares. Make sure the user has access to the share you are looking at.

At the Linux level, you have to ssh into your HDA or login at the console and try to write a file in to the folder for the share (typically in /var/hda/files/FOO, if you did not change the default path).

Further Debugging

For actual debugging, follow the details of the Shares Debug page.

Other

NOTE: we used to have a bug in Amahi 5.0 where users that use ANY capital letters were not created properly. Please stick to users with all lowercase letters. This was fixed in Amahi 5.1.

(This appears to be a problem in shadow-utils in Fedora. For status, see Amahi bug 395 and Fedora bug 550732.)