1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 37. The Samba Checklist</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.68.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 38. 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 37. 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 37. 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 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 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 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#id2649141">Introduction</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2649180">Assumptions</a></span></dt><dt><span class="sect1"><a href="diagnosis.html#id2649477">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="id2649141"></a>Introduction</h2></div></div></div><p>
2 <a class="indexterm" name="id2649149"></a>
3 This file contains a list of tests you can perform to validate your
4 Samba server. It also tells you what the likely cause of the problem
5 is if it fails any one of these steps. If it passes all these tests,
6 then it is probably working fine.
8 You should do all the tests in the order shown. We have tried to
9 carefully choose them so later tests only use capabilities verified in
10 the earlier tests. However, do not stop at the first error: there
11 have been some instances when continuing with the tests has helped
14 If you send one of the Samba mailing lists an email saying, “<span class="quote">It does not work,</span>”
15 and you have not followed this test procedure, you should not be surprised
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="id2649180"></a>Assumptions</h2></div></div></div><p>
18 In all of the tests, it is assumed you have a Samba server called
19 BIGSERVER and a PC called ACLIENT, both in workgroup TESTGROUP.
21 The procedure is similar for other types of clients.
23 It is also assumed you know the name of an available share in your
24 <code class="filename">smb.conf</code>. I for our examples this share is called <em class="parameter"><code>tmp</code></em>.
25 You can add a <em class="parameter"><code>tmp</code></em> share like this by adding the
26 lines shown in <a href="diagnosis.html#tmpshare" title="Example 37.1. smb.conf with [tmp] Share">the next example</a>.
27 </p><div class="example"><a name="tmpshare"></a><p class="title"><b>Example 37.1. smb.conf with [tmp] Share</b></p><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="id2649252"></a><em class="parameter"><code>comment = temporary files </code></em></td></tr><tr><td><a class="indexterm" name="id2649264"></a><em class="parameter"><code>path = /tmp</code></em></td></tr><tr><td><a class="indexterm" name="id2649277"></a><em class="parameter"><code>read only = yes</code></em></td></tr></table></div><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.
31 <a class="indexterm" name="id2649299"></a>
32 <a class="indexterm" name="id2649306"></a>
33 <a class="indexterm" name="id2649313"></a>
34 Please pay attention to the error messages you receive. If any error message
35 reports that your server is being unfriendly, you should first check that your
36 IP name resolution is correctly set up. Make sure your <code class="filename">/etc/resolv.conf</code>
37 file points to name servers that really do exist.
39 <a class="indexterm" name="id2649334"></a>
40 <a class="indexterm" name="id2649341"></a>
41 <a class="indexterm" name="id2649348"></a>
42 <a class="indexterm" name="id2649354"></a>
43 Also, if you do not have DNS server access for name resolution, please check
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 best way to check this is with <span><strong class="command">testparm smb.conf</strong></span>.
47 <a class="indexterm" name="id2649385"></a>
48 <a class="indexterm" name="id2649392"></a>
49 <a class="indexterm" name="id2649399"></a>
50 <a class="indexterm" name="id2649406"></a>
51 <a class="indexterm" name="id2649413"></a>
52 It is helpful to monitor the log files during testing by using the
53 <span><strong class="command">tail -F log_file_name</strong></span> in a separate
54 terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X).
55 Relevant log files can be found (for default installations) in
56 <code class="filename">/usr/local/samba/var</code>. Also, connection logs from
57 machines can be found here or possibly in <code class="filename">/var/log/samba</code>,
58 depending on how or if you specified logging in your <code class="filename">smb.conf</code> file.
60 If you make changes to your <code class="filename">smb.conf</code> file while going through these test,
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="id2649477"></a>The Tests</h2></div></div></div><div class="procedure"><a name="id2649482"></a><p class="title"><b>Procedure 37.1. Diagnosing Your Samba Server</b></p><ol type="1"><li><p>
63 <a class="indexterm" name="id2649495"></a>
64 In the directory in which you store your <code class="filename">smb.conf</code> file, run the command
65 <span><strong class="command">testparm smb.conf</strong></span>. If it reports any errors, then your <code class="filename">smb.conf</code>
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="id2649526"></a>
69 <a class="indexterm" name="id2649533"></a>
70 Your <code class="filename">smb.conf</code> file may be located in <code class="filename">/etc/samba</code>
71 or in <code class="filename">/usr/local/samba/lib</code>.
72 </p></div></li><li><p>
73 <a class="indexterm" name="id2649567"></a>
74 Run the command <span><strong class="command">ping BIGSERVER</strong></span> from the PC and
75 <span><strong class="command">ping ACLIENT</strong></span> from the UNIX box. If you do not get a valid response,
76 then your TCP/IP software is not correctly installed.
78 You will need to start a “<span class="quote">DOS prompt</span>” window on the PC to run ping.
80 <a class="indexterm" name="id2649599"></a>
81 <a class="indexterm" name="id2649606"></a>
82 <a class="indexterm" name="id2649613"></a>
83 If you get a message saying “<span class="quote"><span class="errorname">host not found</span></span>” or a similar message, then
84 your DNS software or <code class="filename">/etc/hosts</code> file is not correctly set up. If using DNS, check that
85 the <code class="filename">/etc/resolv.conf</code> has correct, current, entries in it. It is possible to run
86 Samba without DNS entries for the server and client, but it is assumed you do have correct entries for the
87 remainder of these tests.
89 <a class="indexterm" name="id2649645"></a>
90 <a class="indexterm" name="id2649652"></a>
91 <a class="indexterm" name="id2649659"></a>
92 Another reason why ping might fail is if your host is running firewall
93 software. You will need to relax the rules to let in the workstation
94 in question, perhaps by allowing access from another subnet (on Linux
95 this is done via the appropriate firewall maintenance commands <span><strong class="command">ipchains</strong></span>
96 or <span><strong class="command">iptables</strong></span>).
97 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
98 Modern Linux distributions install ipchains/iptables by default.
99 This is a common problem that is often overlooked.
101 <a class="indexterm" name="id2649694"></a>
102 <a class="indexterm" name="id2649701"></a>
103 If you wish to check what firewall rules may be present in a system under test, simply run
104 <span><strong class="command">iptables -L -v</strong></span>, or if <em class="parameter"><code>ipchains</code></em>-based firewall rules are in use,
105 <span><strong class="command">ipchains -L -v</strong></span>.
107 Here is a sample listing from a system that has an external Ethernet interface (eth1) on which Samba
108 is not active and an internal (private network) interface (eth0) on which Samba is active:
109 </p><pre class="screen">
110 frodo:~ # iptables -L -v
111 Chain INPUT (policy DROP 98496 packets, 12M bytes)
112 pkts bytes target prot opt in out source destination
113 187K 109M ACCEPT all -- lo any anywhere anywhere
114 892K 125M ACCEPT all -- eth0 any anywhere anywhere
115 1399K 1380M ACCEPT all -- eth1 any anywhere anywhere \
116 state RELATED,ESTABLISHED
118 Chain FORWARD (policy DROP 0 packets, 0 bytes)
119 pkts bytes target prot opt in out source destination
120 978K 1177M ACCEPT all -- eth1 eth0 anywhere anywhere \
121 state RELATED,ESTABLISHED
122 658K 40M ACCEPT all -- eth0 eth1 anywhere anywhere
123 0 0 LOG all -- any any anywhere anywhere \
126 Chain OUTPUT (policy ACCEPT 2875K packets, 1508M bytes)
127 pkts bytes target prot opt in out source destination
129 Chain reject_func (0 references)
130 pkts bytes target prot opt in out source destination
133 Run the command <span><strong class="command">smbclient -L BIGSERVER</strong></span>
134 on the UNIX box. You should get back a list of available shares.
136 <a class="indexterm" name="id2649776"></a>
137 <a class="indexterm" name="id2649783"></a>
138 <a class="indexterm" name="id2649790"></a>
139 <a class="indexterm" name="id2649796"></a>
140 <a class="indexterm" name="id2649803"></a>
141 <a class="indexterm" name="id2649810"></a>
142 If you get an error message containing the string “<span class="quote">bad password</span>”, then
143 you probably have either an incorrect <em class="parameter"><code>hosts allow</code></em>,
144 <em class="parameter"><code>hosts deny</code></em>, or <em class="parameter"><code>valid users</code></em> line in your
145 <code class="filename">smb.conf</code>, or your guest account is not valid. Check what your guest account is using <span class="application">testparm</span> and
146 temporarily remove any <em class="parameter"><code>hosts allow</code></em>, <em class="parameter"><code>hosts deny</code></em>,
147 <em class="parameter"><code>valid users</code></em>, or <em class="parameter"><code>invalid users</code></em> lines.
149 <a class="indexterm" name="id2649881"></a>
150 If you get a message <code class="literal">connection refused</code> response, then the <span><strong class="command">smbd</strong></span> server may
151 not be running. If you installed it in <code class="filename">inetd.conf</code>, then you probably edited
152 that file incorrectly. If you installed it as a daemon, then check that
153 it is running and check that the netbios-ssn port is in a LISTEN
154 state using <span><strong class="command">netstat -a</strong></span>.
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="id2649920"></a>
157 <a class="indexterm" name="id2649927"></a>
158 Some UNIX/Linux systems use <span><strong class="command">xinetd</strong></span> in place of
159 <span><strong class="command">inetd</strong></span>. Check your system documentation for the location
160 of the control files for your particular system implementation of
161 the network super daemon.
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>” then
165 it's probably because you have invalid command line parameters to <span class="application">smbd</span>,
166 or a similar fatal problem with the initial startup of <span class="application">smbd</span>. Also
167 check your config file (<code class="filename">smb.conf</code>) for syntax errors with <span class="application">testparm</span>
168 and that the various directories where Samba keeps its log and lock
171 There are a number of reasons for which smbd may refuse or decline
172 a session request. The most common of these involve one or more of
173 the <code class="filename">smb.conf</code> file entries as shown in <a href="diagnosis.html#modif1" title="Example 37.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 37.2. Configuration for Allowing Connections Only from a Certain Subnet</b></p><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="id2650040"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id2650052"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy</code></em></td></tr><tr><td><a class="indexterm" name="id2650065"></a><em class="parameter"><code>interfaces = eth0</code></em></td></tr><tr><td><a class="indexterm" name="id2650078"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr></table></div><p>
175 <a class="indexterm" name="id2650094"></a>
176 In <a href="diagnosis.html#modif1" title="Example 37.2. Configuration for Allowing Connections Only from a Certain Subnet">Configuration for Allowing Connections Only from a Certain Subnet</a>, no
177 allowance has been made for any session requests that will automatically translate to the loopback adapter
178 address 127.0.0.1. To solve this problem, change these lines as shown in <a href="diagnosis.html#modif2" title="Example 37.3. Configuration for Allowing Connections from a Certain Subnet and localhost">the following
180 </p><div class="example"><a name="modif2"></a><p class="title"><b>Example 37.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><em class="parameter"><code>[globals]</code></em></td></tr><tr><td><a class="indexterm" name="id2650146"></a><em class="parameter"><code>hosts deny = ALL</code></em></td></tr><tr><td><a class="indexterm" name="id2650158"></a><em class="parameter"><code>hosts allow = xxx.xxx.xxx.xxx/yy 127.</code></em></td></tr><tr><td><a class="indexterm" name="id2650172"></a><em class="parameter"><code>interfaces = eth0 lo</code></em></td></tr></table></div><p>
181 <a class="indexterm" name="id2650188"></a>
182 <a class="indexterm" name="id2650194"></a>
183 Another common cause of these two errors is having something already running on port <code class="constant">139</code>,
184 such as Samba (<span class="application">smbd</span> is running from <span class="application">inetd</span> already) or Digital's Pathworks. Check
185 your <code class="filename">inetd.conf</code> file before trying to start <span class="application">smbd</span> as a daemon it can avoid a
188 <a class="indexterm" name="id2650239"></a>
189 <a class="indexterm" name="id2650245"></a>
190 <a class="indexterm" name="id2650252"></a>
191 <a class="indexterm" name="id2650259"></a>
192 <a class="indexterm" name="id2650266"></a>
193 And yet another possible cause for failure of this test is when the subnet mask and/or broadcast address
194 settings are incorrect. Please check that the network interface IP address/broadcast address/subnet mask
195 settings are correct and that Samba has correctly noted these in the <code class="filename">log.nmbd</code> file.
197 <a class="indexterm" name="id2650292"></a>
198 Run the command <span><strong class="command">nmblookup -B BIGSERVER __SAMBA__</strong></span>.
199 You should get back the IP address of your Samba server.
201 <a class="indexterm" name="id2650310"></a>
202 <a class="indexterm" name="id2650316"></a>
203 <a class="indexterm" name="id2650323"></a>
204 If you do not, then <span class="application">nmbd</span> is incorrectly installed. Check your <code class="filename">inetd.conf</code>
205 if you run it from there, or that the daemon is running and listening to UDP port 137.
207 One common problem is that many inetd implementations can't take many
208 parameters on the command line. If this is the case, then create a
209 one-line script that contains the right parameters and run that from
212 <a class="indexterm" name="id2650360"></a>
213 Run the command <span><strong class="command">nmblookup -B ACLIENT `*'</strong></span>.
215 You should get the PC's IP address back. If you do not, then the client
216 software on the PC isn't installed correctly, or isn't started, or you
217 got the name of the PC wrong.
219 If ACLIENT does not resolve via DNS, then use the IP address of the
220 client in the above test.
222 Run the command <span><strong class="command">nmblookup -d 2 `*'</strong></span>.
224 This time we are trying the same as the previous test but are trying
225 it via a broadcast to the default broadcast address. A number of
226 NetBIOS/TCP/IP hosts on the network should respond, although Samba may
227 not catch all of the responses in the short time it listens. You
228 should see the <code class="literal">got a positive name query response</code>
229 messages from several hosts.
231 <a class="indexterm" name="id2650417"></a>
232 If this does not give a result similar to the previous test, then nmblookup isn't correctly getting your
233 broadcast address through its automatic mechanism. In this case you should experiment with the <a class="indexterm" name="id2650428"></a>interfaces option in <code class="filename">smb.conf</code> to manually configure your IP address, broadcast, and netmask.
235 If your PC and server aren't on the same subnet, then you will need to use the
236 <code class="option">-B</code> option to set the broadcast address to that of the PC's subnet.
238 This test will probably fail if your subnet mask and broadcast address are
239 not correct. (Refer to test 3 notes above).
241 <a class="indexterm" name="id2650465"></a>
242 Run the command <span><strong class="command">smbclient //BIGSERVER/TMP</strong></span>. You should
243 then be prompted for a password. You should use the password of the account
244 with which you are logged into the UNIX box. If you want to test with
245 another account, then add the <code class="option">-U accountname</code> option to the end of
246 the command line for example, <span><strong class="command">smbclient //bigserver/tmp -Ujohndoe</strong></span>.
247 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
248 It is possible to specify the password along with the username as follows:
249 <span><strong class="command">smbclient //bigserver/tmp -Ujohndoe%secret</strong></span>.
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 network
253 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>.
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>
257 You have shadow passwords (or some other password system) but didn't
258 compile in support for them in <span class="application">smbd</span>.
260 Your <a class="indexterm" name="id2650570"></a>valid users configuration is incorrect.
262 You have a mixed-case password and you haven't enabled the <a class="indexterm" name="id2650585"></a>password level option at a high enough level.
264 The <a class="indexterm" name="id2650600"></a>path line in <code class="filename">smb.conf</code> is incorrect. Check it with <span class="application">testparm</span>.
266 You enabled password encryption but didn't map UNIX to Samba users. Run
267 <span><strong class="command">smbpasswd -a username</strong></span>
268 </p></li></ol></div><p>
269 <a class="indexterm" name="id2650638"></a>
270 <a class="indexterm" name="id2650645"></a>
271 <a class="indexterm" name="id2650652"></a>
272 <a class="indexterm" name="id2650658"></a>
273 Once connected, you should be able to use the commands <span><strong class="command">dir</strong></span>, <span><strong class="command">get</strong></span>,
274 <span><strong class="command">put</strong></span>, and so on. Type <span><strong class="command">help command</strong></span> for instructions. You should
275 especially check that the amount of free disk space shown is correct when you type <span><strong class="command">dir</strong></span>.
277 <a class="indexterm" name="id2650705"></a>
278 On the PC, type the command <span><strong class="command">net view \\BIGSERVER</strong></span>. You will
279 need to do this from within a DOS prompt window. You should get back a
280 list of shares available on the server.
282 <a class="indexterm" name="id2650724"></a>
283 If you get a message <code class="literal">network name not found</code> or similar error, then NetBIOS
284 name resolution is not working. This is usually caused by a problem in <span><strong class="command">nmbd</strong></span>.
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>
287 Fix the <span class="application">nmbd</span> installation.
289 Add the IP address of BIGSERVER to the <span><strong class="command">wins server</strong></span> box in the
290 advanced TCP/IP setup on the PC.
292 Enable Windows name resolution via DNS in the advanced section of the TCP/IP setup.
294 Add BIGSERVER to your lmhosts file on the PC.
295 </p></li></ol></div><p>
296 If you get a message “<span class="quote"><span class="errorname">invalid network name</span></span>” or
297 “<span class="quote"><span class="errorname">bad password error,</span></span>” then apply the
298 same fixes as for the <span><strong class="command">smbclient -L</strong></span> test. In
299 particular, make sure your <span><strong class="command">hosts allow</strong></span> line is correct (see the man pages).
301 Also, do not overlook that fact that when the workstation requests the
302 connection to the Samba server, it will attempt to connect using the
303 name with which you logged onto your Windows machine. You need to make
304 sure that an account exists on your Samba server with that exact same
307 If you get a message “<span class="quote"><span class="errorname">specified computer is not receiving requests</span></span>” or similar error,
308 it probably means that the host is not contactable via TCP services.
309 Check to see if the host is running TCP wrappers, and if so, add an entry in
310 the <code class="filename">hosts.allow</code> file for your client (or subnet, and so on.)
312 Run the command <span><strong class="command">net use x: \\BIGSERVER\TMP</strong></span>. You should
313 be prompted for a password, then you should get a <code class="computeroutput">command completed
314 successfully</code> message. If not, then your PC software is incorrectly
315 installed or your <code class="filename">smb.conf</code> is incorrect. Make sure your <em class="parameter"><code>hosts allow</code></em>
316 and other config lines in <code class="filename">smb.conf</code> are correct.
318 It's also possible that the server can't work out what username to connect you as.
319 To see if this is the problem, add the line
320 <a class="indexterm" name="id2650890"></a>user = username to the
321 <em class="parameter"><code>[tmp]</code></em> section of
322 <code class="filename">smb.conf</code> where <em class="parameter"><code>username</code></em> is the
323 username corresponding to the password you typed. If you find this
324 fixes things, you may need the username mapping option.
326 It might also be the case that your client only sends encrypted passwords
327 and you have <a class="indexterm" name="id2650923"></a>encrypt passwords = no in <code class="filename">smb.conf</code>.
328 Change this setting to `yes' to fix this.
330 Run the command <span><strong class="command">nmblookup -M <em class="parameter"><code>testgroup</code></em></strong></span> where
331 <em class="parameter"><code>testgroup</code></em> is the name of the workgroup that your Samba server and
332 Windows PCs belong to. You should get back the IP address of the
333 master browser for that workgroup.
335 If you do not, then the election process has failed. Wait a minute to
336 see if it is just being slow, then try again. If it still fails after
337 that, then look at the browsing options you have set in <code class="filename">smb.conf</code>. Make
338 sure you have <a class="indexterm" name="id2650978"></a>preferred master = yes to ensure that
339 an election is held at startup.
341 From file manager, try to browse the server. Your Samba server should
342 appear in the browse list of your local workgroup (or the one you
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>”
345 you are probably running Windows NT and it
346 is refusing to browse a server that has no encrypted password
347 capability and is in user-level security mode. In this case, either set
348 <a class="indexterm" name="id2651012"></a>security = server and
349 <a class="indexterm" name="id2651020"></a>password server = Windows_NT_Machine in your
350 <code class="filename">smb.conf</code> file or make sure <a class="indexterm" name="id2651034"></a>encrypt passwords is
351 set to “<span class="quote">yes</span>”.
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 38. Analyzing and Solving Samba Problems</td></tr></table></div></body></html>
projects / samba / blob