I'm running OpenSuse 10.3 and trying to use a NAS drive (bought from SmallDrives http://www.smalldrives.com/), The drive knows about Samba and FTP

My problems are

(1) I've been unable to mount the drive using CIFS.

In fstab I have
//<drive>/<share> /mnt/<point> cifs username=<me>,password=<mine>

attempting to mount gets me
"mount error 5 = Input/output error
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)"

I've tried variations on this theme but all with the same effect.

(2) Possible character-set problems with LFTP

As FTP seemed to be working I thought I would try using lftp to mirror my laptop to the drive. It seems to get a little confused with any files containing an accented character. It manages to copy the files,but on subsequent runs it attempts to copy them again, as if it wasn't recognising that they already existed. The error I get are like the following:

---> DELE <filename with odd character>
<--- 550 Requested action not taken.
rm: 550 Requested action not taken. (<filename with odd character>)

I've tried different character set options in .lftprc in case that might help, but to no avail.

I've checked the files by accessing the drive via konqueror (smb://<user>@<server>) and there are files with accented characters in their names - so they are being copied. All of these create errors on subsequent runs of lftp because it tries to copy them again.

I'd appreciate any suggestions on either of these problems.

Many thanks,

'o-Dzin

With network appliances it's a good idea to ensure that you are running the latest firmware - the original version of any firmware will have bugs, and the vendor will hopefully have fixed them with newer releases. If the vendor is not releasing new firmware versions it's actually a bad sign, as it means that they aren't maintaining it.

WRT the Samba problem, I'd recommend testing with the smbclient command-line utility - it works like a command-line FTP client but is specifically for SMB/CIFS, and is highly reliable. I think that if it doesn't work the debug options will help you find out why.

The command

smbclient -I <ip address> -W WORKGROUP //STORAGE-AEC9/<share>

works with no problems

Try specifying the device by IP address in your fstab, ad see what happens. If there is currently a name resolution problem somewhere then using the IP address will circumvent it.