Trusted, Bureaucrats, Administrators
12,424
edits
Changes
From Amahi Wiki
→Windows 10 Samba Issue
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 files you are interested in from Linux.
* First make sure that '''your workgroup or samba domain match between your HDA and your clients'''. In Amahi 7, the default is Workgroup and cannot be changed in the UI. In Amahi 6or greater, go to Setup » Settings and turn on advanced settings, after that, go to Shares » Settings and check the workgroup name. If the DNS domain is home.com, the workgroup will be just home.
* 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]].
YOURWORKGROUP\username
So, if your username is jdoe and the workgroup is HOME, try HOME\jdoe
* 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
* Some windows clients for some reason may require the whole DNS path, so if your internal domain is, say, home.com, try:
mount -t cifs -o user=user,uid=user,gid=users \\hda\Music Music/
*Be sure to substitute the 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 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/mrxsmb10/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://forums.amahi.org/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 have a need to remove the 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.
