You have file level permissions and share level permissions. The file level permissions apply to the Linux user and the share level permissions apply to the Samba user. I suspect that you have the correct Samba (share) permissions but not the Linux user (file) permissions. That is why you can see the shares but not actually do anything with them. The other possibility is that the user only has read (Samba) permission and not read/write.

I'm not very familiar with Extplorer but I suspect that the TKL fileserver uses Samba users with the Extplorer program. By default it should be set up to sync Linux & Samba users, but for good measure I usually manually sync them - on the Samba page in Webmin there's a button "Sync Linux & Samba users" (or something similar). While you're in Webmin-Samba go into the share and ensure the user is added as having read/write access. Then go back to the main Webmin Samba page and "restart Samba". Now still in Webmin, also go to the Users (Linux users that is) and add your user to the smbusers group.

If all those things are right it should work. Sorry if my instructions aren't very clear. Please ask for more details if there's something you don't understand or doesn't make sense. Good luck!

It seems that my initial suspicions were incorrect. Sorry that I lead you astray.

eXtplorer does not use Linux or Samba users, it has its own separate user database. So eXplorer users are completely separate again and must be added/edited separately (and unfortunately manually). I've done a bit of a writeup on another thread, have a read over here. You may wish to read the previous post (that I was replying to) to get the context of some of my comments.

Hope thats helpful (or at least more helpful than my initial comments).

Hey folks, sorry for the late reply. We are in the middle of a development cycle, and I am putting the Core Lucid beta through final testing before release, so I haven't been around the forums much.

I just wanted to say that the fileserver (and domain-controller) appliances with eXtplorer include the vsftpd binded to localhost to provide net2ftp backend. You'll notice it is one of the connection methods available when logging into eXtplorer.

When connecting via net2ftp, it provides users access to their home directories, as well as workarounds permission issues with eXtplorer.

This is actually documented on the appliance page, maybe we should emphasize it more.

Hope the above helps.