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
@@ -14,7 +14,7 @@ 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 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 @@ -24,7 +24,7 @@ SMB password encryption. the samba HOWTO Collectiondisable this behaviour in NT. See the section about 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. @@ -42,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!

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