samba - Dec 2005 - Weird problem: cannot see files...

I've been trying to setup a samba server on my computer so that the
other Windows computers on my network can access the files on it.  I'm
running version 3.0.20 of sambe that came stock with Slackware 10.2. 
I've gotten it up and running with this simple smb.conf:
[global]
    workgroup = Mshome
    security = share
[downloads]
    path = /mnt/wind/downloads
    read only = yes
    guest ok = yes

My samba server and the downloads share show up under My Network
Places on the Windows computers, but when I try to access the share it
says access denied.  I can connect to the share using smbclient (on
the Linux box) and even get files, but ls and dir both give me the
following error:
NT_STATUS_ACCESS_DENIED listing \*

Here is what is in my log.smbd file for a session where I connect,
attempt to list the contents of the share, and then disconnect:
[2005/12/11 18:19:58, 0] smbd/server.c:main(802)
  smbd version 3.0.20 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2004
[2005/12/11 18:19:59, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2005/12/11 18:19:59, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2005/12/11 18:20:04, 1] smbd/service.c:make_connection_snum(662)
  127.0.0.1 (127.0.0.1) connect to service downloads initially as user
nobody (uid=99, gid=99) (pid 7146)
[2005/12/11 18:20:06, 1] smbd/service.c:close_cnum(835)
  127.0.0.1 (127.0.0.1) closed connection to service downloads

Anyone have any ideas what my problem is?

>   127.0.0.1 (127.0.0.1) connect to service downloads initially as user
> nobody (uid=99, gid=99) (pid 7146)
> 
> Anyone have any ideas what my problem is?
Without also seeing your smb.conf and filesystem permissions it's
difficult to tell for sure, however it seems from here that the user is
connecting as user 'nobody' which apparently doesn't have access to
the
share.  You'll either need to give 'nobody' access or connect as
another
user.

Also, make sure you don't have a 'map to guest' option in smb.conf
which
could be mapping the user to 'nobody' because of an incorrect username
or password.

Cheers,
Adam.