From 4ea9be5467b6274ec2074af8c6438d42415d8fb6 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Mon, 7 Apr 2003 14:01:19 +0000 Subject: Regenerate docs (This used to be commit 3d61303ea9783e01796a90e74efb3457ef76497f) --- docs/htmldocs/diagnosis.html | 484 ++++++++++++++++++++++++++++++++++--------- 1 file changed, 387 insertions(+), 97 deletions(-) (limited to 'docs/htmldocs/diagnosis.html') diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index 69edc6f0bf..43651c049d 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -67,14 +67,14 @@ CLASS="CHAPTER" >Chapter 32. The samba checklistChapter 33. The samba checklist

32.1. Introduction33.1. Introduction

This file contains a list of tests you can perform to validate your @@ -95,8 +95,8 @@ CLASS="SECT1" >

32.2. Assumptions33.2. Assumptions

In all of the tests it is assumed you have a Samba server called @@ -105,8 +105,21 @@ BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.

The procedure is similar for other types of clients.

It is also assumed you know the name of an available share in your -smb.conf. I will assume this share is called "tmp". You can add a -"tmp" share like by adding the following to smb.conf:

smb.conf. I will assume this share is called tmp. +You can add a tmp share like by adding the +following to smb.conf:

THESE TESTS ASSUME VERSION 3.0.0 OR LATER OF THE SAMBA SUITE. SOME
-COMMANDS SHOWN DID NOT EXIST IN EARLIER VERSIONS
These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions. 
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 you
-IP name resolution is correctly set up. eg: Make sure your /etc/resolv.conf
+IP name resolution is correctly set up. eg: Make sure your /etc/resolv.conf
 file points to name servers that really do exist.
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
-best way to check this is with "testparm smb.conf"
smb.conf file results in dns proxy = no. The
+best way to check this is with testparm smb.conf.

32.3. The tests33.3. The tests

  • In the directory in which you store your smb.conf file, run the command -"testparm smb.conf". If it reports any errors then your smb.conf +>In the directory in which you store your smb.conf file, run the command +testparm smb.conf. If it reports any errors then your smb.conf configuration file is faulty.

    Note: Your smb.conf file may be located in: Your smb.conf file may be located in: /etc/samba - Or in: /usr/local/samba/lib

  • Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from +>Run the command ping BIGSERVER from the PC and +ping ACLIENT from the unix box. If you don't get a valid response then your TCP/IP software is not correctly installed.

    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 +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 you do have correct entries for the remainder of these tests.

    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 -this is done via the ipfwadm program.)

    ipfwadm program.)

  • Run the command "smbclient -L BIGSERVER" on the unix box. You +>Run the command smbclient -L BIGSERVER on the unix box. You should get a list of available shares back.

    If you get a error message containing the string "Bad password" then -you probably have either an incorrect "hosts allow", "hosts deny" or -"valid users" line in your smb.conf, or your guest account is not -valid. Check what your guest account is using "testparm" and -temporarily remove any "hosts allow", "hosts deny", "valid users" or -"invalid users" lines.

    hosts allow, +hosts deny or valid users line in your +smb.conf, or your guest account is not +valid. Check what your guest account is using testparm and +temporarily remove any hosts allow, hosts deny, valid users or invalid users lines.

    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 -state using "netstat -a".

    netstat -a.

    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 -check your config file (smb.conf) for syntax errors with "testparm" +its probably because you have invalid command line parameters to smbd, +or a similar fatal problem with the initial startup of smbd. Also +check your config file (smb.conf) for syntax errors with testparm and that the various directories where samba keeps its log and lock files exist.

    There are a number of reasons for which smbd may refuse or decline a session request. The most common of these involve one or more of -the following smb.conf file entries:

    smb.conf file entries:

    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
+>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 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).
    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
-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!
    And yet another possible cause for failure of TEST 3 is when the subnet mask
+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!
    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.nmb file.
    log.nmb file.

  • Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the +>Run the command nmblookup -B BIGSERVER __SAMBA__. You should get the IP address of your Samba server back.

    If you don't then nmbd is incorrectly installed. Check your inetd.conf +>If you don't 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.

  • run the command nmblookup -B ACLIENT '*'run the command nmblookup -B ACLIENT '*'

    You should get the PCs IP address back. If you don't then the client @@ -272,9 +446,9 @@ client in the above test.

  • Run the command nmblookup -d 2 '*'Run the command nmblookup -d 2 '*'

    This time we are trying the same as the previous test but are trying @@ -287,11 +461,20 @@ 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 use 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 the that of the PCs +use the -B option to set the broadcast address to the that of the PCs subnet.

    This test will probably fail if your subnet mask and broadcast address are @@ -299,29 +482,65 @@ not correct. (Refer to TEST 3 notes above).

  • Run the command smbclient //BIGSERVER/TMPRun 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 -U accountname option to the end of the command line. eg: -smbclient //bigserver/tmp -Ujohndoesmbclient //bigserver/tmp -Ujohndoe

    Note: It is possible to specify the password along with the username +>It is possible to specify the password along with the username as follows: -smbclient //bigserver/tmp -Ujohndoe%secretsmbclient //bigserver/tmp -Ujohndoe%secret

    Once you enter the password you should get the "smb>" prompt. If you +>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.

    smb.conf.

    If it says "bad password" then the likely causes are:

  • you have shadow passords (or some other password system) but didn't - compile in support for them in smbd + compile in support for them in smbd

  • 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

  • etc. Type help >command<help command for instructions. You should especially check that the amount of free disk space shown is correct when you type

  • On the PC type the command net view \\BIGSERVEROn 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 available shares on the server.

  • fixup the nmbd installation

    fixup the nmbd installation

  • add the IP address of BIGSERVER to the "wins server" box in the +> add the IP address of BIGSERVER to the wins server box in the advanced tcp/ip setup on the PC.

  • 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 +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)

    Also, do not overlook that fact that when the workstation requests the @@ -430,22 +682,47 @@ name and password.

    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.)

    hosts.allow file for your client (or subnet, etc.)

  • Run the command net use x: \\BIGSERVER\TMPRun 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 -installed or your smb.conf is incorrect. make sure your "hosts allow" -and other config lines in smb.conf are correct.

    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 smb.conf where "USERNAME" is the +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.

    in smb.conf. +> Turn it back on to fix.

  • Run the command nmblookup -M TESTGROUPRun the command nmblookup -M testgroup where -TESTGROUP is the name of the workgroup that your Samba server and +testgroup is the name of the workgroup that your Samba server and Windows PCs belong to. You should get back the IP address of the 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 +that then look at the browsing options you have set in smb.conf. Make sure you have preferred master = yespassword server = Windows_NT_Machine in your -smb.conf file, or enable encrypted passwords AFTER compiling in support -for encrypted passwords (refer to the Makefile).

    smb.conf file, or make sure encrypted passwords is +set to "yes".

    • 32.4. Still having troubles?33.4. Still having troubles?

    Try the mailing list or newsgroup, or use the ethereal utility to @@ -524,8 +816,6 @@ HREF="http://samba.org/samba" TARGET="_top" >http://samba.org/samba/

    Also look at the other docs in the Samba package!