Hi All,

I followed the instructions in http://maemo.org/community/wiki/HowToAccessWindowsCIFS and got fanoush's cifs.ko file (http://handhelds.org/~fanoush/maemo/...06.51-6.tar.gz - it says it is for the second IT 2007 release). But, I just can't mount a share!

I tried passworded and non-passworded (guest) shares from two different computers. None could be mounted. What worries me is that it gives me the same message even if I put in a dud ip address for the share. So the problem could be on a more fundamental level.

If I don't provide any options with -o when mounting, it just says something like:

If I do provide domain(workgroup), user and password using the -o option to mount, it says that share is read-only and then just shows the above message.

The shares themselves are fine, as I can mount them from both, linux and windows computers.

I think the cifs module loads fine as I can see it with lsmod, remove it with rmmod and reload it again.

Anyone got an idea of what I'm doing wrong? Do I need another version of the cifs.ko module?

cheers

P.S.
- I'm using "sudo gainroot" to become root.
- The mount directories do exist.
- The computers witht cifs/samba shares are accessible. I can ping them.
- The samba ports are not blocked.

While I hadn't done this before, I gave it a try and here's what worked. I've got a Buffalo Linkstation Pro, running Samba. On it I've got a share called "pictures". As I couldn't remember what the guest account was I mounted the share using root. (This is from a SSH session running on my PC to the N800, logged in as root)

obviously, the asterisks were replace with my password.

Now on the N800, running File Manager, I can see the "s1_pictures" directory inside of "documents" and it shows everything on my server.

Hope this helps.

Thanks for the reply.

I sorted it though. SSHed into the N800 and typed in my password. Turns out I don't know what my password is, unless I type it in on a conventional keyboard! I was getting some of the characters wrong. (Also, it was stupid of me for having my actual password as my samba password too)

Still surprised that the samba guest account doesn't work though using the following:
<code>-o guest</code>

Also, couldn't get it working through fstab, but I'll have another bash at it later.

Thanks for the sshd tip though. Otherwise I probably would've tapped in my incorrect password on it a few more times, before starting to bash it with something heavier and harder!

:-)