'''NOTE== Access Problems == Access issues are caused by one or two things, in order: at Windows (SMB/Samba) access (domain works, username works), and Linux permissions access So, to diagnose things, make sure you can login first from your client operating system, and then if that works, make sure you can access the moment we have a bug where users that use ANY capital letters files you are not created properlyinterested in from Linux. Please stick to users with all lowercase letters'''
(This appears * First make sure that '''your workgroup or samba domain match between your HDA and your clients'''. In Amahi 6 or greater, go to be a problem in shadow-utils in Fedora. For statusSetup » Settings and turn on advanced settings, after that, see Amahi bug [http://bugs.amahi.org/issues/show/395 395] go to Shares » Settings and Fedora bug [https://bugzillacheck the workgroup name.redhatIf the DNS domain is home.com/show_bug.cgi?id=550732 550732], the workgroup will be just home.)
== Trying Various Ways ==* If only one user can access or write in your shares, and your shares are in a subdirectory of /media, you'll need to unmount your drive from /media, and re-mount it using the instructions found here: [[Adding_a_second_hard_drive_to_your_HDA|How to add additional hard drives in your HDA]].
* In windows at least Windows 7, you can try various things 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 Credential manager under Control Panel -> Al Control Panel Items -> Credential Manager. See this [httpUsername field://forums.amahi.org/viewtopic.php?f=4&t=964&start=11 thread in YOURWORKGROUP\usernameSo, if your username is jdoe and the forums].workgroup is HOME, try HOME\jdoe
== Access Problems ==* In order to confirm the workgroup name sent to samba server, check the logs (most likely located in /var/log/samba/). If the logs don't have enough information, increase the log level to 5 in the smb.conf file (/etc/samba/smb.conf) and restart samba service.** If the domain name in the logs is not same as the workgroup name ("HOME" in example above), Windows is still sending the computer name as the domain name. Try mapping to the shared drive using the following command. Note, password is not supplied in the command. It is recommended that you save the password in Windows Credential Manager (see information below) net use U: \\hda\Movies /USER:YOURWORKGROUP\username /PERSISTENT:YES
* 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
* 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
* Make sure the user has permissions to at least read the share (of course) in the Shares area of your HDA
* Check the Credential manager under Control Panel: Control Panel » All Control Panel Items » Credential Manager: See this [http://forums.amahi.org/viewtopic.php?f=4&t=964&start=11 thread in the forums].
== Permission Problems ==
=== Check permissions on the HDA server ===* If you cannot write to the shares, there permissions at the HDA's SAMBA and Linux levels must be checked.**At the SAMBA level, check Setup » Shares. Make sure the user has access to the share you are two things looking at.**At the Linux level on the HDA, you have to ssh into your HDA or login at the console and try to write a file in to checkthe folder for the share (typically in /var/hda/files/FOO, if you did not change the default path).
* === Troubleshooting Permissions at the SAMBA level* Permissions at the Linux level: Windows Client (including Vista) ===
At *If you cannot access the SAMBA levelshares, check Setup -> Shares. Make sure the user has access to the share and you are looking at.on a Windows Vista machine, there may be other connections open and you may get this error:
At [[File:Errorpermissions.jpeg]] *So we will try doing this:**Start » Type "cmd" into the Linux level, you search bar and press enter**Type in "net use * /delete" to delete all open shared connections**Double check nothing is connected: "net use"**Try connecting to the HDA shares one more time. *Still getting 'not accessible' errors? Users have had luck connecting via cmd on Windows XP clients:**Type in "net use \\hda\Pictures /USER:HOME\jdoe password" Be sure to ssh into substitute the share name, username and password with your real values.**Try connecting to the HDA or login at the console shares one more time. === Troubleshooting Permissions: Linux Client === * If you cannot access shares, and you are on a Linux client, try the following command to write make a file in connection: mount -t cifs -o user=user,uid=user,gid=users \\hda\Music Music/*Be sure to substitute the folder for username, uid, gid (group ID), server and share names with your real values. == Windows 10 Samba Issue == Sometimes Windows 10 client machines are not able to see the share (typically HDA in the home network. This is a problem with the client machine. The following work around will correct the issue: * On the client machine, open a administrator command prompt and type the following: sc.exe config lanmanworkstation depend= bowser/varmrxsmb10/nsi sc.exe config mrxsmb20 start= disabled :Then restart the client and the problem should be fixed. * To reverse the work around, on the client machine open a administrator command prompt and type the following: sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi sc.exe config mrxsmb20 start= auto :Then restart the client and things are back to the previous settings. Ref: [https:/hda/filesforums.amahi.org/FOO, if viewtopic.php?f=8&t=6292&start=10#p35856 Cannot see Amahi HDA on my network after Windows 10 update Forums Post] == Remove Saved Network Passwords == If you did not change have a need to remove the default path)stored network password used to automatically log into your shares from a Windows client, here's how: * [http://support.microsoft.com/kb/306992 Windows XP] * [http://windows.microsoft.com/en-us/windows-vista/remove-stored-passwords Windows Vista] * [http://www.petenetlive.com/KB/Article/0000556.htm Windows 7] * [http://www.jholjhaal.com/manage-stored-passwords-in-windows-8/ Windows 8/10]
== Further Debugging ==
For actual debugging, follow the details of the [[Shares Debug]] page.
Back to the [[Troubleshooting]].
