From cad70ca6eda6498db9acdae97fade2c615c3ce5b Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Thu, 28 Aug 2003 22:13:10 +0000 Subject: Regenerate docs (This used to be commit b78c6ee1d155f255d329899c237281c7cf662260) --- docs/faq/FAQ-errors.html | 29 ++++++++++++++--------------- 1 file changed, 14 insertions(+), 15 deletions(-) (limited to 'docs/faq/FAQ-errors.html') diff --git a/docs/faq/FAQ-errors.html b/docs/faq/FAQ-errors.html index 5f9a5f54b4..ed896b9805 100644 --- a/docs/faq/FAQ-errors.html +++ b/docs/faq/FAQ-errors.html @@ -1,35 +1,34 @@ - -Chapter 4. Common errors
Chapter 4. Common errors
Prev   Next

Chapter 4. Common errors

Table of Contents

Not listening for calling name
System Error 1240
smbclient ignores -N !
The data on the CD-Drive I've shared seems to be corrupted!

Not listening for calling name

-
+Chapter 4. Common errors
Chapter 4. Common errors
Prev   Next
Chapter 4. Common errors
Table of Contents
Not listening for calling name
System Error 1240
smbclient ignores -N !
The data on the CD-Drive I've shared seems to be corrupted!
Not listening for calling name

+
 Session request failed (131,129) with myname=HOBBES destname=CALVIN
 Not listening for calling name
-

-

+

+

If you get this when talking to a Samba box then it means that your -global "hosts allow" or "hosts deny" settings are causing the Samba +global "hosts allow" or "hosts deny" settings are causing the Samba server to refuse the connection.

-Look carefully at your "hosts allow" and "hosts deny" lines in the +Look carefully at your "hosts allow" and "hosts deny" lines in the global section of smb.conf.

It can also be a problem with reverse DNS lookups not functioning correctly, leading to the remote host identity not being able to be confirmed, but that is less likely. -

System Error 1240

+

System Error 1240

System error 1240 means that the client is refusing to talk to a non-encrypting server. Microsoft changed WinNT in service pack 3 to refuse to connect to servers that do not support SMB password encryption. -

There are two main solutions: -
enable SMB password encryption in Samba. See the encryption part of +

There are two main solutions: +

enable SMB password encryption in Samba. See the encryption part of the samba HOWTO Collection
disable this behaviour in NT. See the section about -Windows NT in the chapter "Portability" of the samba HOWTO collection -
-

smbclient ignores -N !

+Windows NT in the chapter "Portability" of the samba HOWTO collection +

+

smbclient ignores -N !

“When getting the list of shares available on a host using the command smbclient -N -L the program always prompts for the password if the server is a Samba server. -It also ignores the "-N" argument when querying some (but not all) of our +It also ignores the "-N" argument when querying some (but not all) of our NT servers. ”

@@ -43,7 +42,7 @@ This will set both the username and password to null, which is an anonymous login for SMB. Using -N would only set the password to null, and this is not accepted as an anonymous login for most SMB servers. -

The data on the CD-Drive I've shared seems to be corrupted!

+

The data on the CD-Drive I've shared seems to be corrupted!

Some OSes (notably Linux) default to auto detection of file type on cdroms and do cr/lf translation. This is a very bad idea when use with Samba. It causes all sorts of stuff ups. -- cgit