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