From 8e4bcf45b714960b7003ff47a15e32302287e563 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Tue, 28 Jun 2005 21:23:26 +0000 Subject: Update. (This used to be commit b0d79e4c3536c5c8d66da6d469344c5a8ad3ea3b) --- docs/Samba3-HOWTO/TOSHARG-Diagnosis.xml | 77 ++++++++++++++++++++++++++------- 1 file changed, 62 insertions(+), 15 deletions(-) (limited to 'docs/Samba3-HOWTO') diff --git a/docs/Samba3-HOWTO/TOSHARG-Diagnosis.xml b/docs/Samba3-HOWTO/TOSHARG-Diagnosis.xml index b1408f3b60..951c879b49 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Diagnosis.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Diagnosis.xml @@ -14,6 +14,7 @@ Introduction +validate This file contains a list of tests you can perform to validate your Samba server. It also tells you what the likely cause of the problem is if it fails any one of these steps. If it passes all these tests, @@ -71,6 +72,9 @@ Some commands shown did not exist in earlier versions. +error messages +name resolution +/etc/resolv.conf Please pay attention to the error messages you receive. If any error message reports that your server is being unfriendly, you should first check that your IP name resolution is correctly set up. Make sure your /etc/resolv.conf @@ -78,13 +82,21 @@ file points to name servers that really do exist. +DNS server access +name resolution +dns proxy +testparm Also, if you do not have DNS server access for name resolution, please check -that the settings for your &smb.conf; file results in dns proxy = no. The +that the settings for your &smb.conf; file results in dns proxy = no. The best way to check this is with testparm smb.conf. +log files +tail +/usr/local/samba/var +/var/log/samba log filesmonitoring It is helpful to monitor the log files during testing by using the tail -F log_file_name in a separate @@ -117,6 +129,8 @@ configuration file is faulty. +/etc/samba +/usr/local/samba/lib Your &smb.conf; file may be located in /etc/samba or in /usr/local/samba/lib. @@ -124,6 +138,7 @@ or in /usr/local/samba/lib. +ping Run the command ping BIGSERVER from the PC and ping ACLIENT from the UNIX box. If you do not get a valid response, then your TCP/IP software is not correctly installed. @@ -134,13 +149,20 @@ You will need to start a DOS prompt window on the PC to run ping. -If you get a message saying host not found or a similar message, then your DNS -software or /etc/hosts file is not correctly set up. -It is possible to run Samba without DNS entries for the server and client, but it is assumed -you do have correct entries for the remainder of these tests. +/etc/hosts +DNS +/etc/resolv.conf +If you get a message saying host not found or a similar message, then +your DNS software or /etc/hosts file is not correctly set up. If using DNS, check that +the /etc/resolv.conf has correct, current, entries in it. It is possible to run +Samba without DNS entries for the server and client, but it is assumed you do have correct entries for the +remainder of these tests. +firewall +iptables +ipchains Another reason why ping might fail is if your host is running firewall software. You will need to relax the rules to let in the workstation in question, perhaps by allowing access from another subnet (on Linux @@ -156,6 +178,8 @@ This is a common problem that is often overlooked. +iptables +ipchains If you wish to check what firewall rules may be present in a system under test, simply run iptables -L -v, or if ipchains-based firewall rules are in use, ipchains -L -v. @@ -198,6 +222,12 @@ on the UNIX box. You should get back a list of available shares. +bad password +hosts allow +hosts deny +valid users +guest account +invalid users If you get an error message containing the string bad password, then you probably have either an incorrect hosts allow, hosts deny, or valid users line in your @@ -207,7 +237,8 @@ temporarily remove any hosts allow, hosts deny -If you get a message connection refused response, then the smbd server may +inetd.conf +If you get a message 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 @@ -224,7 +255,7 @@ the network super daemon. -If you get a message saying session request failed, the server refused the +If you get a message saying session request failed, the server refused the connection. If it says Your server software is being unfriendly, then it's probably because you have invalid command line parameters to &smbd;, or a similar fatal problem with the initial startup of &smbd;. Also @@ -252,6 +283,7 @@ the &smb.conf; file entries as shown in the next example< +loopback adapter In Configuration for Allowing Connections Only from a Certain Subnet, no allowance has been made for any session requests that will automatically translate to the loopback adapter address 127.0.0.1. To solve this problem, change these lines as shown in the following @@ -278,6 +310,11 @@ lot of frustration! +subnet mask +broadcast address +log.nmbd +network interface +IP address And yet another possible cause for failure of this test is when the subnet mask and/or broadcast address settings are incorrect. Please check that the network interface IP address/broadcast address/subnet mask settings are correct and that Samba has correctly noted these in the log.nmbd file. @@ -288,12 +325,16 @@ settings are correct and that Samba has correctly noted these in the l +nmblookup Run the command nmblookup -B BIGSERVER __SAMBA__. You should get back the IP address of your Samba server. -If you do not, then nmbd is incorrectly installed. Check your inetd.conf +inetd.conf +nmbd +port 137 +If you do not, then &nmbd; is incorrectly installed. Check your inetd.conf if you run it from there, or that the daemon is running and listening to UDP port 137. @@ -309,6 +350,7 @@ inetd. +nmblookup Run the command nmblookup -B ACLIENT `*'. @@ -336,16 +378,15 @@ 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/TCP/IP hosts on the network should respond, although Samba may not catch all of the responses in the short time it listens. You -should see the got a positive name query response +should see the got a positive name query response messages from several hosts. -If this does not give a result similar 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 - option in &smb.conf; to manually configure your IP -address, broadcast, and netmask. +nmblookup +If this does not give a result similar 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 option in &smb.conf; to manually configure your IP address, broadcast, and netmask. @@ -422,6 +463,10 @@ If it says bad password, then the likely c +dir +get +put +help command Once connected, you should be able to use the commands dir, get, put, and so on. Type help command for instructions. You should especially check that the amount of free disk space shown is correct when you type dir. @@ -432,13 +477,15 @@ especially check that the amount of free disk space shown is correct when you ty +net view On the PC, type the command net view \\BIGSERVER. You will need to do this from within a DOS prompt window. You should get back a list of shares available on the server. -If you get a message network name not found or similar error, then NetBIOS +nmbd +If you get a message 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): -- cgit