Koozali.org formerly Contribs.org

Lasdt updates and W10

Re: Lasdt updates and W10
« Reply #15 on: November 23, 2018, 10:50:21 PM »


[root@server2 ~]# rpm -qa | grep samba

samba-common-3.6.23-51.el6.x86_64
samba-client-3.6.23-51.el6.x86_64
e-smith-samba-2.4.0-26.el6.sme.noarch
samba-winbind-3.6.23-51.el6.x86_64
samba-winbind-clients-3.6.23-51.el6.x86_64
samba-3.6.23-51.el6.x86_64
[root@server2 ~]#
...

Offline ReetP

  • *
  • 2,726
Re: Lasdt updates and W10
« Reply #16 on: November 23, 2018, 11:12:11 PM »
Thanks. I'll revisit the bug.

Please keep an eye on this thread and add yourself to the bug.... be handy if you can help test things if we modify it.
...
1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions of software
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation

Online TerryF

  • grumpy old man
  • *
  • 1,268
Re: Lasdt updates and W10
« Reply #17 on: November 23, 2018, 11:21:38 PM »
Win10 Home PC
My Home server config and should also add fully updated

[root@fagehome ~]# rpm -qa | grep samb
samba-winbind-clients-3.6.23-51.el6.x86_64
e-smith-samba-2.4.0-26.el6.sme.noarch
samba-client-3.6.23-51.el6.x86_64
samba-common-3.6.23-51.el6.x86_64
samba-3.6.23-51.el6.x86_64
samba-winbind-3.6.23-51.el6.x86_64
[root@fagehome ~]#  config show smb
smb=service
    DeadTime=10080
    KeepVersions=disabled
    OpLocks=enabled
    OsLevel=35
    RecycleBin=disabled
    RoamingProfiles=no
    ServerName=FAGEHOME
    ServerRole=PDC
    ShadowCopy=disabled
    ShadowCount=10
    ShadowDir=/home/e-smith/files/.shadow
    UnixCharSet=UTF8
    UseClientDriver=no
    Workgroup=TF_SL
    status=enabled
--
qui scribit bis legit

Online TerryF

  • grumpy old man
  • *
  • 1,268
--
qui scribit bis legit

Online TerryF

  • grumpy old man
  • *
  • 1,268
Re: Lasdt updates and W10
« Reply #19 on: November 24, 2018, 12:08:11 AM »
OK,. further investigation:

SME9.2 clean install as at before last round of updates, all confs at default

[root@smei386 ~]# rpm -qa e-smith-samba
e-smith-samba-2.4.0-25.el6.sme.noarch

[root@smei386 ~]# config show smb
smb=service
    DeadTime=10080
    KeepVersions=disabled
    OpLocks=enabled
    OsLevel=35
    RecycleBin=disabled
    RoamingProfiles=no
    ServerName=smei386
    ServerRole=WS
    ShadowCount=10
    ShadowDir=/home/e-smith/files/.shadow
    UnixCharSet=UTF8
    UseClientDriver=yes
    Workgroup=sme-server
    status=enabled

Latest update applied to SME9.2 

[root@smei386 ~]# rpm -qa e-smith-samba
e-smith-samba-2.4.0-26.el6.sme.noarch

[root@smei386 ~]# config show smb
smb=service
    DeadTime=10080
    KeepVersions=disabled
    OpLocks=enabled
    OsLevel=35
    RecycleBin=disabled
    RoamingProfiles=no
    ServerName=smei386
    ServerRole=WS
    ShadowCount=10
    ShadowDir=/home/e-smith/files/.shadow
    UnixCharSet=UTF8
    UseClientDriver=yes
    Workgroup=sme-server
    status=enabled
--
qui scribit bis legit

Offline ReetP

  • *
  • 2,726
Re: Lasdt updates and W10
« Reply #20 on: November 24, 2018, 01:04:53 AM »
I think the MaxProtocol options may have been added whilst trying to get around the Win 10 issues originally.

They may have originally been ignored, but the updated rpm then took them into account.

That then advised Win 10 that other protocols (SMB V1/2 over NT1) were enabled and somewhere that caused an issue.

Removing smb2 (which I think should be SMB2 but needs checking with testparm) put it back to NT1 and sanity was restored.

That's my guess anyways.....

Need to see smb.conf before and after to really know.

The remaining question is why did it fail if SMB1/2 was installed on the clients?

Assuming I have this about correct....

Terry, can we go back on the bug and test a little more?
...
1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions of software
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation

Online TerryF

  • grumpy old man
  • *
  • 1,268
Re: Lasdt updates and W10
« Reply #21 on: November 24, 2018, 05:06:55 AM »
ClientMaxProtocol=smb2
ServerMaxProtocol=smb2

These two settings were suggested as possible solutions to the ongoing issue with samba shares and windows 10 from the windows updates in late 2017 and early 2018 that borked win10.

I tried them and plenty of others :-) the above didn't work and I removed them from my smb.conf

If you read the bug quoted the latest update actually fixed a misnamed config entry that enforced the above settings IF they were present.

However they had to be present and the only way for them to be present was for them to have been added manually with, notice the case, lowercase is/was not correct:
config setprop smb ServerMaxProtocol SMB2
config setprop smb ClientMaxProtocol SMB2

The latest update does what its supposed to do, enforces the smb settings :-)

and as to what Mister MS does, mate win10 users, me, have just spent almost 12 months chasing updates to fix an issue that Mr MS introduced with one of his feature updates late last year :-) it has only been the most recent one that has returned the functionality that we already had !!!

Added after hitting enter: They are valid smb.conf settings for any app that needs those protocols
« Last Edit: November 24, 2018, 05:08:28 AM by TerryF »
--
qui scribit bis legit

Offline CmdLn

Re: Lasdt updates and W10
« Reply #22 on: July 17, 2020, 11:59:25 AM »
Either W10 update 1903, 1909 or both break this again, but can be fixed by also adding port 445 to samba like this
Code: [Select]
config setprop smb SMBPorts 139,445

Online TerryF

  • grumpy old man
  • *
  • 1,268
Re: Lasdt updates and W10
« Reply #23 on: July 17, 2020, 12:27:03 PM »
--
qui scribit bis legit

Online TerryF

  • grumpy old man
  • *
  • 1,268
Re: Lasdt updates and W10
« Reply #24 on: July 17, 2020, 12:48:57 PM »
Just adding to have a good look through the bugs, plenty of info for bothe sme9 and sme10, when smb1 is dropped from windows you lose ability to browse for a linux share in windows explorer and the listing of same under Network.

There has been work done by ReetP and a tweak or two by JPP on a package incororating the work done here - https://github.com/christgau/wsdd - this enables the display of linux resource/share and browsing of same once again using the wsdd Discovery Method and not netbios which is disabled with the dumping of smb1, This may be making its debut as a contrib soon.
--
qui scribit bis legit

Offline Jean-Philippe Pialasse

  • *
  • 1,515
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Lasdt updates and W10
« Reply #25 on: July 17, 2020, 10:28:41 PM »
by having max protocol set you change samba behaviour from max nt1 (=smb1) to allow smb2. windows 10 then try to connect to higher available. which is smb2. negociate it using netbios port then communicate on 445.

if samba is not allowed to communicate on this port in its config then connexion fails.


a patch is coming around for that, but as pointed above if you want you can force the port.