Troubleshooting Windows shares (samba) - Revision history

Ramuk: /* Windows Vista */

Ramuk — Mon, 14 May 2007 04:48:14 GMT

Windows Vista

← Older revision		Revision as of 04:48, 14 May 2007
Line 13:		Line 13:

	== Windows Vista ==		== Windows Vista ==
-	A samba "bug" has been fixed in samba v3.0.22 <ref>[http://us4.samba.org/samba/docs/ Samba Documentation]</ref><ref> http://www.samba.org/ The samba web site</ref><ref> http://us4.samba.org/samba/docs/using_samba/toc.html "Using Samba", by Ts, Eckstein, and Collier-Brown (O'Reilly)</ref>	+	A samba "bug" has been fixed in samba v3.0.22 <ref>[http://us4.samba.org/samba/docs/ Samba Documentation]</ref><ref> http://www.samba.org/ The samba web site</ref><ref> http://us4.samba.org/samba/docs/using_samba/toc.html "Using Samba", by Ts, Eckstein, and Collier-Brown (O'Reilly)</ref> To connect a password protected samba share from Vista <ref>[http://www.scalefree.info/2006/09/vista_and_buffalo_terastation.html Vista and Buffalo Terastation]</ref> on a [[w:Buffalo network-attached storage series\|Buffalo network-attached storage series]] device using an older version of [[Samba]] (ie Pre v3.0.22), you need to do the following:
-		+
-		+
-	To connect a ~~passwort~~ protected share from Vista ~~see:~~	+
-		+
-	http://www.scalefree.info/2006/09/vista_and_buffalo_terastation.html	+
-		+
-	~~"Just a note in case anyone else runs into this problem.~~	+
-		+
-	~~If you want to connect to a share~~ on a Buffalo ~~Terastation (which~~	+
-	~~seems to be~~ using Samba) ~~from a Windows Vista installation~~, you need	+
-	to do the following:	+
	# Run the Local Security Policy app - secpol.msc		# Run the Local Security Policy app - secpol.msc
	# Go to Local Policies \| Security Options and choose the "Network		# Go to Local Policies \| Security Options and choose the "Network
	# Security: LAN Manager Authentican Level" item		# Security: LAN Manager Authentican Level" item
	# Set it to "Send LM & NLTM, use NTMLv2 session if negotiated"		# Set it to "Send LM & NLTM, use NTMLv2 session if negotiated"
-
-	~~And that should sort you out."~~
-	~~Works also with my Linkstation's Samba version 2.2.8a-ja-1.1.~~

	If for some reason your “secpol.msc” refuses to work, you can manually change a setting in the Windows registery.		If for some reason your “secpol.msc” refuses to work, you can manually change a setting in the Windows registery.

-	1- Go in the “Execute command window” and type “regedit” and press “OK”, it will pop the Windows registery window.	+	# Go in the “Execute command window” and type “regedit” and press “OK”, it will pop the Windows registery window.
-		+	# Browse the this key: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\” and change the value for the option “LMCompatibilityLevel” from value 3 to a value 1.
-	2- Browse the this key: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\” and change the value for the option “LMCompatibilityLevel” from value 3 to a value 1.	+
-		+

	== Are you using the same workgroup ? ==		== Are you using the same workgroup ? ==

Ramuk at 22:42, 13 May 2007

Ramuk — Sun, 13 May 2007 22:42:56 GMT

← Older revision		Revision as of 22:42, 13 May 2007
Line 1:		Line 1:
	{{Articles\|FAQ\|Mediaserver}}		{{Articles\|FAQ\|Mediaserver}}
-	= Troubleshooting Windows shares (samba) =	+	= Troubleshooting Windows shares ([[samba]]) =

	== On your Windows machines, use DHCP ==		== On your Windows machines, use DHCP ==

Types474 at 08:30, 11 May 2007

Types474 — Fri, 11 May 2007 08:30:16 GMT

← Older revision		Revision as of 08:30, 11 May 2007
Line 31:		Line 31:

	And that should sort you out."		And that should sort you out."
-
	Works also with my Linkstation's Samba version 2.2.8a-ja-1.1.		Works also with my Linkstation's Samba version 2.2.8a-ja-1.1.
		+
		+	If for some reason your “secpol.msc” refuses to work, you can manually change a setting in the Windows registery.
		+
		+	1- Go in the “Execute command window” and type “regedit” and press “OK”, it will pop the Windows registery window.
		+
		+	2- Browse the this key: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\” and change the value for the option “LMCompatibilityLevel” from value 3 to a value 1.
		+

	== Are you using the same workgroup ? ==		== Are you using the same workgroup ? ==

24.241.108.152: /* Windows Vista */

24.241.108.152 — Mon, 02 Apr 2007 02:18:58 GMT

Windows Vista

← Older revision		Revision as of 02:18, 2 April 2007
Line 25:		Line 25:
	seems to be using Samba) from a Windows Vista installation, you need		seems to be using Samba) from a Windows Vista installation, you need
	to do the following:		to do the following:
