From 99bde6889d3d8b7a9e950c86c30e82662e1dacdd Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Tue, 9 Sep 2003 02:58:53 +0000 Subject: syncing files from 3.0 into HEAD again (This used to be commit bca0bba209255d0effbae6a3d3b6d298f0952c3a) --- docs/docbook/projdoc/Diagnosis.xml | 87 ++++++++++++++++++-------------------- 1 file changed, 42 insertions(+), 45 deletions(-) (limited to 'docs/docbook/projdoc/Diagnosis.xml') diff --git a/docs/docbook/projdoc/Diagnosis.xml b/docs/docbook/projdoc/Diagnosis.xml index 7e3656c0f3..76984f3076 100644 --- a/docs/docbook/projdoc/Diagnosis.xml +++ b/docs/docbook/projdoc/Diagnosis.xml @@ -52,14 +52,13 @@ You can add a tmp share like this by adding the following to &smb.conf;: - - -[tmp] - comment = temporary files - path = /tmp - read only = yes - - + + smb.conf with [tmp] share +[tmp] +commenttemporary files +path/tmp +read onlyyes + @@ -80,6 +79,8 @@ that the settings for your &smb.conf; file results in dns proxy = notestparm smb.conf. +log filesmonitoring + It is helpful to monitor the log files during testing by using the tail -F log_file_name in a separate @@ -102,6 +103,8 @@ don't forget to restart &smbd; and &nmbd;. Diagnosing your samba server +testparm + In the directory in which you store your &smb.conf; file, run the command @@ -175,6 +178,8 @@ state using netstat -a. +inetd +xinetdinetd Some Unix / Linux systems use xinetd in place of inetd. Check your system documentation for the location of the control file/s for your particular system implementation of @@ -197,11 +202,11 @@ a session request. The most common of these involve one or more of the following &smb.conf; file entries: - - hosts deny = ALL - hosts allow = xxx.xxx.xxx.xxx/yy - bind interfaces only = Yes - + +hosts denyALL +hosts allowxxx.xxx.xxx.xxx/yy +bind interfaces onlyYes + In the above, no allowance has been made for any session requests that @@ -209,22 +214,23 @@ will automatically translate to the loopback adapter address 127.0.0.1. To solve this problem change these lines to: - - hosts deny = ALL - hosts allow = xxx.xxx.xxx.xxx/yy 127. - + +hosts denyALL +hosts allowxxx.xxx.xxx.xxx/yy 127. + -Do not use the bind interfaces only parameter where you +Do not use the bind interfaces only parameter where you may wish to use the samba password change facility, or where &smbclient; may need to access a local service for name resolution or for local resource -connections. (Note: the bind interfaces only parameter deficiency +connections. (Note: the bind interfaces only parameter deficiency where it will not allow connections to the loopback address will be fixed soon). +inetd Another common cause of these two errors is having something already running on port 139, such as Samba (ie: &smbd; is running from inetd already) or @@ -299,13 +305,13 @@ messages from several hosts. If this doesn't 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 +interfaces option in &smb.conf; to manually configure your IP address, broadcast and netmask. If your PC and server aren't on the same subnet then you will need to -use the -B option to set the broadcast address to that of the PCs +use the option to set the broadcast address to that of the PCs subnet. @@ -318,11 +324,13 @@ not correct. (Refer to TEST 3 notes above). +smbclient + Run the command smbclient //BIGSERVER/TMP. You should then be prompted for a password. You should use the password of the account you are logged into the unix box with. If you want to test with -another account then add the -U accountname option to the end of +another account then add the option to the end of the command line. eg: smbclient //bigserver/tmp -Ujohndoe @@ -353,26 +361,25 @@ If it says bad password then the likely causes are: - your valid users configuration is incorrect + your valid users 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 password level option at a high enough level - the path = line in &smb.conf; is incorrect. Check it with &testparm; + the path line in &smb.conf; is incorrect. Check it with &testparm; - you enabled password encryption but didn't map unix to samba users + you enabled password encryption but didn't map unix to samba users. Run smbpasswd -a username. @@ -458,8 +465,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 user = -username to the [tmp] section of +connect you as. To see if this is the problem add the line userusername to the [tmp] 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. @@ -467,7 +473,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 passwords = no in &smb.conf; +and you have encrypt passwordsno in &smb.conf; Turn it back on to fix. @@ -486,7 +492,7 @@ master browser for that workgroup. If you don't 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 master = yes to ensure that +sure you have preferred masteryes to ensure that an election is held at startup. @@ -495,16 +501,16 @@ an election is held at startup. ->From file manager try to browse the server. Your samba server should +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 +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 a "invalid password" error when you do then you are probably running WinNT 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 -security = server AND -password server = Windows_NT_Machine in your -&smb.conf; file, or make sure encrypted passwords is +securityserver AND +password serverWindows_NT_Machine in your +&smb.conf; file, or make sure encrypt passwords is set to "yes". @@ -512,13 +518,4 @@ set to "yes". - -Still having troubles? - -Read the chapter on -Analysing and Solving Problems. - - - - -- cgit