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
On 28.06.2018 16:30, mark wrote:> 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 > >the solution is to enable SMBv1 in Win10 ... look for this in the Knowledge-Base of Microsoft https://support.microsoft.com/en-sg/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and
Walter H. wrote:> On 28.06.2018 16:30, mark wrote: > >> 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? >> >> > the solution is to enable SMBv1 in Win10 ... look for this in the > Knowledge-Base of Microsoft > > https://support.microsoft.com/en-sg/help/2696547/how-to-detect-enable-and > -disable-smbv1-smbv2-and-smbv3-in-windows-and >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
On 28/06/18 15:30, mark wrote:> 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....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?> 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 > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos
On 06/28/2018 10:35 AM, mark wrote:> 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 > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >I ran into this as well. There is a procedure that a W10 administrator can enable SMBv1. I did it and it worked. I believe that I started from this link: https://social.technet.microsoft.com/Forums/windows/en-US/8160d62b-0f5d-48a3-9fe9-5cd319837917/how-te-reenable-smb1-in-windows1o?forum=win10itprogeneral HTH -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.wells at leidos.com
mark
2018-Jun-28 16:50 UTC
[CentOS] EXTERNAL: Samba issues with Win 10 (one last followup)
Wells, Roger K. wrote:> On 06/28/2018 10:35 AM, mark wrote: >> >> 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? >> > I ran into this as well. > There is a procedure that a W10 administrator can enable SMBv1. > I did it and it worked. > I believe that I started from this link: > https://social.technet.microsoft.com/Forums/windows/en-US/8160d62b-0f5d-48 > a3-9fe9-5cd319837917/how-te-reenable-smb1-in-windows1o?forum=win10itproge > neral HTH >Yeah. I'm not sure why my original problem statement wasn't clear, and I've done some online research since then, but what I was looking for was a CentOS 6 solution, where we just modified the C6 samba server, rather than have to put a ticket in for each and every user that's stuck with Win 10. And, since this is an office in a US federal gov't agency (civilian sector, so budgets suck), there could be a dozen or two people, and I understand we're getting in new laptops & desktops for a number of folks with older systems, we're going to see more of this, and it's a big issue, since the server that serves samba also does a lot else, and that will affect almost everyone. That's why a C6 solution would have been far better. But I see that the cifs.ko with the C6 kernel doesn't support smbv2, so that's what we'll have to do. (And, since the samba server is now out of warranty, it's time to start thinking about a replacement). mark
On 28.06.2018 16:30, mark wrote:> 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....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
On 06/28/2018 07:30 AM, mark wrote:> 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....https://wiki.samba.org/index.php/Samba_3.6_Features_added/changed#SMB2_support
On Thu, Jun 28, 2018 at 06:55:21PM -0700, Gordon Messmer wrote:> On 06/28/2018 07:30 AM, mark wrote: > > 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.... > > https://wiki.samba.org/index.php/Samba_3.6_Features_added/changed#SMB2_supportFWIW, 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. -- ---- Fred Smith -- fredex at fcshome.stoneham.ma.us ----------------------------- "And he will be called Wonderful Counselor, Mighty God, Everlasting Father, Prince of Peace. Of the increase of his government there will be no end. He will reign on David's throne and over his kingdom, establishing and upholding it with justice and righteousness from that time on and forever." ------------------------------- Isaiah 9:7 (niv) ------------------------------