Ignore:
Timestamp:
May 23, 2008, 6:56:41 AM (17 years ago)
Author:
Paul Smedley
Message:

Update source to 3.0.29

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/samba-3.0/docs/htmldocs/Samba3-HOWTO/diagnosis.html

    r44 r134  
    1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 38. The Samba Checklist</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="prev" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="next" href="problems.html" title="Chapter 39. Analyzing and Solving Samba Problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 38. The Samba Checklist</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a> </td><th width="60%" align="center">Part V. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="problems.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="diagnosis"></a>Chapter 38. The Samba Checklist</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a href="mailto:dan@samba.org">dan@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">Wed Jan 15</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="diagnosis.html#id438262">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id438295">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id438577">The Tests</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id438262"></a>Introduction</h2></div></div></div><p>
    2 <a class="indexterm" name="id438270"></a>
     1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 38. The Samba Checklist</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="prev" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="next" href="problems.html" title="Chapter 39. Analyzing and Solving Samba Problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 38. The Samba Checklist</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a> </td><th width="60%" align="center">Part V. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="problems.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="diagnosis"></a>Chapter 38. The Samba Checklist</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">Wed Jan 15</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="diagnosis.html#id462256">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id462289">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id462567">The Tests</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id462256"></a>Introduction</h2></div></div></div><p>
     2<a class="indexterm" name="id462264"></a>
    33This file contains a list of tests you can perform to validate your
    44Samba server. It also tells you what the likely cause of the problem
     
    1515and you have not followed this test procedure, you should not be surprised
    1616if your email is ignored.
    17 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id438295"></a>Assumptions</h2></div></div></div><p>
     17</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id462289"></a>Assumptions</h2></div></div></div><p>
    1818In all of the tests, it is assumed you have a Samba server called
    1919BIGSERVER and a PC called ACLIENT, both in workgroup TESTGROUP.
     
    2424<code class="filename">smb.conf</code>. I for our examples this share is called <em class="parameter"><code>tmp</code></em>.
    2525You can add a <em class="parameter"><code>tmp</code></em> share like this by adding the
    26 lines shown in <a href="diagnosis.html#tmpshare" title="Example 38.1. smb.conf with [tmp] Share">the next example</a>.
    27 </p><div class="example"><a name="tmpshare"></a><p class="title"><b>Example 38.1. smb.conf with [tmp] Share</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[tmp]</code></em></td></tr><tr><td><a class="indexterm" name="id438363"></a><em class="parameter"><code>comment = temporary files </code></em></td></tr><tr><td><a class="indexterm" name="id438376"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td><a class="indexterm" name="id438388"></a><em class="parameter"><code>read only = yes</code></em></td></tr></table></div></div><br class="example-break"><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
     26lines shown in <a class="link" href="diagnosis.html#tmpshare" title="Example 38.1. smb.conf with [tmp] Share">the next example</a>.
     27</p><div class="example"><a name="tmpshare"></a><p class="title"><b>Example 38.1. smb.conf with [tmp] Share</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[tmp]</code></em></td></tr><tr><td><a class="indexterm" name="id462356"></a><em class="parameter"><code>comment = temporary files </code></em></td></tr><tr><td><a class="indexterm" name="id462368"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td><a class="indexterm" name="id462379"></a><em class="parameter"><code>read only = yes</code></em></td></tr></table></div></div><br class="example-break"><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    2828These tests assume version 3.0.0 or later of the Samba suite.
    2929Some commands shown did not exist in earlier versions.
    3030</p></div><p>
    31 <a class="indexterm" name="id438409"></a>
    32 <a class="indexterm" name="id438416"></a>
    33 <a class="indexterm" name="id438423"></a>
     31<a class="indexterm" name="id462399"></a>
     32<a class="indexterm" name="id462406"></a>
     33<a class="indexterm" name="id462413"></a>
    3434Please pay attention to the error messages you receive. If any error message
    3535reports that your server is being unfriendly, you should first check that your
     
    3737file points to name servers that really do exist.
    3838</p><p>
    39 <a class="indexterm" name="id438441"></a>
    40 <a class="indexterm" name="id438448"></a>
    41 <a class="indexterm" name="id438454"></a>
    42 <a class="indexterm" name="id438461"></a>
     39<a class="indexterm" name="id462431"></a>
     40<a class="indexterm" name="id462438"></a>
     41<a class="indexterm" name="id462445"></a>
     42<a class="indexterm" name="id462452"></a>
    4343Also, if you do not have DNS server access for name resolution, please check
    4444that the settings for your <code class="filename">smb.conf</code> file results in <em class="parameter"><code>dns proxy = no</code></em>. The
    4545best way to check this is with <code class="literal">testparm smb.conf</code>.
    4646</p><p>
    47 <a class="indexterm" name="id438490"></a>
    48 <a class="indexterm" name="id438497"></a>
    49 <a class="indexterm" name="id438504"></a>
    50 <a class="indexterm" name="id438511"></a>
    51 <a class="indexterm" name="id438517"></a>
     47<a class="indexterm" name="id462480"></a>
     48<a class="indexterm" name="id462487"></a>
     49<a class="indexterm" name="id462494"></a>
     50<a class="indexterm" name="id462501"></a>
     51<a class="indexterm" name="id462508"></a>
    5252It is helpful to monitor the log files during testing by using the
    5353<code class="literal">tail -F log_file_name</code> in a separate
     
    6060If you make changes to your <code class="filename">smb.conf</code> file while going through these test,
    6161remember to restart <span class="application">smbd</span> and <span class="application">nmbd</span>.
    62 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id438577"></a>The Tests</h2></div></div></div><div class="procedure"><a name="id438583"></a><p class="title"><b>Procedure 38.1. Diagnosing Your Samba Server</b></p><ol type="1"><li><p>
    63 <a class="indexterm" name="id438595"></a>
     62</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id462567"></a>The Tests</h2></div></div></div><div class="procedure"><a name="id462573"></a><p class="title"><b>Procedure 38.1. Diagnosing Your Samba Server</b></p><ol type="1"><li><p>
     63<a class="indexterm" name="id462585"></a>
    6464In the directory in which you store your <code class="filename">smb.conf</code> file, run the command
    6565<code class="literal">testparm smb.conf</code>. If it reports any errors, then your <code class="filename">smb.conf</code>
    6666configuration file is faulty.
    6767</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    68 <a class="indexterm" name="id438625"></a>
    69 <a class="indexterm" name="id438632"></a>
     68<a class="indexterm" name="id462615"></a>
     69<a class="indexterm" name="id462622"></a>
    7070Your <code class="filename">smb.conf</code> file may be located in <code class="filename">/etc/samba</code>
    7171or in <code class="filename">/usr/local/samba/lib</code>.
    7272</p></div></li><li><p>
    73 <a class="indexterm" name="id438665"></a>
     73<a class="indexterm" name="id462655"></a>
    7474Run the command <code class="literal">ping BIGSERVER</code> from the PC and
    7575<code class="literal">ping ACLIENT</code> from the UNIX box. If you do not get a valid response,
     
    7878You will need to start a &#8220;<span class="quote">DOS prompt</span>&#8221; window on the PC to run ping.
    7979</p><p>
    80 <a class="indexterm" name="id438696"></a>
    81 <a class="indexterm" name="id438702"></a>
    82 <a class="indexterm" name="id438709"></a>
     80<a class="indexterm" name="id462686"></a>
     81<a class="indexterm" name="id462693"></a>
     82<a class="indexterm" name="id462699"></a>
    8383If you get a message saying &#8220;<span class="quote"><span class="errorname">host not found</span></span>&#8221; or a similar message, then
    8484your DNS software or <code class="filename">/etc/hosts</code> file is not correctly set up.  If using DNS, check that
     
    8787remainder of these tests.
    8888</p><p>
    89 <a class="indexterm" name="id438738"></a>
    90 <a class="indexterm" name="id438745"></a>
    91 <a class="indexterm" name="id438752"></a>
     89<a class="indexterm" name="id462729"></a>
     90<a class="indexterm" name="id462735"></a>
     91<a class="indexterm" name="id462742"></a>
    9292Another reason why ping might fail is if your host is running firewall
    9393software. You will need to relax the rules to let in the workstation
     
    9999This is a common problem that is often overlooked.
    100100</p></div><p>
    101 <a class="indexterm" name="id438784"></a>
    102 <a class="indexterm" name="id438790"></a>
     101<a class="indexterm" name="id462774"></a>
     102<a class="indexterm" name="id462781"></a>
    103103If you wish to check what firewall rules may be present in a system under test, simply run
    104104<code class="literal">iptables -L -v</code>, or if <em class="parameter"><code>ipchains</code></em>-based firewall rules are in use,
     
    134134on the UNIX box. You should get back a list of available shares.
    135135</p><p>
    136 <a class="indexterm" name="id438862"></a>
    137 <a class="indexterm" name="id438868"></a>
    138 <a class="indexterm" name="id438875"></a>
    139 <a class="indexterm" name="id438882"></a>
    140 <a class="indexterm" name="id438889"></a>
    141 <a class="indexterm" name="id438896"></a>
     136<a class="indexterm" name="id462852"></a>
     137<a class="indexterm" name="id462859"></a>
     138<a class="indexterm" name="id462865"></a>
     139<a class="indexterm" name="id462872"></a>
     140<a class="indexterm" name="id462879"></a>
     141<a class="indexterm" name="id462886"></a>
    142142If you get an error message containing the string &#8220;<span class="quote">bad password</span>&#8221;, then
    143143you probably have either an incorrect <em class="parameter"><code>hosts allow</code></em>,
     
    147147<em class="parameter"><code>valid users</code></em>, or <em class="parameter"><code>invalid users</code></em> lines.
    148148</p><p>
    149 <a class="indexterm" name="id438964"></a>
     149<a class="indexterm" name="id462954"></a>
    150150If you get a message <code class="literal">connection refused</code> response, then the <code class="literal">smbd</code> server may
    151151not be running. If you installed it in <code class="filename">inetd.conf</code>, then you probably edited
     
    154154state using <code class="literal">netstat -a</code>.
    155155</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    156 <a class="indexterm" name="id439001"></a>
    157 <a class="indexterm" name="id439007"></a>
     156<a class="indexterm" name="id462991"></a>
     157<a class="indexterm" name="id462998"></a>
    158158Some UNIX/Linux systems use <code class="literal">xinetd</code> in place of
    159159<code class="literal">inetd</code>. Check your system documentation for the location
     
    171171There are a number of reasons for which smbd may refuse or decline
    172172a session request. The most common of these involve one or more of
    173 the <code class="filename">smb.conf</code> file entries as shown in <a href="diagnosis.html#modif1" title="Example 38.2. Configuration for Allowing Connections Only from a Certain Subnet">the next example</a>.
    174 </p><div class="example"><a name="modif1"></a><p class="title"><b>Example 38.2. Configuration for Allowing Connections Only from a Certain Subnet</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[globals]</code></em></td></tr><tr><td><a class="indexterm" name="id439113"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id439126"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy</code></em></td></tr><tr><td><a class="indexterm" name="id439139"></a><em class="parameter"><code>interfaces = eth0</code></em></td></tr><tr><td><a class="indexterm" name="id439151"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
    175 <a class="indexterm" name="id439167"></a>
    176 In <a href="diagnosis.html#modif1" title="Example 38.2. Configuration for Allowing Connections Only from a Certain Subnet">Configuration for Allowing Connections Only from a Certain Subnet</a>, no
     173the <code class="filename">smb.conf</code> file entries as shown in <a class="link" href="diagnosis.html#modif1" title="Example 38.2. Configuration for Allowing Connections Only from a Certain Subnet">the next example</a>.
     174</p><div class="example"><a name="modif1"></a><p class="title"><b>Example 38.2. Configuration for Allowing Connections Only from a Certain Subnet</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[globals]</code></em></td></tr><tr><td><a class="indexterm" name="id463104"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id463115"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy</code></em></td></tr><tr><td><a class="indexterm" name="id463127"></a><em class="parameter"><code>interfaces = eth0</code></em></td></tr><tr><td><a class="indexterm" name="id463138"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>
     175<a class="indexterm" name="id463153"></a>
     176In <a class="link" href="diagnosis.html#modif1" title="Example 38.2. Configuration for Allowing Connections Only from a Certain Subnet">Configuration for Allowing Connections Only from a Certain Subnet</a>, no
    177177allowance has been made for any session requests that will automatically translate to the loopback adapter
    178 address 127.0.0.1.  To solve this problem, change these lines as shown in <a href="diagnosis.html#modif2" title="Example 38.3. Configuration for Allowing Connections from a Certain Subnet and localhost">the following
     178address 127.0.0.1.  To solve this problem, change these lines as shown in <a class="link" href="diagnosis.html#modif2" title="Example 38.3. Configuration for Allowing Connections from a Certain Subnet and localhost">the following
    179179example</a>.
    180 </p><div class="example"><a name="modif2"></a><p class="title"><b>Example 38.3. Configuration for Allowing Connections from a Certain Subnet and localhost</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[globals]</code></em></td></tr><tr><td><a class="indexterm" name="id439216"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id439228"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy 127.</code></em></td></tr><tr><td><a class="indexterm" name="id439241"></a><em class="parameter"><code>interfaces = eth0 lo</code></em></td></tr></table></div></div><br class="example-break"><p>
    181 <a class="indexterm" name="id439257"></a>
    182 <a class="indexterm" name="id439264"></a>
     180</p><div class="example"><a name="modif2"></a><p class="title"><b>Example 38.3. Configuration for Allowing Connections from a Certain Subnet and localhost</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[globals]</code></em></td></tr><tr><td><a class="indexterm" name="id463202"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id463213"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy 127.</code></em></td></tr><tr><td><a class="indexterm" name="id463225"></a><em class="parameter"><code>interfaces = eth0 lo</code></em></td></tr></table></div></div><br class="example-break"><p>
     181<a class="indexterm" name="id463240"></a>
     182<a class="indexterm" name="id463246"></a>
    183183Another common cause of these two errors is having something already running on port <code class="constant">139</code>,
    184184such as Samba (<span class="application">smbd</span> is running from <span class="application">inetd</span> already) or Digital's Pathworks. Check
     
    186186lot of frustration!
    187187</p><p>
    188 <a class="indexterm" name="id439306"></a>
    189 <a class="indexterm" name="id439312"></a>
    190 <a class="indexterm" name="id439319"></a>
    191 <a class="indexterm" name="id439325"></a>
    192 <a class="indexterm" name="id439332"></a>
     188<a class="indexterm" name="id463288"></a>
     189<a class="indexterm" name="id463295"></a>
     190<a class="indexterm" name="id463301"></a>
     191<a class="indexterm" name="id463308"></a>
     192<a class="indexterm" name="id463315"></a>
    193193And yet another possible cause for failure of this test is when the subnet mask and/or broadcast address
    194194settings are incorrect. Please check that the network interface IP address/broadcast address/subnet mask
    195195settings are correct and that Samba has correctly noted these in the <code class="filename">log.nmbd</code> file.
    196196</p></li><li><p>
    197 <a class="indexterm" name="id439356"></a>
     197<a class="indexterm" name="id463339"></a>
    198198Run the command <code class="literal">nmblookup -B BIGSERVER __SAMBA__</code>.
    199199You should get back the IP address of your Samba server.
    200200</p><p>
    201 <a class="indexterm" name="id439373"></a>
    202 <a class="indexterm" name="id439380"></a>
    203 <a class="indexterm" name="id439387"></a>
     201<a class="indexterm" name="id463356"></a>
     202<a class="indexterm" name="id463363"></a>
     203<a class="indexterm" name="id463369"></a>
    204204If you do not, then <span class="application">nmbd</span> is incorrectly installed. Check your <code class="filename">inetd.conf</code>
    205205if you run it from there, or that the daemon is running and listening to UDP port 137.
     
    210210inetd.
    211211</p></li><li><p>
    212 <a class="indexterm" name="id439420"></a>
     212<a class="indexterm" name="id463403"></a>
    213213Run the command <code class="literal">nmblookup -B ACLIENT `*'</code>.
    214214</p><p>
     
    229229messages from several hosts.
    230230</p><p>
    231 <a class="indexterm" name="id439472"></a>
     231<a class="indexterm" name="id463455"></a>
    232232If this does not give a result similar to the previous test, then nmblookup isn't correctly getting your
    233 broadcast address through its automatic mechanism. In this case you should experiment with the <a class="indexterm" name="id439481"></a>interfaces option in <code class="filename">smb.conf</code> to manually configure your IP address, broadcast, and netmask.
     233broadcast address through its automatic mechanism. In this case you should experiment with the <a class="link" href="smb.conf.5.html#INTERFACES">interfaces</a> option in <code class="filename">smb.conf</code> to manually configure your IP address, broadcast, and netmask.
    234234</p><p>
    235235If your PC and server aren't on the same subnet, then you will need to use the
     
    239239not correct. (Refer to test 3 notes above).
    240240</p></li><li><p>
    241 <a class="indexterm" name="id439515"></a>
     241<a class="indexterm" name="id463501"></a>
    242242Run the command <code class="literal">smbclient //BIGSERVER/TMP</code>. You should
    243243then be prompted for a password. You should use the password of the account
     
    258258        compile in support for them in <span class="application">smbd</span>.
    259259        </p></li><li><p>
    260         Your <a class="indexterm" name="id439613"></a>valid users configuration is incorrect.
     260        Your <a class="link" href="smb.conf.5.html#VALIDUSERS">valid users</a> configuration is incorrect.
    261261        </p></li><li><p>
    262         You have a mixed-case password and you haven't enabled the <a class="indexterm" name="id439628"></a>password level option at a high enough level.
     262        You have a mixed-case password and you haven't enabled the <a class="link" href="smb.conf.5.html#PASSWORDLEVEL">password level</a> option at a high enough level.
    263263        </p></li><li><p>
    264         The <a class="indexterm" name="id439642"></a>path line in <code class="filename">smb.conf</code> is incorrect. Check it with <span class="application">testparm</span>.
     264        The <a class="link" href="smb.conf.5.html#PATH">path</a> line in <code class="filename">smb.conf</code> is incorrect. Check it with <span class="application">testparm</span>.
    265265        </p></li><li><p>
    266266        You enabled password encryption but didn't map UNIX to Samba users. Run
    267267        <code class="literal">smbpasswd -a username</code>
    268268        </p></li></ol></div><p>
    269 <a class="indexterm" name="id439679"></a>
    270 <a class="indexterm" name="id439686"></a>
    271 <a class="indexterm" name="id439692"></a>
    272 <a class="indexterm" name="id439699"></a>
     269<a class="indexterm" name="id463675"></a>
     270<a class="indexterm" name="id463682"></a>
     271<a class="indexterm" name="id463689"></a>
     272<a class="indexterm" name="id463695"></a>
    273273Once connected, you should be able to use the commands <code class="literal">dir</code>, <code class="literal">get</code>,
    274274<code class="literal">put</code>, and so on. Type <code class="literal">help command</code> for instructions. You should
    275275especially check that the amount of free disk space shown is correct when you type <code class="literal">dir</code>.
    276276</p></li><li><p>
    277 <a class="indexterm" name="id439744"></a>
     277<a class="indexterm" name="id463740"></a>
    278278On the PC, type the command <code class="literal">net view \\BIGSERVER</code>. You will
    279279need to do this from within a DOS prompt window. You should get back a
    280280list of shares available on the server.
    281281</p><p>
    282 <a class="indexterm" name="id439761"></a>
     282<a class="indexterm" name="id463758"></a>
    283283If you get a message <code class="literal">network name not found</code> or similar error, then NetBIOS
    284284name resolution is not working. This is usually caused by a problem in <code class="literal">nmbd</code>.
     
    318318It's also possible that the server can't work out what username to connect you as.
    319319To see if this is the problem, add the line
    320 <a class="indexterm" name="id439913"></a>user = username to the
     320<a class="link" href="smb.conf.5.html#USER">user = username</a> to the
    321321<em class="parameter"><code>[tmp]</code></em> section of
    322322<code class="filename">smb.conf</code> where <em class="parameter"><code>username</code></em> is the
     
    325325</p><p>
    326326It might also be the case that your client only sends encrypted passwords
    327 and you have <a class="indexterm" name="id439943"></a>encrypt passwords = no in <code class="filename">smb.conf</code>.
     327and you have <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS">encrypt passwords = no</a> in <code class="filename">smb.conf</code>.
    328328Change this setting to `yes' to fix this.
    329329</p></li><li><p>
     
    336336see if it is just being slow, then try again. If it still fails after
    337337that, then look at the browsing options you have set in <code class="filename">smb.conf</code>. Make
    338 sure you have <a class="indexterm" name="id439994"></a>preferred master = yes to ensure that
     338sure you have <a class="link" href="smb.conf.5.html#PREFERREDMASTER">preferred master = yes</a> to ensure that
    339339an election is held at startup.
    340340</p></li><li><p>
     
    346346is refusing to browse a server that has no encrypted password
    347347capability and is in user-level security mode. In this case, either set
    348 <a class="indexterm" name="id440024"></a>security = server and
    349 <a class="indexterm" name="id440031"></a>password server = Windows_NT_Machine in your
    350 <code class="filename">smb.conf</code> file or make sure <a class="indexterm" name="id440044"></a>encrypt passwords is
     348<a class="link" href="smb.conf.5.html#SECURITY">security = server</a> and
     349<a class="link" href="smb.conf.5.html#PASSWORDSERVER">password server = Windows_NT_Machine</a> in your
     350<code class="filename">smb.conf</code> file or make sure <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS">encrypt passwords</a> is
    351351set to &#8220;<span class="quote">yes</span>&#8221;.
    352352</p></li></ol></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="problems.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Part V. Troubleshooting </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 39. Analyzing and Solving Samba Problems</td></tr></table></div></body></html>
Note: See TracChangeset for help on using the changeset viewer.