-	Run the Local Security Policy app - secpol.msc	+	# Run the Local Security Policy app - secpol.msc
-	Go to Local Policies \| Security Options and choose the "Network	+	# Go to Local Policies \| Security Options and choose the "Network
-	Security: LAN Manager Authentican Level" item	+	# Security: LAN Manager Authentican Level" item
-	Set it to "Send LM & NLTM, use NTMLv2 session if negotiated"	+	# Set it to "Send LM & NLTM, use NTMLv2 session if negotiated"

	And that should sort you out."		And that should sort you out."

-	Works also with my Linkstation's ~~Samva~~ version 2.2.8a-ja-1.1.	+	Works also with my Linkstation's Samba version 2.2.8a-ja-1.1.

	== Are you using the same workgroup ? ==		== Are you using the same workgroup ? ==

WizardFusion: /* Are you using the same workgroup ? */

WizardFusion — Sat, 04 Nov 2006 17:41:11 GMT

Are you using the same workgroup ?

← Older revision		Revision as of 17:41, 4 November 2006
Line 37:		Line 37:
	Make sure that the '''workgroup''' you use is the same that your windows computers use:		Make sure that the '''workgroup''' you use is the same that your windows computers use:
	*Defined in '''Windows ;ControlPanel:Network:Identification_Tab:Workgroup_field'''		*Defined in '''Windows ;ControlPanel:Network:Identification_Tab:Workgroup_field'''
-	*For a workgroup '''MSHOME''' these lines should appear in <tt>/etc/smb.conf</tt>	+	*For a workgroup '''MSHOME''' these lines should appear in <tt>/etc/samba/smb.conf</tt>
	[global]		[global]
	workgroup = MSHOME		workgroup = MSHOME

85.181.50.141: /* Windows Vista */

85.181.50.141 — Thu, 12 Oct 2006 20:37:33 GMT

Windows Vista

← Older revision		Revision as of 20:37, 12 October 2006
Line 32:		Line 32:
	And that should sort you out."		And that should sort you out."

-	Works also with Linkstation.	+	Works also with my Linkstation's Samva version 2.2.8a-ja-1.1.

	== Are you using the same workgroup ? ==		== Are you using the same workgroup ? ==

85.181.50.141: /* Windows Vista */

85.181.50.141 — Thu, 12 Oct 2006 20:31:44 GMT

Windows Vista

