1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN">
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.7"><LINK
11 HREF=
"samba-faq.html"><LINK
13 TITLE=
"Specific client application problems"
14 HREF=
"faq-clientapp.html"><LINK
17 HREF=
"faq-features.html"></HEAD
28 SUMMARY=
"Header navigation table"
45 HREF=
"faq-clientapp.html"
59 HREF=
"faq-features.html"
74 >Chapter
5. Common errors
</H1
84 HREF=
"faq-errors.html#AEN209"
85 >Not listening for calling name
</A
89 HREF=
"faq-errors.html#AEN216"
94 HREF=
"faq-errors.html#AEN223"
95 >smbclient ignores -N !
</A
99 HREF=
"faq-errors.html#AEN232"
100 >The data on the CD-Drive I've shared seems to be corrupted!
</A
104 HREF=
"faq-errors.html#AEN236"
105 >Why can users access home directories of other users?
</A
109 HREF=
"faq-errors.html#AEN249"
110 >Until a few minutes after samba has started, clients get the error
"Domain Controller Unavailable"</A
114 HREF=
"faq-errors.html#AEN252"
115 >I'm getting
"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs
</A
125 >5.1. Not listening for calling name
</A
129 CLASS=
"PROGRAMLISTING"
130 >Session request failed (
131,
129) with myname=HOBBES destname=CALVIN
131 Not listening for calling name
</PRE
134 >If you get this when talking to a Samba box then it means that your
135 global
"hosts allow" or
"hosts deny" settings are causing the Samba
136 server to refuse the connection.
</P
138 >Look carefully at your
"hosts allow" and
"hosts deny" lines in the
139 global section of smb.conf.
</P
141 >It can also be a problem with reverse DNS lookups not functioning
142 correctly, leading to the remote host identity not being able to
143 be confirmed, but that is less likely.
</P
151 >5.2. System Error
1240</A
154 >System error
1240 means that the client is refusing to talk
155 to a non-encrypting server. Microsoft changed WinNT in service
156 pack
3 to refuse to connect to servers that do not support
157 SMB password encryption.
</P
159 >There are two main solutions:
167 >enable SMB password encryption in Samba. See the encryption part of
168 the samba HOWTO Collection
</TD
172 >disable this new behaviour in NT. See the section about
173 Windows NT in the chapter
"Portability" of the samba HOWTO collection
</TD
187 >5.3. smbclient ignores -N !
</A
192 >"When getting the list of shares available on a host using the command
197 the program always prompts for the password if the server is a Samba server.
198 It also ignores the "-N
" argument when querying some (but not all) of our
202 >No, it does not ignore -N, it is just that your server rejected the
203 null password in the connection, so smbclient prompts for a password
206 >To get the behaviour that you probably want use
<B
208 >smbclient -L host -U%
</B
211 >This will set both the username and password to null, which is
212 an anonymous login for SMB. Using -N would only set the password
213 to null, and this is not accepted as an anonymous login for most
222 >5.4. The data on the CD-Drive I've shared seems to be corrupted!
</A
225 >Some OSes (notably Linux) default to auto detection of file type on
226 cdroms and do cr/lf translation. This is a very bad idea when use with
227 Samba. It causes all sorts of stuff ups.
</P
229 >To overcome this problem use conv=binary when mounting the cdrom
230 before exporting it with Samba.
</P
238 >5.5. Why can users access home directories of other users?
</A
243 >"We are unable to keep individual users from mapping to any other user's
244 home directory once they have supplied a valid password! They only need
245 to enter their own password. I have not found *any* method that I can
246 use to configure samba to enforce that only a user may map their own
247 home directory."</SPAN
252 >"User xyzzy can map his home directory. Once mapped user xyzzy can also map
253 *anyone* elses home directory!"</SPAN
256 >This is not a security flaw, it is by design. Samba allows
257 users to have *exactly* the same access to the UNIX filesystem
258 as they would if they were logged onto the UNIX box, except
259 that it only allows such views onto the file system as are
260 allowed by the defined shares.
</P
262 >This means that if your UNIX home directories are set up
263 such that one user can happily cd into another users
264 directory and do an ls, the UNIX security solution is to
265 change the UNIX file permissions on the users home directories
266 such that the cd and ls would be denied.
</P
268 >Samba tries very hard not to second guess the UNIX administrators
269 security policies, and trusts the UNIX admin to set
270 the policies and permissions he or she desires.
</P
272 >Samba does allow the setup you require when you have set the
273 "only user = yes" option on the share, is that you have not set the
274 valid users list for the share.
</P
276 >Note that only user works in conjunction with the users= list,
277 so to get the behavior you require, add the line :
279 CLASS=
"PROGRAMLISTING"
282 this is equivalent to:
284 CLASS=
"PROGRAMLISTING"
285 >valid users = %S
</PRE
287 to the definition of the [homes] share, as recommended in
288 the smb.conf man page.
</P
296 >5.6. Until a few minutes after samba has started, clients get the error
"Domain Controller Unavailable"</A
299 >A domain controller has to announce on the network who it is. This usually takes a while.
</P
307 >5.7. I'm getting
"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs
</A
310 >Your loopback device isn't working correctly. Make sure it's running.
</P
318 SUMMARY=
"Footer navigation table"
329 HREF=
"faq-clientapp.html"
338 HREF=
"samba-faq.html"
347 HREF=
"faq-features.html"
357 >Specific client application problems
</TD