Samba Issues With Win 10

Home » CentOS » Samba Issues With Win 10
CentOS 9 Comments

Hi, folks,

Just ran into a problem: someone with a new laptop, running Win 10, version 1709, tried to map their home directory (served from a CentOS
6.9 box, and it fails, with Windows complaining that it no longer supports SMBv1, and if you go to their site, you can install support for that manually….

The server running samba can *not* be updated to 7 – we have a lot of stuff based off it, and most of our users use it, one way or another, so it’s a major thing when we do finally upgrade (or, more likely, replace the server).

Has anyone run into this, and if so, any workarounds on the Linux end?

mark

9 thoughts on - Samba Issues With Win 10

  • Walter H. wrote:
    Our desktop support person found that, but as I said, it is apparently a manual install for desktop support. And is it the case that, although we’ve shut off the lower level of security on samba on CentOS 6, that it’s still smbv1?

    Are there any updates? Is there something in, say, the SCL that might support smbv2, or is there some way to configure the regular smb to support v2?

    mark

  • I fail to understand what’s the problem you are having. I say that smbv1
    can be re/added to Win10 and I think there is a few pages on that on the net, so is it that Win10 is still not working after addition of smbv1?

  • assuming from my experience with sles11 and windows 10, putting

    min protocol = SMB2
    max protocol = SMB2

    in the [global] section of your smb.conf should solve your issue.

    best regards Ulf

  • FWIW, with CentOS-7 and windows 10, I was finally able to map a Linux directory to a windows drive, successfully. Problem was selinux, which I proved by temporarily disabling it (setenforce 0). Doing
    “setsebool -P samba_enable_home_dirs 1” then reenabling selinux
    (setenforce 1) seems to have fixed it. at least for now.

    BTW, I also have max and min smb versions set to 3_11 in my smb.conf and it all still seems to work.

    With 6.9 some of the values/settings may need to be different, but one thing to check when remote stuff doesn’t work, and you’ve checked everything else, is to try with setenforce 0. If it suddenly miraculously works, then its a selinux issue.

  • DO not do that is you care at all about security!!

    You did not say what version of samba you are running but I am going to assume it is not the samba4 rpms that come with c-6.

    I would suggest that you remove the currently installed samba rpms and install samba4-4.2.10-12.el6_9.x86_64 and friends.

    I have several customers still running c-6 with the samba4 rpms using win10 and win server 2016 that work just fine and best of all no smb_1

    Regards,

  • me@tdiehl.org wrote:

    The default samba, 3.6.23-51. The real issue, which you may have missed, is that this is *heavily* used by the entire Office. Such an upgrade would require extensive testing before we can roll it out. By the time we do that, we may have finally ordered a replacement server for the system, and the new one will be C7.

    This isn’t a cube farm, but 30 or 50 or 60 people being out of capability for hours or days is not something we do.

    mark

  • I did not miss it. I seem to remember that you asked for something in SCL. If you are willing to use SCL then why not use packages supplied in base?

    If you are not willing to do the testing then your only choice is NO SECURITY. SMB_1 is not secure and should not be used. That is why it is no longer supported in Win 10 or samba 3.x. For once MS is doing the right thing.

    It is not an intrusive change but I agree it should be tested.

    Bottom line is it is your system so you get to decide. :-)

    Regards,