ClearOS release 7.4.0 (Final) Community here
I have a mixed environment of ~ 200 Linux, Win 7 pro and Win 10 pro machines in a Samba domain with LDAP backend (not Samba directory). The updated to Win10 1803 boxes show several oddities since Microsoft removed SMB v1 support.
The solution for these problems regarding to different sources on the web seem to be changes to smb.conf to force a newer protocol version. Since I don't know the dependencies of all the ClearOS apps among each other, here are my problems with two settings:
min protocol = SMB2
Win 7 Logon OK, network shares not available
Win 10, no logon possible
protocol = SMB 3
Samba doesn't start at all when restarting the service.
Before I mess any more with the install, does anybody of you guys have a solution to force SMB 2/3 without causing problems?
Thanks
MSTIBS
I have a mixed environment of ~ 200 Linux, Win 7 pro and Win 10 pro machines in a Samba domain with LDAP backend (not Samba directory). The updated to Win10 1803 boxes show several oddities since Microsoft removed SMB v1 support.
The solution for these problems regarding to different sources on the web seem to be changes to smb.conf to force a newer protocol version. Since I don't know the dependencies of all the ClearOS apps among each other, here are my problems with two settings:
min protocol = SMB2
Win 7 Logon OK, network shares not available
Win 10, no logon possible
protocol = SMB 3
Samba doesn't start at all when restarting the service.
Before I mess any more with the install, does anybody of you guys have a solution to force SMB 2/3 without causing problems?
Thanks
MSTIBS
Share this post:
Accepted Answer
That link is the latest news we have. 
I've no idea what the future of the ClearOS domain offering is for the moment, or of M$'s intent. It could be a bug on M$'s behalf as there has been no announcement, but they may not need to see the need for an announcement as SBS2003 went EoL four years ago.
I've no idea what the future of the ClearOS domain offering is for the moment, or of M$'s intent. It could be a bug on M$'s behalf as there has been no announcement, but they may not need to see the need for an announcement as SBS2003 went EoL four years ago. Responses (5)
-
Accepted Answer
I ran with SMB2 enabled in 6.x for a long time, but I suspect it didn't work with NT domains.
FWIW I think the upgrade to samba just rolling out through the community may obsolete the need for SMB1 to join NT domains and deprecates the "Allow Windows 10 Domain logons" parameter. It does not fix the issue of Win 10 v1803 no longer being able to join NT domains. -
Accepted Answer
-
Accepted Answer
Simple solution for ClearOS 6.0 (old yeah I know), Win10 doesn't support SMB1 out of the box but does SMB2. Edit /etc/samba/smb.conf, Under Global section add "protocol = SMB2", later down, comment out the line that points the port to 139 (put a # in front). Worked Win10 1803 Sept 2018.
To restart Samba and pick up the latest config:
/etc/init.d/smb stop
/etc/init.d/smb start -
Accepted Answer
https://sfj48-fkj200.heiksthsd.cf/clearfoundation/social/community/windows-10-issue-with-samba-domains-and-filesharing-in-clearos
is maybe the answer that the problem is in the works.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »