docs/htmldocs/diagnosis.html

   1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 33. The Samba Checklist</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="previous" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="next" href="problems.html" title="Chapter 34. 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 33. 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 33. 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><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></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><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></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><tt class="email">&lt;<a href="mailto:dan@samba.org">dan@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">Wed Jan 15</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="diagnosis.html#id2969273">Introduction</a></dt><dt><a href="diagnosis.html#id2969311">Assumptions</a></dt><dt><a href="diagnosis.html#id2969546">The Tests</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2969273"></a>Introduction</h2></div></div><div></div></div><p>
   2 This file contains a list of tests you can perform to validate your
   3 Samba server. It also tells you what the likely cause of the problem
   4 is if it fails any one of these steps. If it passes all these tests,
   5 then it is probably working fine.
   6 </p><p>
   7 You should do all the tests, in the order shown. We have tried to
   8 carefully choose them so later tests only use capabilities verified in
   9 the earlier tests. However, do not stop at the first error as there
  10 have been some instances when continuing with the tests has helped
  11 to solve a problem.
  12 </p><p>
  13 If you send one of the Samba mailing lists  an email saying, &#8220;<span class="quote">it does not work</span>&#8221;
  14 and you have not followed this test procedure, you should not be surprised
  15 if your email is ignored.
  16 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2969311"></a>Assumptions</h2></div></div><div></div></div><p>
  17 In all of the tests, it is assumed you have a Samba server called
  18 BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.
  19 </p><p>
  20 The procedure is similar for other types of clients.
  21 </p><p>
  22 It is also assumed you know the name of an available share in your
  23 <tt class="filename">smb.conf</tt>. I will assume this share is called <i class="parameter"><tt>tmp</tt></i>.
  24 You can add a <i class="parameter"><tt>tmp</tt></i> share like this by adding the
  25 lines shown in <link linkend="tmpshare">.
  26 </p><div class="example"><a name="tmpshare"></a><p class="title"><b>Example 33.1. smb.conf with [tmp] share</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[tmp]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = temporary files </tt></i></td></tr><tr><td><i class="parameter"><tt>path = /tmp</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = yes</tt></i></td></tr></table></div><p>
  27 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
  28 These tests assume version 3.0.0 or later of the Samba suite.
  29 Some commands shown did not exist in earlier versions.
  30 </p></div><p>
  31 Please pay attention to the error messages you receive. If any error message
  32 reports that your server is being unfriendly, you should first check that your
  33 IP name resolution is correctly set up. Make sure your <tt class="filename">/etc/resolv.conf</tt>
  34 file points to name servers that really do exist.
  35 </p><p>
  36 Also, if you do not have DNS server access for name resolution, please check
  37 that the settings for your <tt class="filename">smb.conf</tt> file results in <b class="command">dns proxy = no</b>. The
  38 best way to check this is with <b class="command">testparm smb.conf</b>.
  39 </p><p>
  40 <a class="indexterm" name="id2969474"></a>
  41 It is helpful to monitor the log files during testing by using the
  42 <b class="command">tail -F log_file_name</b> in a separate
  43 terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X).
  44 Relevant log files can be found (for default installations) in
  45 <tt class="filename">/usr/local/samba/var</tt>. Also, connection logs from
  46 machines can be found here or possibly in <tt class="filename">/var/log/samba</tt>,
  47 depending on how or if you specified logging in your <tt class="filename">smb.conf</tt> file.
  48 </p><p>
  49 If you make changes to your <tt class="filename">smb.conf</tt> file while going through these test,
  50 remember to restart <span class="application">smbd</span> and <span class="application">nmbd</span>.
  51 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2969546"></a>The Tests</h2></div></div><div></div></div><div class="procedure"><p class="title"><b>Procedure 33.1. Diagnosing your Samba server</b></p><ol type="1"><li><p>
  52 <a class="indexterm" name="id2969570"></a>
  53 In the directory in which you store your <tt class="filename">smb.conf</tt> file, run the command
  54 <b class="command">testparm smb.conf</b>. If it reports any errors, then your <tt class="filename">smb.conf</tt>
  55 configuration file is faulty.
  56 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
  57 Your <tt class="filename">smb.conf</tt> file may be located in: <tt class="filename">/etc/samba</tt>
  58 or in <tt class="filename">/usr/local/samba/lib</tt>.
  59 </p></div></li><li><p>
  60 Run the command <b class="command">ping BIGSERVER</b> from the PC and
  61 <b class="command">ping ACLIENT</b> from the UNIX box. If you do not get a valid response,
  62 then your TCP/IP software is not correctly installed.
  63 </p><p>
  64 You will need to start a &#8220;<span class="quote">dos prompt</span>&#8221; window on the PC to run ping.
  65 </p><p>
  66 If you get a message saying &#8220;<span class="quote"><span class="errorname">host not found</span></span>&#8221; or similar, then your DNS
  67 software or <tt class="filename">/etc/hosts</tt> file is not correctly setup.
  68 It is possible to run Samba without DNS entries for the server and client, but it is assumed
  69 you do have correct entries for the remainder of these tests.
  70 </p><p>
  71 Another reason why ping might fail is if your host is running firewall
  72 software. You will need to relax the rules to let in the workstation
  73 in question, perhaps by allowing access from another subnet (on Linux
  74 this is done via the appropriate firewall maintenance commands <b class="command">ipchains</b>
  75 or <b class="command">iptables</b>).
  76 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
  77 Modern Linux distributions install ipchains/iptables by default.
  78 This is a common problem that is often overlooked.
  79 </p></div><p>
  80 If you wish to check what firewall rules may be present in a system under test, simply run
  81 <b class="command">iptables -L -v</b> or if <i class="parameter"><tt>ipchains</tt></i>-based firewall rules are in use,
  82 <b class="command">ipchains -L -v</b>.
  83 </p><p>
  84 Here is a sample listing from a system that has an external ethernet interface (eth1) on which Samba
  85 is not active, and an internal (private network) interface (eth0) on which Samba is active:
  86 </p><pre class="screen">
  87 frodo:~ # iptables -L -v
  88 Chain INPUT (policy DROP 98496 packets, 12M bytes)
  89  pkts bytes target     prot opt in     out     source     destination
  90  187K  109M ACCEPT     all  --  lo     any     anywhere   anywhere
  91  892K  125M ACCEPT     all  --  eth0   any     anywhere   anywhere
  92 1399K 1380M ACCEPT     all  --  eth1   any     anywhere   anywhere  \
  93                                         state RELATED,ESTABLISHED
  94
  95 Chain FORWARD (policy DROP 0 packets, 0 bytes)
  96  pkts bytes target     prot opt in     out     source     destination
  97  978K 1177M ACCEPT     all  --  eth1   eth0    anywhere   anywhere \
  98                                         state RELATED,ESTABLISHED
  99  658K   40M ACCEPT     all  --  eth0   eth1    anywhere   anywhere
 100     0     0 LOG        all  --  any    any     anywhere   anywhere \
 101                                         LOG level warning
 102
 103 Chain OUTPUT (policy ACCEPT 2875K packets, 1508M bytes)
 104  pkts bytes target     prot opt in     out     source     destination
 105
 106 Chain reject_func (0 references)
 107  pkts bytes target     prot opt in     out     source     destinat
 108 </pre><p>
 109 </p></li><li><p>
 110 Run the command: <b class="command">smbclient -L BIGSERVER</b>
 111 on the UNIX box. You should get back a list of available shares.
 112 </p><p>
 113 If you get an error message containing the string &#8220;<span class="quote">Bad password</span>&#8221;, then
 114 you probably have either an incorrect <i class="parameter"><tt>hosts allow</tt></i>,
 115 <i class="parameter"><tt>hosts deny</tt></i> or <i class="parameter"><tt>valid users</tt></i> line in your
 116 <tt class="filename">smb.conf</tt>, or your guest account is not valid. Check what your guest account is using <span class="application">testparm</span> and
 117 temporarily remove any <i class="parameter"><tt>hosts allow</tt></i>, <i class="parameter"><tt>hosts deny</tt></i>,
 118 <i class="parameter"><tt>valid users</tt></i> or <i class="parameter"><tt>invalid users</tt></i> lines.
 119 </p><p>
 120 If you get a message &#8220;<span class="quote"><span class="errorname">connection refused</span></span>&#8221; response, then the <b class="command">smbd</b> server may
 121 not be running. If you installed it in <tt class="filename">inetd.conf</tt>, then you probably edited
 122 that file incorrectly. If you installed it as a daemon, then check that
 123 it is running, and check that the netbios-ssn port is in a LISTEN
 124 state using <b class="command">netstat -a</b>.
 125 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 126 <a class="indexterm" name="id2969931"></a>
 127 <a class="indexterm" name="id2969939"></a>
 128 Some UNIX/Linux systems use <b class="command">xinetd</b> in place of
 129 <b class="command">inetd</b>. Check your system documentation for the location
 130 of the control files for your particular system implementation of
 131 the network super daemon.
 132 </p></div><p>
 133 If you get a message saying &#8220;<span class="quote"><span class="errorname">session request failed</span></span>&#8221;, the server refused the
 134 connection. If it says &#8220;<span class="quote">Your server software is being unfriendly</span>&#8221;, then
 135 it's probably because you have invalid command line parameters to <span class="application">smbd</span>,
 136 or a similar fatal problem with the initial startup of <span class="application">smbd</span>. Also
 137 check your config file (<tt class="filename">smb.conf</tt>) for syntax errors with <span class="application">testparm</span>
 138 and that the various directories where Samba keeps its log and lock
 139 files exist.
 140 </p><p>
 141 There are a number of reasons for which smbd may refuse or decline
 142 a session request. The most common of these involve one or more of
 143 the <tt class="filename">smb.conf</tt> file entries as shown in <link linkend="modif1">.
 144 </p><p>
 145 </p><div class="example"><a name="modif1"></a><p class="title"><b>Example 33.2. Configuration for only allowing connections from a certain subnet</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[globals]</tt></i></td></tr><tr><td>...</td></tr><tr><td><i class="parameter"><tt>hosts deny = ALL</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts allow = xxx.xxx.xxx.xxx/yy</tt></i></td></tr><tr><td><i class="parameter"><tt>interfaces = eth0</tt></i></td></tr><tr><td><i class="parameter"><tt>bind interfaces only = Yes</tt></i></td></tr><tr><td>...</td></tr></table></div><p>
 146 </p><p>
 147 In the above, no allowance has been made for any session requests that
 148 will automatically translate to the loopback adapter address 127.0.0.1.
 149 To solve this problem, change these lines as shown in <link linkend="modif2">.
 150 </p><p>
 151 </p><div class="example"><a name="modif2"></a><p class="title"><b>Example 33.3. Configuration for allowing connections from a certain subnet and localhost</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[globals]</tt></i></td></tr><tr><td>...</td></tr><tr><td><i class="parameter"><tt>hosts deny = ALL</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts allow = xxx.xxx.xxx.xxx/yy 127.</tt></i></td></tr><tr><td><i class="parameter"><tt>interfaces = eth0 lo</tt></i></td></tr><tr><td>...</td></tr></table></div><p>
 152 </p><p>
 153 <a class="indexterm" name="id2970193"></a>
 154 Another common cause of these two errors is having something already running
 155 <a class="indexterm" name="id2970203"></a>
 156 on port <tt class="constant">139</tt>, such as Samba (<span class="application">smbd</span> is running from <span class="application">inetd</span> already) or
 157 something like Digital's Pathworks. Check your <tt class="filename">inetd.conf</tt> file before trying
 158 to start <span class="application">smbd</span> as a daemon  it can avoid a lot of frustration!
 159 </p><p>
 160 And yet another possible cause for failure of this test is when the subnet mask
 161 and/or broadcast address settings are incorrect. Please check that the
 162 network interface IP Address/Broadcast Address/Subnet Mask settings are
 163 correct and that Samba has correctly noted these in the <tt class="filename">log.nmbd</tt> file.
 164 </p></li><li><p>
 165 Run the command: <b class="command">nmblookup -B BIGSERVER __SAMBA__</b>.
 166 You should get back the IP address of your Samba server.
 167 </p><p>
 168 If you do not, then nmbd is incorrectly installed. Check your <tt class="filename">inetd.conf</tt>
 169 if you run it from there, or that the daemon is running and listening to udp port 137.
 170 </p><p>
 171 One common problem is that many inetd implementations can't take many
 172 parameters on the command line. If this is the case, then create a
 173 one-line script that contains the right parameters and run that from
 174 inetd.
 175 </p></li><li><p>
 176 Run the command: <b class="command">nmblookup -B ACLIENT `*'</b>
 177 </p><p>
 178 You should get the PC's IP address back. If you do not then the client
 179 software on the PC isn't installed correctly, or isn't started, or you
 180 got the name of the PC wrong.
 181 </p><p>
 182 If ACLIENT does not resolve via DNS then use the IP address of the
 183 client in the above test.
 184 </p></li><li><p>
 185 Run the command: <b class="command">nmblookup -d 2 '*'</b>
 186 </p><p>
 187 This time we are trying the same as the previous test but are trying
 188 it via a broadcast to the default broadcast address. A number of
 189 NetBIOS/TCP/IP hosts on the network should respond, although Samba may
 190 not catch all of the responses in the short time it listens. You
 191 should see the &#8220;<span class="quote"><span class="errorname">got a positive name query response</span></span>&#8221;
 192 messages from several hosts.
 193 </p><p>
 194 If this does not give a similar result to the previous test, then
 195 nmblookup isn't correctly getting your broadcast address through its
 196 automatic mechanism. In this case you should experiment with the
 197 <a class="indexterm" name="id2970377"></a><i class="parameter"><tt>interfaces</tt></i> option in <tt class="filename">smb.conf</tt> to manually configure your IP
 198 address, broadcast and netmask.
 199 </p><p>
 200 If your PC and server aren't on the same subnet, then you will need to use the
 201 <tt class="option">-B</tt> option to set the broadcast address to that of the PCs subnet.
 202 </p><p>
 203 This test will probably fail if your subnet mask and broadcast address are
 204 not correct. (Refer to TEST 3 notes above).
 205 </p></li><li><p>
 206 <a class="indexterm" name="id2970428"></a>
 207 Run the command: <b class="command">smbclient //BIGSERVER/TMP</b>. You should
 208 then be prompted for a password. You should use the password of the account
 209 with which you are logged into the UNIX box. If you want to test with
 210 another account, then add the <tt class="option">-U accountname</tt> option to the end of
 211 the command line. For example, <b class="command">smbclient //bigserver/tmp -Ujohndoe</b>.
 212 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 213 It is possible to specify the password along with the username as follows:
 214 <b class="command">smbclient //bigserver/tmp -Ujohndoe%secret</b>.
 215 </p></div><p>
 216 Once you enter the password, you should get the <tt class="prompt">smb&gt;</tt> prompt. If you
 217 do not, then look at the error message. If it says &#8220;<span class="quote"><span class="errorname">invalid network
 218 name</span></span>&#8221;, then the service <i class="parameter"><tt>tmp</tt></i> is not correctly setup in your <tt class="filename">smb.conf</tt>.
 219 </p><p>
 220 If it says &#8220;<span class="quote"><span class="errorname">bad password</span></span>&#8221;, then the likely causes are:
 221 </p><div class="orderedlist"><ol type="1"><li><p>
 222         You have shadow passwords (or some other password system) but didn't
 223         compile in support for them in <span class="application">smbd</span>.
 224         </p></li><li><p>
 225         Your <a class="indexterm" name="id2970549"></a><i class="parameter"><tt>valid users</tt></i> configuration is incorrect.
 226         </p></li><li><p>
 227         You have a mixed case password and you haven't enabled the <a class="indexterm" name="id2970572"></a><i class="parameter"><tt>password level</tt></i> option at a high enough level.
 228         </p></li><li><p>
 229         The <a class="indexterm" name="id2970595"></a><i class="parameter"><tt>path</tt></i> line in <tt class="filename">smb.conf</tt> is incorrect. Check it with <span class="application">testparm</span>.
 230         </p></li><li><p>
 231         You enabled password encryption but didn't map UNIX to Samba users. Run:
 232         <b class="command">smbpasswd -a username</b>
 233         </p></li></ol></div><p>
 234 Once connected, you should be able to use the commands <b class="command">dir</b>, <b class="command">get</b>,
 235 <b class="command">put</b> and so on. Type <b class="command">help command</b> for instructions. You should
 236 especially check that the amount of free disk space shown is correct when you type <b class="command">dir</b>.
 237 </p></li><li><p>
 238 On the PC, type the command <b class="command">net view \\BIGSERVER</b>. You will
 239 need to do this from within a dos prompt window. You should get back a
 240 list of shares available on the server.
 241 </p><p>
 242 If you get a message &#8220;<span class="quote"><span class="errorname">network name not found</span></span>&#8221; or similar error, then netbios
 243 name resolution is not working. This is usually caused by a problem in <b class="command">nmbd</b>.
 244 To overcome it, you could do one of the following (you only need to choose one of them):
 245 </p><div class="orderedlist"><ol type="1"><li><p>
 246         Fixup the <span class="application">nmbd</span> installation.
 247 </p></li><li><p>
 248         Add the IP address of BIGSERVER to the <b class="command">wins server</b> box in the
 249         advanced TCP/IP setup on the PC.
 250 </p></li><li><p>
 251         Enable Windows name resolution via DNS in the advanced section of the TCP/IP setup.
 252 </p></li><li><p>
 253         Add BIGSERVER to your lmhosts file on the PC.
 254 </p></li></ol></div><p>
 255 If you get a message &#8220;<span class="quote"><span class="errorname">invalid network name</span></span>&#8221; or
 256 &#8220;<span class="quote"><span class="errorname">bad password error</span></span>&#8221;, then apply the
 257 same fixes as for the <b class="command">smbclient -L</b> test above. In
 258 particular, make sure your <b class="command">hosts allow</b> line is correct (see the man pages).
 259 </p><p>
 260 Also, do not overlook that fact that when the workstation requests the
 261 connection to the Samba server, it will attempt to connect using the
 262 name with which you logged onto your Windows machine. You need to make
 263 sure that an account exists on your Samba server with that exact same
 264 name and password.
 265 </p><p>
 266 If you get a message &#8220;<span class="quote"><span class="errorname">specified computer is not receiving requests</span></span>&#8221; or similar,
 267 it probably means that the host is not contactable via TCP services.
 268 Check to see if the host is running TCP wrappers, and if so add an entry in
 269 the <tt class="filename">hosts.allow</tt> file for your client (or subnet, and so on.)
 270 </p></li><li><p>
 271 Run the command <b class="command">net use x: \\BIGSERVER\TMP</b>. You should
 272 be prompted for a password, then you should get a <tt class="computeroutput">command completed
 273 successfully</tt> message. If not, then your PC software is incorrectly
 274 installed or your <tt class="filename">smb.conf</tt> is incorrect. Make sure your <i class="parameter"><tt>hosts allow</tt></i>
 275 and other config lines in <tt class="filename">smb.conf</tt> are correct.
 276 </p><p>
 277 It's also possible that the server can't work out what user name to connect you as.
 278 To see if this is the problem, add the line
 279 <a class="indexterm" name="id2970891"></a><i class="parameter"><tt>user</tt></i> = username to the
 280 <i class="parameter"><tt>[tmp]</tt></i> section of
 281 <tt class="filename">smb.conf</tt> where <i class="parameter"><tt>username</tt></i> is the
 282 username corresponding to the password you typed. If you find this
 283 fixes things, you may need the username mapping option.
 284 </p><p>
 285 It might also be the case that your client only sends encrypted passwords
 286 and you have <a class="indexterm" name="id2970934"></a><i class="parameter"><tt>encrypt passwords</tt></i> = no in <tt class="filename">smb.conf</tt>.
 287 Change this to "yes" to fix this.
 288 </p></li><li><p>
 289 Run the command <b class="command">nmblookup -M <i class="parameter"><tt>testgroup</tt></i></b> where
 290 <i class="parameter"><tt>testgroup</tt></i> is the name of the workgroup that your Samba server and
 291 Windows PCs belong to. You should get back the IP address of the
 292 master browser for that workgroup.
 293 </p><p>
 294 If you do not, then the election process has failed. Wait a minute to
 295 see if it is just being slow, then try again. If it still fails after
 296 that, then look at the browsing options you have set in <tt class="filename">smb.conf</tt>. Make
 297 sure you have <a class="indexterm" name="id2971004"></a><i class="parameter"><tt>preferred master</tt></i> = yes to ensure that
 298 an election is held at startup.
 299 </p></li><li><p>
 300 &gt;From file manager, try to browse the server. Your Samba server should
 301 appear in the browse list of your local workgroup (or the one you
 302 specified in <tt class="filename">smb.conf</tt>). You should be able to double click on the name
 303 of the server and get a list of shares. If you get the error message &#8220;<span class="quote">invalid password</span>&#8221;,
 304  you are probably running Windows NT and it
 305 is refusing to browse a server that has no encrypted password
 306 capability and is in User Level Security mode. In this case, either set
 307 <a class="indexterm" name="id2971052"></a><i class="parameter"><tt>security</tt></i> = server and
 308 <a class="indexterm" name="id2971066"></a><i class="parameter"><tt>password server</tt></i> = Windows_NT_Machine in your
 309 <tt class="filename">smb.conf</tt> file, or make sure <a class="indexterm" name="id2971087"></a><i class="parameter"><tt>encrypt passwords</tt></i> is
 310 set to &#8220;<span class="quote">yes</span>&#8221;.
 311 </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 34. Analyzing and Solving Samba Problems</td></tr></table></div></body></html>