From c5151b62679edd11940023e757378c7aac66933a Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Fri, 14 Sep 2012 09:28:06 -0700 Subject: docs: Update docs to the modern age of Samba 4.0 This removes references to security=share, security=server and other outdated things. It also updates to a world where encrypted passwords are the norm. Andrew Bartlett --- docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml | 40 ++++++++--------------------- 1 file changed, 11 insertions(+), 29 deletions(-) (limited to 'docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml') diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml index 951c879b49..5ea2db2641 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-Diagnosis.xml @@ -130,9 +130,9 @@ configuration file is faulty. /etc/samba -/usr/local/samba/lib +/usr/local/samba/etc Your &smb.conf; file may be located in /etc/samba -or in /usr/local/samba/lib. +or in /usr/local/samba/etc. @@ -431,8 +431,9 @@ If it says bad password, then the likely c - You have shadow passwords (or some other password system) but didn't - compile in support for them in &smbd;. + Password encryption is enabled by default, but you have not + yet set a password for your samba user. Run + smbpasswd -a username @@ -444,7 +445,8 @@ If it says bad password, then the likely c - You have a mixed-case password and you haven't enabled the option at a high enough level. + You have explicitly disabled encrypted passwords with + no have a mixed-case password and you haven't enabled the option at a high enough level. @@ -454,12 +456,6 @@ If it says bad password, then the likely c - - - You enabled password encryption but didn't map UNIX to Samba users. Run - smbpasswd -a username - - @@ -544,17 +540,7 @@ and other config lines in &smb.conf; are correct. -It's also possible that the server can't work out what username to connect you as. -To see if this is the problem, add the line -username to the - section of -&smb.conf; where username is the -username corresponding to the password you typed. If you find this -fixes things, you may need the username mapping option. - - - -It might also be the case that your client only sends encrypted passwords +By default, most clients only sends encrypted passwords and you have no in &smb.conf;. Change this setting to `yes' to fix this. @@ -587,13 +573,9 @@ From file manager, try to browse the server. Your Samba server should appear in the browse list of your local workgroup (or the one you specified in &smb.conf;). You should be able to double-click on the name of the server and get a list of shares. If you get the error message invalid password, - you are probably running Windows NT and it -is refusing to browse a server that has no encrypted password -capability and is in user-level security mode. In this case, either set -server and -Windows_NT_Machine in your -&smb.conf; file or make sure is -set to yes. +your client may be refusing to browse a server that has no encrypted password +capability. In this case make sure is +set to yes and repeat the steps in this gude. -- cgit