From 9c72dd78f25be4a7ffa5af5a242670ec76930d6f Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Sat, 12 Mar 2005 22:34:38 +0000 Subject: Use new definition of , fixes a bunch of validity errors. (This used to be commit 3eb5c35e47951f320f7c2f4cd478a95f6d48236e) --- docs/Samba-HOWTO-Collection/Diagnosis.xml | 40 +++++++++++++++---------------- 1 file changed, 20 insertions(+), 20 deletions(-) (limited to 'docs/Samba-HOWTO-Collection/Diagnosis.xml') diff --git a/docs/Samba-HOWTO-Collection/Diagnosis.xml b/docs/Samba-HOWTO-Collection/Diagnosis.xml index f6403dcf2c..2f55626683 100644 --- a/docs/Samba-HOWTO-Collection/Diagnosis.xml +++ b/docs/Samba-HOWTO-Collection/Diagnosis.xml @@ -58,9 +58,9 @@ lines shown in the next example. smb.conf with [tmp] share [tmp] -commenttemporary files -path/tmp -read onlyyes +temporary files +/tmp +yes @@ -244,10 +244,10 @@ the &smb.conf; file entries as shown in the next example< Configuration for only allowing connections from a certain subnet [globals] ... -hosts denyALL -hosts allowxxx.xxx.xxx.xxx/yy -interfaceseth0 -bind interfaces onlyYes +ALL +xxx.xxx.xxx.xxx/yy +eth0 +Yes ... @@ -263,9 +263,9 @@ To solve this problem, change these lines as shown in the Configuration for allowing connections from a certain subnet and localhost [globals] ... -hosts denyALL -hosts allowxxx.xxx.xxx.xxx/yy 127. -interfaceseth0 lo +ALL +xxx.xxx.xxx.xxx/yy 127. +eth0 lo ... @@ -347,7 +347,7 @@ messages from several hosts. If this does not give a similar result to the previous test, then nmblookup isn't correctly getting your broadcast address through its automatic mechanism. In this case you should experiment with the -interfaces option in &smb.conf; to manually configure your IP + option in &smb.conf; to manually configure your IP address, broadcast and netmask. @@ -400,19 +400,19 @@ If it says bad password, then the likely c - Your valid users configuration is incorrect. + Your configuration is incorrect. - You have a mixed case password and you haven't enabled the password level option at a high enough level. + You have a mixed case password and you haven't enabled the option at a high enough level. - The path line in &smb.conf; is incorrect. Check it with &testparm;. + The line in &smb.conf; is incorrect. Check it with &testparm;. @@ -502,7 +502,7 @@ and other config lines in &smb.conf; are correct. It's also possible that the server can't work out what user name to connect you as. To see if this is the problem, add the line -userusername to the +username to the [tmp] section of &smb.conf; where username is the username corresponding to the password you typed. If you find this @@ -511,7 +511,7 @@ fixes things, you may need the username mapping option. It might also be the case that your client only sends encrypted passwords -and you have encrypt passwordsno in &smb.conf;. +and you have no in &smb.conf;. Change this to "yes" to fix this. @@ -530,7 +530,7 @@ master browser for that workgroup. If you do not, then the election process has failed. Wait a minute to see if it is just being slow, then try again. If it still fails after that, then look at the browsing options you have set in &smb.conf;. Make -sure you have preferred masteryes to ensure that +sure you have yes to ensure that an election is held at startup. @@ -546,9 +546,9 @@ of the server and get a list of shares. If you get the error message inva 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 -securityserver and -password serverWindows_NT_Machine in your -&smb.conf; file, or make sure encrypt passwords is +server and +Windows_NT_Machine in your +&smb.conf; file, or make sure is set to yes. -- cgit