We have a feeling at O'Reilly that Appendices C (Samba config options) and D (utilities) of Using Samba would make a useful pocket reference. So I've incorporated all (I think) the corrections and changes for 2.0.7 that all of you provided into these appendices and have turned them into a small book of their own.

Who would like to see these appendices in their current form, along with the little preface I wrote? I'd be happy to release the preface (which is mainly a few passages stolen from the preface and Chapter 1 of Using Samba) to the team, if anybody thinks it would be useful. But mainly, I need people to do a sanity check for O'Reilly's sake, a check that I've gotten the appendices up to date and that I don't say anything embarrassing in the preface.

For me, the easiest way to get you these pages is to send them as PDF or PostScript files; I imagine they'll add up to about 75 pages. But if you're in North America and would like a hard-copy, I can get you one.

I have added the codepages for Turkish support to samba. I'd like to submit it to the Samba group for inclusion in samba.

Where do I send the stuff into?

Here is a brief explanation of what I have currently:

CPISO8559-9.TXT for compiling unicode_map.ISO-8859-9 CP857.TXT for compiling unicode_map.857 codepage_def.857 for compiling codepage.857 patch file for charcnv.c to support client code page 857 and character set ISO8559-9. (based on 2.0.7 samba)

All of the above can be found on http://www.arayan.com/da/linux.html

I was wondering if something has happened with support for dos clients in samba 2.2? I have a samba 2.2 PDC setup on my network providing authentication to other samba 2.2 servers. I have a floppy setup for disk imaging which is using dos tcp/ip and win3.11 network drivers to map a drive to my Linux raid machine. When the floppy is fully booted and logged onto the network I do a directory listing and no files or directory's show up, even though while in the shared path on the linux box there are several files/dir's there. I checked to see if the map hidden was set in the smb.conf file and it was not. So needless to say I am stumped on this one.

So, I have the same problem. Long time I try get help from samba guys, but no answer... (

I resolve this problem. I think so.

Edit file /source/smbd/dir.c

Find function:

I have just applied some more patches to libsmbclient.

These are:

1. Changes to the interface (I am sorry) to:

- add an smbc_readdir call (not tested)

- change the auth_fn to provide the buffers for workgroup, username and password from the library and provide the current suggested values so the client can display them or use them to retrieve cached info and avoid asking the user for this info ...

2. Many fixes to bugs in the old and new code

3. More code in tree.c that puts up two panes, one for the tree of objects that can be seen/retrieved, as well as a list window that can show file info if you click on a node in the tree.

This last program still has many bugs and defficiencies, but it suffices to allow me to test things quickly.

I have the following outstanding fixes to apply at some stage:

1. Cache NetBIOS name lookups for a period of time to avoid excessive delays in browsing directory entries

2. Handle systems with multiple interfaces

3. Have a directory and file cache

4. Allow multple shares to use the one TCP connection to server

5. etc

One of the big problem I still have is that fact that the current libsmb cli_ routines on files and enumeration of servers etc are all callback based and return all the information (in a directory, for example) all in one go.

This forces me to build a list of all the available info all in smbc_opendir call. I would rather get the info needed as the user makes calls to smbc_readdir and smbc_getdents ... Although that presents some problems as well.

OK, I have found the real problem, as well as others ... :-)

I did not have the codepage stuff initialized, so in trying to convert a UNICODE string to a UNIX string, I was indexing through a NULL pointer ... Unfortunately, I have also found that Win2K times out TCP connections, so I have to think about reconnect ...