Shares troubleshooting - Revision history

Bigfoot65: /* Windows 10 Samba Issue */

2018-10-25T01:00:41Z

Windows 10 Samba Issue

2017-05-25T00:36:35Z

Further Debugging

2017-02-15T08:08:02Z

Access Problems

2016-03-07T02:36:37Z

Windows 10 Samba Issue (Amahi 8/9)

2016-03-07T02:36:16Z

Windows 10 Samba Issue (Amahi 8)

2016-01-09T02:56:34Z

Windows 10 Samba Issue (Amahi 8)

2016-01-09T02:52:32Z

Windows 10 (Amahi 8)

2016-01-09T02:46:35Z

Further Debugging

2015-09-15T00:53:20Z

Access Problems

2014-04-02T22:32:41Z

Other

← Older revision		Revision as of 01:00, 25 October 2018
Line 72:		Line 72:

	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]		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 ==		== Further Debugging ==

← Older revision		Revision as of 00:36, 25 May 2017
Line 76:		Line 76:

	For actual debugging, follow the details of the [[Shares Debug]] page.		For actual debugging, follow the details of the [[Shares Debug]] page.
		+
		+
		+	Back to the [[Troubleshooting]].

@@ Line 12: / Line 12: @@
         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:

@@ Line 49: / Line 49: @@
 *Be sure to substitute the username, uid, gid (group ID), server and share names with your real values.
-== Windows 10 Samba Issue (Amahi 8/9) ==
+== 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.

@@ Line 49: / Line 49: @@
 *Be sure to substitute the username, uid, gid (group ID), server and share names with your real values.
-== Windows 10 Samba Issue (Amahi 8) ==
+== Windows 10 Samba Issue (Amahi 8/9) ==
 Sometimes Windows 10 client machines are not able to see the HDA in the home network.  This is a problem with the client machine.

@@ Line 66: / Line 66: @@
 :Then restart the client and things are back to the previous settings.
 == Further Debugging ==
 For actual debugging, follow the details of the [[Shares Debug]] page.

@@ Line 49: / Line 49: @@
 *Be sure to substitute the username, uid, gid (group ID), server and share names with your real values.
-== Windows 10 (Amahi 8) ==
+== Windows 10 Samba Issue (Amahi 8) ==
 Sometimes Windows 10 client machines are not able to see the HDA in the home network.  This is a problem with the client machine.
@@ Line 55: / Line 55: @@
 The following work around will correct the issue:
-On the client machine, open a administrator command prompt and type the following:
+* 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.
+: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:
+* 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.
+:Then restart the client and things are back to the previous settings.
 == Further Debugging ==
 For actual debugging, follow the details of the [[Shares Debug]] page.

@@ Line 5: / Line 5: @@
 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 6, go to Setup &raquo; Settings and turn on advanced settings, after that, go to Shares &raquo; Settings and check the workgroup name. If the DNS domain is home.com, the workgroup will be just home.
+* First make sure that '''your workgroup or samba domain match between your HDA and your clients'''. In Amahi 6 or greater, go to Setup &raquo; Settings and turn on advanced settings, after that, go to Shares &raquo; 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]].

← Older revision		Revision as of 22:32, 2 April 2014
Line 52:		Line 52:

	For actual debugging, follow the details of the [[Shares Debug]] page.		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 [http://bugs.amahi.org/issues/show/395 395] and Fedora bug [https://bugzilla.redhat.com/show_bug.cgi?id=550732 550732].)