From 37a6f03f3550321f96200b1357078b308a45f6cd Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 27 May 2003 13:20:26 +0000 Subject: Very large number of markup fixes, layout updates, etc. (This used to be commit 8dfbaafb843d17b865855ba1fef1e62cd38d3964) --- docs/docbook/projdoc/Diagnosis.xml | 52 ++++++++++++++++++++------------------ 1 file changed, 27 insertions(+), 25 deletions(-) (limited to 'docs/docbook/projdoc/Diagnosis.xml') diff --git a/docs/docbook/projdoc/Diagnosis.xml b/docs/docbook/projdoc/Diagnosis.xml index 150f071b78..50c5e1352d 100644 --- a/docs/docbook/projdoc/Diagnosis.xml +++ b/docs/docbook/projdoc/Diagnosis.xml @@ -129,7 +129,7 @@ run ping. -If you get a message saying "host not found" or similar then your DNS +If you get a message saying host not found or similar then your DNS software or /etc/hosts file is not correctly setup. It is possible to run samba without DNS entries for the server and client, but I assume @@ -143,10 +143,12 @@ in question, perhaps by allowing access from another subnet (on Linux this is done via the ipfwadm program.) + -Note: Modern Linux distributions install ipchains/iptables by default. +Modern Linux distributions install ipchains/iptables by default. This is a common problem that is often overlooked. + @@ -165,7 +167,7 @@ temporarily remove any hosts allow, hosts deny -If you get a "connection refused" response then the smbd server may +If you get a connection refused response then the smbd server may not be running. If you installed it in inetd.conf then you probably edited that file incorrectly. If you installed it as a daemon then check that it is running, and check that the netbios-ssn port is in a LISTEN @@ -180,7 +182,7 @@ this network super daemon. -If you get a "session request failed" then the server refused the +If you get a session request failed then the server refused the connection. If it says "Your server software is being unfriendly" then its probably because you have invalid command line parameters to &smbd;, or a similar fatal problem with the initial startup of &smbd;. Also @@ -213,7 +215,7 @@ To solve this problem change these lines to: -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 @@ -224,7 +226,8 @@ fixed soon). 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 +on port 139, such as Samba +(ie: &smbd; is running from inetd already) or something like Digital's Pathworks. Check your inetd.conf file before trying to start &smbd; as a daemon, it can avoid a lot of frustration! @@ -288,8 +291,8 @@ This time we are trying the same as the previous test but are trying it via a broadcast to the default broadcast address. A number of Netbios/TCPIP hosts on the network should respond, although Samba may not catch all of the responses in the short time it listens. You -should see "got a positive name query response" messages from several -hosts. +should see got a positive name query response +messages from several hosts. @@ -332,12 +335,12 @@ as follows: Once you enter the password you should get the smb> prompt. If you -don't then look at the error message. If it says "invalid network -name" then the service "tmp" is not correctly setup in your &smb.conf;. +don't then look at the error message. If it says invalid network +name then the service "tmp" is not correctly setup in your &smb.conf;. -If it says "bad password" then the likely causes are: +If it says bad password then the likely causes are: @@ -369,8 +372,7 @@ If it says "bad password" then the likely causes are: - you enabled password encryption but didn't create the SMB encrypted - password file + you enabled password encryption but didn't map unix to samba users @@ -394,7 +396,7 @@ list of available shares on the server. -If you get a "network name not found" or similar error then netbios +If you get a network name not found or similar error then netbios name resolution is not working. This is usually caused by a problem in nmbd. To overcome it you could do one of the following (you only need to choose one of them): @@ -421,7 +423,7 @@ to choose one of them): -If you get a "invalid network name" or "bad password error" then the +If you get a invalid network name or bad password error then the same fixes apply as they did for the smbclient -L test above. In particular, make sure your hosts allow line is correct (see the man pages) @@ -436,7 +438,7 @@ name and password. -If you get "specified computer is not receiving requests" or similar +If you get specified computer is not receiving requests or similar it probably means that the host is not contactable via tcp services. Check to see if the host is running tcp wrappers, and if so add an entry in the hosts.allow file for your client (or subnet, etc.) @@ -448,16 +450,16 @@ the hosts.allow file for your client (or subnet, etc.) Run the command net use x: \\BIGSERVER\TMP. You should -be prompted for a password then you should get a "command completed -successfully" message. If not then your PC software is incorrectly +be prompted for a password then you should get a command completed +successfully message. If not then your PC software is incorrectly installed or your smb.conf is incorrect. make sure your hosts allow 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 user = +username 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. @@ -465,7 +467,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 passwords = no in &smb.conf; Turn it back on to fix. @@ -484,7 +486,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 master = yes to ensure that an election is held at startup. @@ -500,9 +502,9 @@ 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 +security = server AND +password server = Windows_NT_Machine in your +&smb.conf; file, or make sure encrypted passwords is set to "yes". -- cgit