Garrett Burke Garrett.Burke@msc.ie wrote:

Anyone know of any issues with smbclient (version 1.9.18p8) and filers running CIFS (OnTap 5.2.1)?

Session setup is failing. I can use smbclient to connect to my NT servers but not the filer. I notice from the debug output of smbclient that it says "Using encrypted passwords" Could this be the problem? Can't see anything on the smbclient man page to force it to use unencrypted passwords.

Here's some "-d 3" output from smbclient:

[..]

(Before you all say "use NFS", I'm writing some monitoring tools that will run on a FreeBSD box and will actually fetch a file from the filer and calc a CRC to ensure it's ok. This way I know the file service is available)

Hi Garrett,

Yes, there is a problem with the filer's handling of Session Setup requests in 5.2 that prevents smbclient from connecting. What's happening is smbclient is trying to connect with a client buffer size of 0x4400, but 5.2 rejects any client using a buffer size greater than 0x2000. So, you can recompile smbclient with the CLI_BUFFER_SIZE constant set to 0x2000 to get an smbclient that can connect to 5.2. (See below for the patch.) With that patch, smbclient should work well enough for you to at least connect and fetch a file. (There could be other bugs, though... we haven't spent any time testing smbclient yet, on any release.)

In 5.3 this client buffer size limitation has been removed, so that patch isn't required. Unfortunately, though, a bug was introduced in 5.3 that causes smbclient to get filenames that are short by one character (do a "dir" and you'll see what I mean). That shouldn't prevent you from connecting and fetching a file, though. This bug will be fixed in 5.3.2. (It only affects smbclient, by the way.)

Hope that helps, Matt

*** samba-2.0.3/source/include/client.h- Fri Feb 5 18:17:46 1999 --- samba-2.0.3/source/include/client.h Thu Apr 15 12:18:47 1999 *************** *** 27,33 **** /* the client asks for a smaller buffer to save ram and also to get more overlap on the wire. This size gives us a nice read/write size, which will be a multiple of the page size on almost any system */ ! #define CLI_BUFFER_SIZE (0x4400)

/* * These definitions depend on smb.h --- 27,33 ---- /* the client asks for a smaller buffer to save ram and also to get more overlap on the wire. This size gives us a nice read/write size, which will be a multiple of the page size on almost any system */ ! #define CLI_BUFFER_SIZE (0x2000)

/* * These definitions depend on smb.h