Announcement

Collapse
No announcement yet.

Samba 4.11 Aims To Be Scalable To 100,000+ Users

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ermo
    replied
    I'll start by noting that "man 5 smb.conf" is your friend, but to cut a long story short, I'd try with:

    Code:
    server min protocol = SMB2
    and ensure that auth and smb protocol negotiation logging is enabled with something like:

    Code:
    log level = 1 auth:3 smb:3 smb2:3
    Then just keep an eye on the logs for the connecting host to see what's going on?

    Leave a comment:


  • Dedobot
    replied
    Win7 = smb2.1
    Me thinks Sun/Oracle's have better approach: don't invent, just strictly follow MS.
    Solaris 11.4's SMB server (3.1=win 2016) is a blazing fast.
    ‚Äč

    Leave a comment:


  • birdie
    replied
    Originally posted by schmidtbag View Post
    Have you tried setting the min protocol to SMB1?
    https://www.samba.org/samba/docs/cur...ENTMINPROTOCOL
    I don't want to degrade security that much. Of course it works. And SMB1 is dead for all intents and purposes.

    Also, discard my requirement about Windows XP. I stopped using it years ago. So, I need compatibility only with Windows 7 - 10LTSC.

    Leave a comment:


  • boxie
    replied
    Originally posted by schmidtbag View Post
    Have you tried setting the min protocol to SMB1?
    https://www.samba.org/samba/docs/cur...ENTMINPROTOCOL
    please don't do that... SMB1 should not be enabled in any way shape or form

    Leave a comment:


  • schmidtbag
    replied
    Originally posted by birdie View Post
    Since lots of talented Open Source engineers read Phoronix, I'm gonna ask this question: what options need to be enabled for Samba to be accessible both for old clients (say Windows XP, 7) and Windows 10 LTSC in light of this new feature/requirement?

    Currently for all Windows 10 clients I have to enable Computer configuration\administrative templates\network\Lanman Workstation ->"Enable insecure guest logons" in GPO but I don't like it.

    My Samba configuration looks like this:

    Code:
    [global]
    security = user
    guest account = nobody
    map to guest = Bad User
    Have you tried setting the min protocol to SMB1?
    https://www.samba.org/samba/docs/cur...ENTMINPROTOCOL

    Leave a comment:


  • birdie
    replied
    Since lots of talented Open Source engineers read Phoronix, I'm gonna ask this question: what options need to be enabled for Samba to be accessible both for old clients (say Windows [strike]XP[/strike], 7) and Windows 10 LTSC in light of this new feature/requirement?

    Currently for all Windows 10 clients I have to enable Computer configuration\administrative templates\network\Lanman Workstation ->"Enable insecure guest logons" in GPO but I don't like it.

    My Samba configuration looks like this:

    Code:
    [global]
        security = user
        guest account = nobody
        map to guest = Bad User
    Last edited by birdie; 04 July 2019, 11:31 AM.

    Leave a comment:


  • phoronix
    started a topic Samba 4.11 Aims To Be Scalable To 100,000+ Users

    Samba 4.11 Aims To Be Scalable To 100,000+ Users

    Phoronix: Samba 4.11 Aims To Be Scalable To 100,000+ Users

    For those using Samba for better Windows interoperability with SMB/CIFS/AD, the forthcoming Samba 4.11 will be a lot more scalable so it can be used within massive organizations...

    http://www.phoronix.com/scan.php?pag...-4.11-Features
Working...
X