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 ofstuff 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-di...
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 Thu, 28 Jun 2018, mark wrote:
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
DO not do that is you care at all about security!!
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?
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:
On Thu, 28 Jun 2018, mark wrote:
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?
<snip>
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.
The default samba, 3.6.23-51.
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
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
On Tue, 3 Jul 2018, mark wrote:
me@tdiehl.org wrote:
On Thu, 28 Jun 2018, mark wrote:
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?
<snip> > 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.
The default samba, 3.6.23-51.
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
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.
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.
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.
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,
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 ofstuff 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@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@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... HTH
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 06/28/2018 12:50 PM, mark wrote:
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
Yeah, I thought that might be the case, sorry. Here we are planning to upgrade the our server to CentOS 7.5 shortly
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On Thu, Jun 28, 2018 at 12:50:06PM -0400, mark wrote:
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.
Trouble is that smb v1 is horribly insecure. Even Microsoft tells people not to use it.
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.
I'd think the feds would have figured out that smb v1 is a bad protocol to use and outlawed it.
That's why a C6 solution would have been far better.
But I see that the cifs.ko with the C6 kernel doesn 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).
At home, while I do not have win10 talking directly to samba on my LInux desktop, I also have a Synology Disk Station and have configured it to use only smb v3, and in the mount command on Linux I specify smb v3, and it works fine.
'course, that's the samba client, not the server. I haven't really investigated why I can't directly access win10 from linux and vice- versa, so it may be a v1 vs v3 issue. However, at work I had no trouble accessing my home filesystem on linux from win10. haven't, so far, figured out what the difference is.
Fred
Fred Smith wrote:
On Thu, Jun 28, 2018 at 12:50:06PM -0400, mark wrote:
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....
Trouble is that smb v1 is horribly insecure. Even Microsoft tells people not to use it.
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.
I'd think the feds would have figured out that smb v1 is a bad protocol to use and outlawed it.
<snip>
ROTFLMAO!
I know that there are folks who are running Windows XP... but those are *not* on the open network, and have to have an internal firewall... but they run software controlling machines that cost many millions of dollars, and are still doing very good and useful work.
We're just slowly rolling out C7 (AND we have to encrypt it all, as we do). But there's no budget to disrupt all the work everyone's doing. Hell, staffing here is down about a third or more in the almost nine years I've been here. But then, who needs to spend money on science, I mean, really?
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_suppo...
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_suppo...
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.
-
Fred Smith -
Gordon Messmer -
lejeczek -
mark -
me＠tdiehl.org -
Ulf Volmer -
Walter H. -
Wells, Roger K.