- Timestamp:
- Jan 15, 2010, 8:21:06 AM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.3.x/docs/htmldocs/Samba3-HOWTO/diagnosis.html
r342 r368 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.7 4.0"><link rel="home" href="index.html" title="The Official Samba 3.3.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="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>></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="orgname">The Samba Team</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"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="orgname">Samba Team</span> <span class="surname">Shearer</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>></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#id2682800">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2682839">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2683132">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="id2682800"></a>Introduction</h2></div></div></div><p>2 <a class="indexterm" name="id268 2808"></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.75.2"><link rel="home" href="index.html" title="The Official Samba 3.3.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" title="Chapter 38. The Samba Checklist"><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"><<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>></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"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a class="email" href="mailto:dan@samba.org">dan@samba.org</a>></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#id2688857">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2688896">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2689189">The Tests</a></span></dt></dl></div><div class="sect1" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2688857"></a>Introduction</h2></div></div></div><p> 2 <a class="indexterm" name="id2688865"></a> 3 3 This file contains a list of tests you can perform to validate your 4 4 Samba server. It also tells you what the likely cause of the problem … … 12 12 to solve a problem. 13 13 </p><p> 14 If you send one of the Samba mailing lists an email saying, “<span class="quote">It does not work,</span>”14 If you send one of the Samba mailing lists an email saying, <span class="quote">“<span class="quote">It does not work,</span>”</span> 15 15 and you have not followed this test procedure, you should not be surprised 16 16 if 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="id2682839"></a>Assumptions</h2></div></div></div><p>17 </p></div><div class="sect1" title="Assumptions"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2688896"></a>Assumptions</h2></div></div></div><p> 18 18 In all of the tests, it is assumed you have a Samba server called 19 19 BIGSERVER and a PC called ACLIENT, both in workgroup TESTGROUP. … … 25 25 You can add a <em class="parameter"><code>tmp</code></em> share like this by adding the 26 26 lines 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="id2682910"></a><em class="parameter"><code>comment = temporary files </code></em></td></tr><tr><td><a class="indexterm" name="id2682922"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td><a class="indexterm" name="id2682933"></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>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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[tmp]</code></em></td></tr><tr><td><a class="indexterm" name="id2688967"></a><em class="parameter"><code>comment = temporary files </code></em></td></tr><tr><td><a class="indexterm" name="id2688979"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td><a class="indexterm" name="id2688990"></a><em class="parameter"><code>read only = yes</code></em></td></tr></table></div></div><br class="example-break"><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 28 28 These tests assume version 3.0.0 or later of the Samba suite. 29 29 Some commands shown did not exist in earlier versions. 30 30 </p></div><p> 31 <a class="indexterm" name="id268 2955"></a>32 <a class="indexterm" name="id268 2962"></a>33 <a class="indexterm" name="id268 2968"></a>31 <a class="indexterm" name="id2689011"></a> 32 <a class="indexterm" name="id2689018"></a> 33 <a class="indexterm" name="id2689025"></a> 34 34 Please pay attention to the error messages you receive. If any error message 35 35 reports that your server is being unfriendly, you should first check that your … … 37 37 file points to name servers that really do exist. 38 38 </p><p> 39 <a class="indexterm" name="id268 2989"></a>40 <a class="indexterm" name="id268 2996"></a>41 <a class="indexterm" name="id268 3003"></a>42 <a class="indexterm" name="id268 3010"></a>39 <a class="indexterm" name="id2689046"></a> 40 <a class="indexterm" name="id2689053"></a> 41 <a class="indexterm" name="id2689060"></a> 42 <a class="indexterm" name="id2689066"></a> 43 43 Also, if you do not have DNS server access for name resolution, please check 44 44 that the settings for your <code class="filename">smb.conf</code> file results in <em class="parameter"><code>dns proxy = no</code></em>. The 45 45 best way to check this is with <code class="literal">testparm smb.conf</code>. 46 46 </p><p> 47 <a class="indexterm" name="id268 3040"></a>48 <a class="indexterm" name="id268 3047"></a>49 <a class="indexterm" name="id268 3054"></a>50 <a class="indexterm" name="id268 3061"></a>51 <a class="indexterm" name="id268 3068"></a>47 <a class="indexterm" name="id2689097"></a> 48 <a class="indexterm" name="id2689104"></a> 49 <a class="indexterm" name="id2689111"></a> 50 <a class="indexterm" name="id2689118"></a> 51 <a class="indexterm" name="id2689125"></a> 52 52 It is helpful to monitor the log files during testing by using the 53 53 <code class="literal">tail -F log_file_name</code> in a separate … … 60 60 If you make changes to your <code class="filename">smb.conf</code> file while going through these test, 61 61 remember 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="id2683132"></a>The Tests</h2></div></div></div><div class="procedure"><a name="id2683138"></a><p class="title"><b>Procedure 38.1. Diagnosing Your Samba Server</b></p><ol type="1"><li><p>63 <a class="indexterm" name="id268 3150"></a>62 </p></div><div class="sect1" title="The Tests"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2689189"></a>The Tests</h2></div></div></div><div class="procedure" title="Procedure 38.1. Diagnosing Your Samba Server"><a name="id2689194"></a><p class="title"><b>Procedure 38.1. Diagnosing Your Samba Server</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> 63 <a class="indexterm" name="id2689207"></a> 64 64 In the directory in which you store your <code class="filename">smb.conf</code> file, run the command 65 65 <code class="literal">testparm smb.conf</code>. If it reports any errors, then your <code class="filename">smb.conf</code> 66 66 configuration file is faulty. 67 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>68 <a class="indexterm" name="id268 3181"></a>69 <a class="indexterm" name="id268 3188"></a>67 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 68 <a class="indexterm" name="id2689238"></a> 69 <a class="indexterm" name="id2689245"></a> 70 70 Your <code class="filename">smb.conf</code> file may be located in <code class="filename">/etc/samba</code> 71 71 or in <code class="filename">/usr/local/samba/lib</code>. 72 </p></div></li><li ><p>73 <a class="indexterm" name="id268 3222"></a>72 </p></div></li><li class="step" title="Step 2"><p> 73 <a class="indexterm" name="id2689279"></a> 74 74 Run the command <code class="literal">ping BIGSERVER</code> from the PC and 75 75 <code class="literal">ping ACLIENT</code> from the UNIX box. If you do not get a valid response, 76 76 then your TCP/IP software is not correctly installed. 77 77 </p><p> 78 You will need to start a “<span class="quote">DOS prompt</span>”window on the PC to run ping.79 </p><p> 80 <a class="indexterm" name="id268 3255"></a>81 <a class="indexterm" name="id268 3262"></a>82 <a class="indexterm" name="id268 3268"></a>83 If you get a message saying “<span class="quote"><span class="errorname">host not found</span></span>”or a similar message, then78 You will need to start a <span class="quote">“<span class="quote">DOS prompt</span>”</span> window on the PC to run ping. 79 </p><p> 80 <a class="indexterm" name="id2689311"></a> 81 <a class="indexterm" name="id2689318"></a> 82 <a class="indexterm" name="id2689325"></a> 83 If you get a message saying <span class="quote">“<span class="quote"><span class="errorname">host not found</span></span>”</span> or a similar message, then 84 84 your DNS software or <code class="filename">/etc/hosts</code> file is not correctly set up. If using DNS, check that 85 85 the <code class="filename">/etc/resolv.conf</code> has correct, current, entries in it. It is possible to run … … 87 87 remainder of these tests. 88 88 </p><p> 89 <a class="indexterm" name="id268 3301"></a>90 <a class="indexterm" name="id268 3307"></a>91 <a class="indexterm" name="id268 3314"></a>89 <a class="indexterm" name="id2689357"></a> 90 <a class="indexterm" name="id2689364"></a> 91 <a class="indexterm" name="id2689371"></a> 92 92 Another reason why ping might fail is if your host is running firewall 93 93 software. You will need to relax the rules to let in the workstation … … 95 95 this is done via the appropriate firewall maintenance commands <code class="literal">ipchains</code> 96 96 or <code class="literal">iptables</code>). 97 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>97 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 98 98 Modern Linux distributions install ipchains/iptables by default. 99 99 This is a common problem that is often overlooked. 100 100 </p></div><p> 101 <a class="indexterm" name="id268 3349"></a>102 <a class="indexterm" name="id268 3356"></a>101 <a class="indexterm" name="id2689406"></a> 102 <a class="indexterm" name="id2689413"></a> 103 103 If you wish to check what firewall rules may be present in a system under test, simply run 104 104 <code class="literal">iptables -L -v</code>, or if <em class="parameter"><code>ipchains</code></em>-based firewall rules are in use, … … 130 130 pkts bytes target prot opt in out source destination 131 131 </pre><p> 132 </p></li><li ><p>132 </p></li><li class="step" title="Step 3"><p> 133 133 Run the command <code class="literal">smbclient -L BIGSERVER</code> 134 134 on the UNIX box. You should get back a list of available shares. 135 135 </p><p> 136 <a class="indexterm" name="id268 3431"></a>137 <a class="indexterm" name="id268 3438"></a>138 <a class="indexterm" name="id268 3445"></a>139 <a class="indexterm" name="id268 3452"></a>140 <a class="indexterm" name="id268 3458"></a>141 <a class="indexterm" name="id268 3465"></a>142 If you get an error message containing the string “<span class="quote">bad password</span>”, then136 <a class="indexterm" name="id2689488"></a> 137 <a class="indexterm" name="id2689495"></a> 138 <a class="indexterm" name="id2689502"></a> 139 <a class="indexterm" name="id2689508"></a> 140 <a class="indexterm" name="id2689515"></a> 141 <a class="indexterm" name="id2689522"></a> 142 If you get an error message containing the string <span class="quote">“<span class="quote">bad password</span>”</span>, then 143 143 you probably have either an incorrect <em class="parameter"><code>hosts allow</code></em>, 144 144 <em class="parameter"><code>hosts deny</code></em>, or <em class="parameter"><code>valid users</code></em> line in your … … 147 147 <em class="parameter"><code>valid users</code></em>, or <em class="parameter"><code>invalid users</code></em> lines. 148 148 </p><p> 149 <a class="indexterm" name="id268 3536"></a>149 <a class="indexterm" name="id2689593"></a> 150 150 If you get a message <code class="literal">connection refused</code> response, then the <code class="literal">smbd</code> server may 151 151 not be running. If you installed it in <code class="filename">inetd.conf</code>, then you probably edited … … 153 153 it is running and check that the netbios-ssn port is in a LISTEN 154 154 state using <code class="literal">netstat -a</code>. 155 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>156 <a class="indexterm" name="id268 3575"></a>157 <a class="indexterm" name="id268 3582"></a>155 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 156 <a class="indexterm" name="id2689632"></a> 157 <a class="indexterm" name="id2689639"></a> 158 158 Some UNIX/Linux systems use <code class="literal">xinetd</code> in place of 159 159 <code class="literal">inetd</code>. Check your system documentation for the location … … 162 162 </p></div><p> 163 163 If you get a message saying <code class="literal">session request failed,</code> the server refused the 164 connection. If it says “<span class="quote">Your server software is being unfriendly,</span>”then164 connection. If it says <span class="quote">“<span class="quote">Your server software is being unfriendly,</span>”</span> then 165 165 it's probably because you have invalid command line parameters to <span class="application">smbd</span>, 166 166 or a similar fatal problem with the initial startup of <span class="application">smbd</span>. Also … … 172 172 a session request. The most common of these involve one or more of 173 173 the <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="id2683694"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id2683706"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy</code></em></td></tr><tr><td><a class="indexterm" name="id2683718"></a><em class="parameter"><code>interfaces = eth0</code></em></td></tr><tr><td><a class="indexterm" name="id2683730"></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="id268 3745"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[globals]</code></em></td></tr><tr><td><a class="indexterm" name="id2689751"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id2689763"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy</code></em></td></tr><tr><td><a class="indexterm" name="id2689775"></a><em class="parameter"><code>interfaces = eth0</code></em></td></tr><tr><td><a class="indexterm" name="id2689786"></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="id2689801"></a> 176 176 In <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 177 177 allowance has been made for any session requests that will automatically translate to the loopback adapter 178 178 address 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 179 179 example</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="id2683797"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id2683808"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy 127.</code></em></td></tr><tr><td><a class="indexterm" name="id2683820"></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="id268 3835"></a>182 <a class="indexterm" name="id268 3842"></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 border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[globals]</code></em></td></tr><tr><td><a class="indexterm" name="id2689854"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id2689865"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy 127.</code></em></td></tr><tr><td><a class="indexterm" name="id2689877"></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="id2689892"></a> 182 <a class="indexterm" name="id2689899"></a> 183 183 Another common cause of these two errors is having something already running on port <code class="constant">139</code>, 184 184 such as Samba (<span class="application">smbd</span> is running from <span class="application">inetd</span> already) or Digital's Pathworks. Check … … 186 186 lot of frustration! 187 187 </p><p> 188 <a class="indexterm" name="id268 3887"></a>189 <a class="indexterm" name="id268 3893"></a>190 <a class="indexterm" name="id268 3900"></a>191 <a class="indexterm" name="id268 3907"></a>192 <a class="indexterm" name="id268 3914"></a>188 <a class="indexterm" name="id2689944"></a> 189 <a class="indexterm" name="id2689950"></a> 190 <a class="indexterm" name="id2689957"></a> 191 <a class="indexterm" name="id2689964"></a> 192 <a class="indexterm" name="id2689971"></a> 193 193 And yet another possible cause for failure of this test is when the subnet mask and/or broadcast address 194 194 settings are incorrect. Please check that the network interface IP address/broadcast address/subnet mask 195 195 settings are correct and that Samba has correctly noted these in the <code class="filename">log.nmbd</code> file. 196 </p></li><li ><p>197 <a class="indexterm" name="id268 3940"></a>196 </p></li><li class="step" title="Step 4"><p> 197 <a class="indexterm" name="id2689997"></a> 198 198 Run the command <code class="literal">nmblookup -B BIGSERVER __SAMBA__</code>. 199 199 You should get back the IP address of your Samba server. 200 200 </p><p> 201 <a class="indexterm" name="id26 83958"></a>202 <a class="indexterm" name="id26 83965"></a>203 <a class="indexterm" name="id26 83971"></a>201 <a class="indexterm" name="id2690014"></a> 202 <a class="indexterm" name="id2690021"></a> 203 <a class="indexterm" name="id2690028"></a> 204 204 If you do not, then <span class="application">nmbd</span> is incorrectly installed. Check your <code class="filename">inetd.conf</code> 205 205 if you run it from there, or that the daemon is running and listening to UDP port 137. … … 209 209 one-line script that contains the right parameters and run that from 210 210 inetd. 211 </p></li><li ><p>212 <a class="indexterm" name="id26 84008"></a>211 </p></li><li class="step" title="Step 5"><p> 212 <a class="indexterm" name="id2690065"></a> 213 213 Run the command <code class="literal">nmblookup -B ACLIENT `*'</code>. 214 214 </p><p> … … 219 219 If ACLIENT does not resolve via DNS, then use the IP address of the 220 220 client in the above test. 221 </p></li><li ><p>221 </p></li><li class="step" title="Step 6"><p> 222 222 Run the command <code class="literal">nmblookup -d 2 `*'</code>. 223 223 </p><p> … … 229 229 messages from several hosts. 230 230 </p><p> 231 <a class="indexterm" name="id26 84066"></a>231 <a class="indexterm" name="id2690122"></a> 232 232 If this does not give a result similar to the previous test, then nmblookup isn't correctly getting your 233 233 broadcast address through its automatic mechanism. In this case you should experiment with the <a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a> option in <code class="filename">smb.conf</code> to manually configure your IP address, broadcast, and netmask. … … 238 238 This test will probably fail if your subnet mask and broadcast address are 239 239 not correct. (Refer to test 3 notes above). 240 </p></li><li ><p>241 <a class="indexterm" name="id26 84118"></a>240 </p></li><li class="step" title="Step 7"><p> 241 <a class="indexterm" name="id2690175"></a> 242 242 Run the command <code class="literal">smbclient //BIGSERVER/TMP</code>. You should 243 243 then be prompted for a password. You should use the password of the account … … 245 245 another account, then add the <code class="option">-U accountname</code> option to the end of 246 246 the command line for example, <code class="literal">smbclient //bigserver/tmp -Ujohndoe</code>. 247 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>247 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 248 248 It is possible to specify the password along with the username as follows: 249 249 <code class="literal">smbclient //bigserver/tmp -Ujohndoe%secret</code>. 250 250 </p></div><p> 251 251 Once you enter the password, you should get the <code class="prompt">smb></code> prompt. If you 252 do not, then look at the error message. If it says “<span class="quote"><span class="errorname">invalid network253 name,</span></span>” then the service <em class="parameter"><code>tmp</code></em> is not correctly set up in your <code class="filename">smb.conf</code>.254 </p><p> 255 If it says “<span class="quote"><span class="errorname">bad password,</span></span>”then the likely causes are:256 </p><div class="orderedlist"><ol type="1"><li><p>252 do not, then look at the error message. If it says <span class="quote">“<span class="quote"><span class="errorname">invalid network 253 name,</span></span>”</span> then the service <em class="parameter"><code>tmp</code></em> is not correctly set up in your <code class="filename">smb.conf</code>. 254 </p><p> 255 If it says <span class="quote">“<span class="quote"><span class="errorname">bad password,</span></span>”</span> then the likely causes are: 256 </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p> 257 257 You have shadow passwords (or some other password system) but didn't 258 258 compile in support for them in <span class="application">smbd</span>. 259 </p></li><li ><p>259 </p></li><li class="listitem"><p> 260 260 Your <a class="link" href="smb.conf.5.html#VALIDUSERS" target="_top">valid users</a> configuration is incorrect. 261 </p></li><li ><p>261 </p></li><li class="listitem"><p> 262 262 You have a mixed-case password and you haven't enabled the <a class="link" href="smb.conf.5.html#PASSWORDLEVEL" target="_top">password level</a> option at a high enough level. 263 </p></li><li ><p>263 </p></li><li class="listitem"><p> 264 264 The <a class="link" href="smb.conf.5.html#PATH" target="_top">path</a> line in <code class="filename">smb.conf</code> is incorrect. Check it with <span class="application">testparm</span>. 265 </p></li><li ><p>265 </p></li><li class="listitem"><p> 266 266 You enabled password encryption but didn't map UNIX to Samba users. Run 267 267 <code class="literal">smbpasswd -a username</code> 268 268 </p></li></ol></div><p> 269 <a class="indexterm" name="id26 84303"></a>270 <a class="indexterm" name="id26 84309"></a>271 <a class="indexterm" name="id26 84316"></a>272 <a class="indexterm" name="id26 84323"></a>269 <a class="indexterm" name="id2690360"></a> 270 <a class="indexterm" name="id2690366"></a> 271 <a class="indexterm" name="id2690373"></a> 272 <a class="indexterm" name="id2690380"></a> 273 273 Once connected, you should be able to use the commands <code class="literal">dir</code>, <code class="literal">get</code>, 274 274 <code class="literal">put</code>, and so on. Type <code class="literal">help command</code> for instructions. You should 275 275 especially check that the amount of free disk space shown is correct when you type <code class="literal">dir</code>. 276 </p></li><li ><p>277 <a class="indexterm" name="id26 84370"></a>276 </p></li><li class="step" title="Step 8"><p> 277 <a class="indexterm" name="id2690426"></a> 278 278 On the PC, type the command <code class="literal">net view \\BIGSERVER</code>. You will 279 279 need to do this from within a DOS prompt window. You should get back a 280 280 list of shares available on the server. 281 281 </p><p> 282 <a class="indexterm" name="id26 84389"></a>282 <a class="indexterm" name="id2690445"></a> 283 283 If you get a message <code class="literal">network name not found</code> or similar error, then NetBIOS 284 284 name resolution is not working. This is usually caused by a problem in <code class="literal">nmbd</code>. 285 285 To overcome it, you could do one of the following (you only need to choose one of them): 286 </p><div class="orderedlist"><ol type="1"><li><p>286 </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p> 287 287 Fix the <span class="application">nmbd</span> installation. 288 </p></li><li ><p>288 </p></li><li class="listitem"><p> 289 289 Add the IP address of BIGSERVER to the <code class="literal">wins server</code> box in the 290 290 advanced TCP/IP setup on the PC. 291 </p></li><li ><p>291 </p></li><li class="listitem"><p> 292 292 Enable Windows name resolution via DNS in the advanced section of the TCP/IP setup. 293 </p></li><li ><p>293 </p></li><li class="listitem"><p> 294 294 Add BIGSERVER to your lmhosts file on the PC. 295 295 </p></li></ol></div><p> 296 If you get a message “<span class="quote"><span class="errorname">invalid network name</span></span>”or297 “<span class="quote"><span class="errorname">bad password error,</span></span>”then apply the296 If you get a message <span class="quote">“<span class="quote"><span class="errorname">invalid network name</span></span>”</span> or 297 <span class="quote">“<span class="quote"><span class="errorname">bad password error,</span></span>”</span> then apply the 298 298 same fixes as for the <code class="literal">smbclient -L</code> test. In 299 299 particular, make sure your <code class="literal">hosts allow</code> line is correct (see the man pages). … … 305 305 name and password. 306 306 </p><p> 307 If you get a message “<span class="quote"><span class="errorname">specified computer is not receiving requests</span></span>”or similar error,307 If you get a message <span class="quote">“<span class="quote"><span class="errorname">specified computer is not receiving requests</span></span>”</span> or similar error, 308 308 it probably means that the host is not contactable via TCP services. 309 309 Check to see if the host is running TCP wrappers, and if so, add an entry in 310 310 the <code class="filename">hosts.allow</code> file for your client (or subnet, and so on.) 311 </p></li><li ><p>311 </p></li><li class="step" title="Step 9"><p> 312 312 Run the command <code class="literal">net use x: \\BIGSERVER\TMP</code>. You should 313 313 be prompted for a password, then you should get a <code class="computeroutput">command completed … … 327 327 and you have <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = no</a> in <code class="filename">smb.conf</code>. 328 328 Change this setting to `yes' to fix this. 329 </p></li><li ><p>329 </p></li><li class="step" title="Step 10"><p> 330 330 Run the command <code class="literal">nmblookup -M <em class="parameter"><code>testgroup</code></em></code> where 331 331 <em class="parameter"><code>testgroup</code></em> is the name of the workgroup that your Samba server and … … 338 338 sure you have <a class="link" href="smb.conf.5.html#PREFERREDMASTER" target="_top">preferred master = yes</a> to ensure that 339 339 an election is held at startup. 340 </p></li><li ><p>340 </p></li><li class="step" title="Step 11"><p> 341 341 From file manager, try to browse the server. Your Samba server should 342 342 appear in the browse list of your local workgroup (or the one you 343 343 specified in <code class="filename">smb.conf</code>). You should be able to double-click on the name 344 of the server and get a list of shares. If you get the error message “<span class="quote">invalid password,</span>”344 of the server and get a list of shares. If you get the error message <span class="quote">“<span class="quote">invalid password,</span>”</span> 345 345 you are probably running Windows NT and it 346 346 is refusing to browse a server that has no encrypted password … … 349 349 <a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server = Windows_NT_Machine</a> in your 350 350 <code class="filename">smb.conf</code> file or make sure <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords</a> is 351 set to “<span class="quote">yes</span>”.351 set to <span class="quote">“<span class="quote">yes</span>”</span>. 352 352 </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.