← Older revision		Revision as of 20:31, 12 October 2006
Line 14:		Line 14:
	== Windows Vista ==		== Windows Vista ==
	A samba "bug" has been fixed in samba v3.0.22 <ref>[http://us4.samba.org/samba/docs/ Samba Documentation]</ref><ref> http://www.samba.org/ The samba web site</ref><ref> http://us4.samba.org/samba/docs/using_samba/toc.html "Using Samba", by Ts, Eckstein, and Collier-Brown (O'Reilly)</ref>		A samba "bug" has been fixed in samba v3.0.22 <ref>[http://us4.samba.org/samba/docs/ Samba Documentation]</ref><ref> http://www.samba.org/ The samba web site</ref><ref> http://us4.samba.org/samba/docs/using_samba/toc.html "Using Samba", by Ts, Eckstein, and Collier-Brown (O'Reilly)</ref>
		+
		+
		+	To connect a passwort protected share from Vista see:
		+
		+	http://www.scalefree.info/2006/09/vista_and_buffalo_terastation.html
		+
		+	"Just a note in case anyone else runs into this problem.
		+
		+	If you want to connect to a share on a Buffalo Terastation (which
		+	seems to be using Samba) from a Windows Vista installation, you need
		+	to do the following:
		+	Run the Local Security Policy app - secpol.msc
		+	Go to Local Policies \| Security Options and choose the "Network
		+	Security: LAN Manager Authentican Level" item
		+	Set it to "Send LM & NLTM, use NTMLv2 session if negotiated"
		+
		+	And that should sort you out."
		+
		+	Works also with Linkstation.

	== Are you using the same workgroup ? ==		== Are you using the same workgroup ? ==

160.39.42.155: /* Are file names mangled? Try setting the charset */

160.39.42.155 — Wed, 30 Aug 2006 01:43:09 GMT

Are file names mangled? Try setting the charset

← Older revision		Revision as of 01:43, 30 August 2006
Line 54:		Line 54:

	==Are file names mangled? Try setting the charset==		==Are file names mangled? Try setting the charset==
-	If you find that files copied to your ~~samba~~ share work fine when using ~~samba~~, but appear with garbled characters when accessed through SSH or SCP (e.g. "menú" shows up as "menÃº"), the problem is probably the charset you are using. You will need to set the <tt>unix charset</tt> variable in the global section of the smb.conf file to the correct value. For example, if you are using Latin1 in ~~windows~~, you set:	+	If you find that files copied to your Samba share work fine when using Samba, but appear with garbled characters when accessed through SSH or SCP (e.g. "menú" shows up as "menÃº"), the problem is probably the charset you are using. You will need to set the <tt>unix charset</tt> variable in the global section of the <tt>smb.conf</tt> file to the correct value. For example, if you are using Latin1 in Windows, you set:
	unix charset = ISO8859-1		unix charset = ISO8859-1

	=References=		=References=
	<references/>		<references/>

160.39.42.155: /* Are file names mangled? Try setting the charset */

160.39.42.155 — Wed, 30 Aug 2006 01:42:29 GMT

Are file names mangled? Try setting the charset

← Older revision		Revision as of 01:42, 30 August 2006
Line 54:		Line 54:

	==Are file names mangled? Try setting the charset==		==Are file names mangled? Try setting the charset==
-	If you find that files copied to your samba share work fine when using samba, but appear with garbled characters when accessed through SSH or SCP (e.g. "menú" shows up as "menÃº"), the problem is probably the charset ~~to use~~. You will need to set the <tt>unix charset</tt> variable in the global section of the smb.conf file to the correct value. For example, if you are using Latin1 in windows, you set:	+	If you find that files copied to your samba share work fine when using samba, but appear with garbled characters when accessed through SSH or SCP (e.g. "menú" shows up as "menÃº"), the problem is probably the charset you are using. You will need to set the <tt>unix charset</tt> variable in the global section of the smb.conf file to the correct value. For example, if you are using Latin1 in windows, you set:
	unix charset = ISO8859-1		unix charset = ISO8859-1

	=References=		=References=
	<references/>		<references/>

160.39.42.155: /* Try adding guest access */ File name mangling

160.39.42.155 — Wed, 30 Aug 2006 01:41:32 GMT

Try adding guest access: File name mangling

← Older revision		Revision as of 01:41, 30 August 2006
Line 52:		Line 52:
	5. Doubleclick the icon to see the '''share''' directory.<br>		5. Doubleclick the icon to see the '''share''' directory.<br>
	6. Navigate to the '''share''' directory.<br>		6. Navigate to the '''share''' directory.<br>
		+
		+	==Are file names mangled? Try setting the charset==
		+	If you find that files copied to your samba share work fine when using samba, but appear with garbled characters when accessed through SSH or SCP (e.g. "menú" shows up as "menÃº"), the problem is probably the charset to use. You will need to set the <tt>unix charset</tt> variable in the global section of the smb.conf file to the correct value. For example, if you are using Latin1 in windows, you set:
		+	unix charset = ISO8859-1

	=References=		=References=
	<references/>		<references/>