- Timestamp:
- Sep 30, 2008, 7:14:08 AM (17 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.0/docs/htmldocs/Samba3-HOWTO/diagnosis.html
r134 r158 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"><<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#id4 62256">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="id4 62264"></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"><<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#id436512">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id436545">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id436824">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="id436512"></a>Introduction</h2></div></div></div><p> 2 <a class="indexterm" name="id436520"></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 … … 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="id4 62289"></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="id436545"></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="id4 62356"></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>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="id436613"></a><em class="parameter"><code>comment = temporary files </code></em></td></tr><tr><td><a class="indexterm" name="id436624"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td><a class="indexterm" name="id436636"></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> 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="id4 62399"></a>32 <a class="indexterm" name="id4 62406"></a>33 <a class="indexterm" name="id4 62413"></a>31 <a class="indexterm" name="id436656"></a> 32 <a class="indexterm" name="id436663"></a> 33 <a class="indexterm" name="id436669"></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="id4 62431"></a>40 <a class="indexterm" name="id4 62438"></a>41 <a class="indexterm" name="id4 62445"></a>42 <a class="indexterm" name="id4 62452"></a>39 <a class="indexterm" name="id436688"></a> 40 <a class="indexterm" name="id436694"></a> 41 <a class="indexterm" name="id436701"></a> 42 <a class="indexterm" name="id436708"></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="id4 62480"></a>48 <a class="indexterm" name="id4 62487"></a>49 <a class="indexterm" name="id4 62494"></a>50 <a class="indexterm" name="id4 62501"></a>51 <a class="indexterm" name="id4 62508"></a>47 <a class="indexterm" name="id436737"></a> 48 <a class="indexterm" name="id436744"></a> 49 <a class="indexterm" name="id436750"></a> 50 <a class="indexterm" name="id436757"></a> 51 <a class="indexterm" name="id436764"></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="id4 62567"></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="id4 62585"></a>62 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id436824"></a>The Tests</h2></div></div></div><div class="procedure"><a name="id436829"></a><p class="title"><b>Procedure 38.1. Diagnosing Your Samba Server</b></p><ol type="1"><li><p> 63 <a class="indexterm" name="id436842"></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 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="id4 62615"></a>69 <a class="indexterm" name="id4 62622"></a>68 <a class="indexterm" name="id436871"></a> 69 <a class="indexterm" name="id436878"></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 72 </p></div></li><li><p> 73 <a class="indexterm" name="id4 62655"></a>73 <a class="indexterm" name="id436912"></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, … … 78 78 You will need to start a “<span class="quote">DOS prompt</span>” window on the PC to run ping. 79 79 </p><p> 80 <a class="indexterm" name="id4 62686"></a>81 <a class="indexterm" name="id4 62693"></a>82 <a class="indexterm" name="id4 62699"></a>80 <a class="indexterm" name="id436942"></a> 81 <a class="indexterm" name="id436949"></a> 82 <a class="indexterm" name="id436956"></a> 83 83 If you get a message saying “<span class="quote"><span class="errorname">host not found</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 … … 87 87 remainder of these tests. 88 88 </p><p> 89 <a class="indexterm" name="id4 62729"></a>90 <a class="indexterm" name="id4 62735"></a>91 <a class="indexterm" name="id4 62742"></a>89 <a class="indexterm" name="id436985"></a> 90 <a class="indexterm" name="id436992"></a> 91 <a class="indexterm" name="id436999"></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 … … 99 99 This is a common problem that is often overlooked. 100 100 </p></div><p> 101 <a class="indexterm" name="id4 62774"></a>102 <a class="indexterm" name="id4 62781"></a>101 <a class="indexterm" name="id437030"></a> 102 <a class="indexterm" name="id437037"></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, … … 134 134 on the UNIX box. You should get back a list of available shares. 135 135 </p><p> 136 <a class="indexterm" name="id4 62852"></a>137 <a class="indexterm" name="id4 62859"></a>138 <a class="indexterm" name="id4 62865"></a>139 <a class="indexterm" name="id4 62872"></a>140 <a class="indexterm" name="id4 62879"></a>141 <a class="indexterm" name="id4 62886"></a>136 <a class="indexterm" name="id437108"></a> 137 <a class="indexterm" name="id437115"></a> 138 <a class="indexterm" name="id437122"></a> 139 <a class="indexterm" name="id437129"></a> 140 <a class="indexterm" name="id437135"></a> 141 <a class="indexterm" name="id437142"></a> 142 142 If you get an error message containing the string “<span class="quote">bad password</span>”, then 143 143 you probably have either an incorrect <em class="parameter"><code>hosts allow</code></em>, … … 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="id4 62954"></a>149 <a class="indexterm" name="id437211"></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 … … 154 154 state using <code class="literal">netstat -a</code>. 155 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="id4 62991"></a>157 <a class="indexterm" name="id4 62998"></a>156 <a class="indexterm" name="id437247"></a> 157 <a class="indexterm" name="id437254"></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 … … 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="id4 63104"></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="id4 63153"></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="id437360"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id437372"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy</code></em></td></tr><tr><td><a class="indexterm" name="id437383"></a><em class="parameter"><code>interfaces = eth0</code></em></td></tr><tr><td><a class="indexterm" name="id437395"></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="id437409"></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="id4 63202"></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="id4 63240"></a>182 <a class="indexterm" name="id4 63246"></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="id437458"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id437470"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy 127.</code></em></td></tr><tr><td><a class="indexterm" name="id437481"></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="id437496"></a> 182 <a class="indexterm" name="id437503"></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="id4 63288"></a>189 <a class="indexterm" name="id4 63295"></a>190 <a class="indexterm" name="id4 63301"></a>191 <a class="indexterm" name="id4 63308"></a>192 <a class="indexterm" name="id4 63315"></a>188 <a class="indexterm" name="id437545"></a> 189 <a class="indexterm" name="id437551"></a> 190 <a class="indexterm" name="id437558"></a> 191 <a class="indexterm" name="id437565"></a> 192 <a class="indexterm" name="id437571"></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 196 </p></li><li><p> 197 <a class="indexterm" name="id4 63339"></a>197 <a class="indexterm" name="id437595"></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="id4 63356"></a>202 <a class="indexterm" name="id4 63363"></a>203 <a class="indexterm" name="id4 63369"></a>201 <a class="indexterm" name="id437612"></a> 202 <a class="indexterm" name="id437619"></a> 203 <a class="indexterm" name="id437626"></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. … … 210 210 inetd. 211 211 </p></li><li><p> 212 <a class="indexterm" name="id4 63403"></a>212 <a class="indexterm" name="id437659"></a> 213 213 Run the command <code class="literal">nmblookup -B ACLIENT `*'</code>. 214 214 </p><p> … … 229 229 messages from several hosts. 230 230 </p><p> 231 <a class="indexterm" name="id4 63455"></a>231 <a class="indexterm" name="id437711"></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">interfaces</a> option in <code class="filename">smb.conf</code> to manually configure your IP address, broadcast, and netmask. … … 239 239 not correct. (Refer to test 3 notes above). 240 240 </p></li><li><p> 241 <a class="indexterm" name="id4 63501"></a>241 <a class="indexterm" name="id437758"></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 … … 267 267 <code class="literal">smbpasswd -a username</code> 268 268 </p></li></ol></div><p> 269 <a class="indexterm" name="id4 63675"></a>270 <a class="indexterm" name="id4 63682"></a>271 <a class="indexterm" name="id4 63689"></a>272 <a class="indexterm" name="id4 63695"></a>269 <a class="indexterm" name="id437932"></a> 270 <a class="indexterm" name="id437938"></a> 271 <a class="indexterm" name="id437945"></a> 272 <a class="indexterm" name="id437952"></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 276 </p></li><li><p> 277 <a class="indexterm" name="id4 63740"></a>277 <a class="indexterm" name="id437997"></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="id4 63758"></a>282 <a class="indexterm" name="id438014"></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>.
Note:
See TracChangeset
for help on using the changeset viewer.
