I have a Slackware 14.0 box, and a Slackware 14.1 box. They both use identical smb.conf files as follows:

Both of them have an identical public account.

Mounting the 14.0 share works fine. Mounting the 14.1 share gives "mount error(13): Permission denied"

What am I missing? What was changed with Slackware 14.1 or the version of samba that comes with it that I can no longer mount this share?

I notice that the log for the 14.1 box shows that security=share is no longer supported, as is acl comptibility, and max protocol=NT is no longer valid either.

The 14.0 box logs only complain about max protocol=NT.

I'm guessing that samba has been changed, and the way I've shared my stuff for years and years no longer works?


Edit: changing security=share to:

security = user
map to guest = Bad User

lets me mount the share, but now I'm unable to make them writable. One step forward....

This has been discussed here

I saw that, but changing security mode did not fix all of the problems. My once read/write share is now read only, and I can no longer mount password protected shares

And to make it really interesting....I can no longer connect from my windows machines. Bloody hell, this worked great (and still does) with 14.0. So now I have to either spend bloody hours trying to figure out how to get the latest and greatest samba do what the old one did...or revert to Slack 14.0. I feel like I'm missing something fundamental, this should not be so difficult and time consuming. I'll have to return to this later because I don't have any more time to waste on this. I think for now I'm going to revert to 14.0 with the older samba, and work on the upgrade when I have more time to get things working <sigh>...

Have you tested the "map to guest" option?

To make them writeable, use "writeable = yes"

Greetings Ook.

I too have the same issues you brought up. My fix if it can be called that, is to remove Samba version 4.1.4 on Slackware 14.1 and install Samba 3.6.8 from an earlier version of Slackware and it works just fine.

I have spent a lot of time with 4.1.4 and have given up until I learn more.

Good luck to you.

Let me make sure I understand. I have slackware 14.1, patched to whatever the current 14.1 patches are, including the 3.10.x kernel. I have discovered that with this version I cannot even get my Samba shares to mount. I used to use -o sec=ntlm to get them to mount, but not even that works with the latest version. No matter what I do, I can not mount any shares anymore. On my boxes with the older versions it still works just fine.

And I can fix my Samba hell problems by simply using an older version of Samba?

At this point I'm trying to understand how something that worked so well was changed to basically not work at all. I don't know what I'm missing, but I have yet to find someone that can explain what I'm doing wrong, and why it is that what I've been doing for years no longer works. I'm about to scrap Samba for good.

Does anyone have Samba working with the 3.10.x kernel? Would you be willing to share your config?

OK, so I removed Samba 4.1.x and installed Samba 3.6.8 from the slackware 14.0 packages. IT WORKS!!!!!!!

What in the name of deity did they do the 4.1.x that people like us can't get it to work?

My windows 8 box couldn't connect to slackware 64 14.1 samba 4.1.4 secured share. I found this works now, no problem with guest shares.

I recently upgraded my media server to Slackware64 14.1, which uses Samba shares to make my local content available to different devices around the house. I can connect to these shares from my laptop which is running Slackware64 14.1 and Windows 7 x64 Ultimate (it works from both systems), as well as my XBMC and WDTV Live. I didn't have to downgrade Samba or do anything out of the ordinary, it all worked just as it did before.

Unfortunately I can't offer any ideas about what may be causing your problem, but I will say that my setup is extremely simple, so maybe there's an issue with a particular option or combination of options?

Would you be willing to share your smb.conf file? For all I know it is a simple setting causing all the problem.

Alas, I'm going linux to linux. I don't use Windows anymore. Interesting enough, I had a Windows 7 box a year or so ago, and I could not connect to its shared drives - at all. Just could not get it to work, never found out why. An identical box sitting next to it worked fine. I have since wiped them both and put linux on them. At least when Linux does not work, it consistently doesn't work LOL.

How about sshfs? Just tried your particular example (well, near enough - I have a seperate disk mounted as /backup).
With sshfs I mounted the root filesystem on /mnt/hd, and all was there under /mnt/hd/backup

Less hassle ...

I have only ever used samba to facilitate sharing between qemu guests and hosts -- so I know next to nothing about samba. However there is a fair amount of slightly old information about setting this up and I have just copied their host samba configs and it has worked just fine...until slackware 14.1 (more precisely the new samba 4.x in it).

I came across this debian patch which points out quite clearly what the problem is, and this may interest people who find this thread through a search:

https://bugs.debian.org/cgi-bin/bugr...cgi?bug=727756

Knowing very little about samba I can't quickly see if this is basically the same as what was dicussed in the thread referred to by willys above. If it contains nothing new, apologies, I just thought it might be of interest.

Michael