Okay, So I've replaced ubuntu on my desktop with antix-m8 and I can no longer access my samba share using the same smb.conf configuration i was using in ubuntu.

I've followed the instructions here:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/access-shares-via-samba-fuse-t634.html"
linktext was:"antix.freeforu ms.org/access-shar ... -t634.html"
====================================
" onclick="window.open(this.href);return false

tried using both fusesmb and smbnetfs.

When i try to run either of these (ie"sudo fusesmb /media/Iomega_HDD" style) I get a message saying use the nonempty option, and when i run it with the nonempty option it gives me this:

fuse: bad mount point `/media/Iomega_HDD': Permission denied

I've set up the ~/.icewm/startup file to contain the code"fusesmb -o nonempty /media/Iomega_HDD" ... maybe it's preventing me from doing it at the command line? or maybe it fails with the same error at startup?

This laptop was able to mount my share easily when i ran ubuntu, and can still mount it when i boot my desktop into windows, but since i've switched to antiX it's giving me the following error:

CIFS VFS: cifs_mount failed w/return code = -6

Then it tells me error 6: no such file or directory and to check the man page for mount.cifs, which was no help; and it WAS telling me permission denied.

So I ran"smbpasswd -a indubitableness" and picked a password, at which point it stopped telling me permission denied.

This is the command I'm using:

sudo mount -t smbfs -o user=indubitableness,password=passwd //192.168.0.xx/media/Iomega_HDD /media/iomega

of course that's not the password i'm using, but the rest of it's pretty much exact. Like i said this command works fine with windows running and it used to work perfectly in ubuntu. My smb.conf share folder section looks like this:

[MyFiles]
path = /media/Iomega_HDD
browseable = yes
read only = yes
guest ok = yes
create mask = 0644
directory mask = 0755
force user = indubitableness
force group = indubitableness

I figured this is a problem with samba, and I was trying to avoid posting here for a while, but I can't find anything that's helped me even get a clue as to what might be going on.

Ok, a couple of things.

1. There is a bug in smbclient. It has been this way for a while, so connecting can be a little flakey at times. There seems to be some time out errors.

2. Forget about sudo.

3. Fuse should be run as a user not root. So"fusesmb /path/to/mount/point". The mount point must already exist.

4. Forget about sudo.

5. To unmount run fusermount -u /path/to/mount/point

6. Forget about sudo