• [6.11] No more "private" SMB access possible from different devices (Windows, Android, Printer)


    D.Romeleitis
    • Urgent

    Hi, 

     

    I read a lot in the other threads, but no possible solution worked for my Windowssystem and I haven't found anything my my other machines. 

    With 6.10.3 everything was fine. Like I read the kernel support of SMB1 was deleted. 

    Actual situation:

    With share set to "Private" I can't access the shares. Error message "You don't have access rights" or "The local device name is used. Connection can't be established". 

    It doesn't matter which setting I use on WIndows in security options -> LAN Manager authentication level. I tried everything. Error messages are different then, but no access. 

    With Android I am using Total Commander. In the settings it doesn't matter if I am using SMB1, 2 or 3. I get "Access denied". Same for my Multi Function Printer where I can scan directly to a SMB share... 

    When I change to "Secure" I get back access, but even if my user is set to "read/write" I only have read access. 

    Please find a solution in Unraid itself (Patch/Setting) so that I can use my devices again. 

     

    Kind regards, 

     

    Daniel




    User Feedback

    Recommended Comments

    Start by going through this thread very carefully:

         https://forums.unraid.net/topic/128875-smb-private-readwrite-working-just-cant-paste-folders-only-files       

     

     

    Make sure that you have read the first post (and the PDF file) in this thread about windows issues:

           

            https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/

     

    Edited by Frank1940
    Link to comment

    I don't understand what I should change exactly.

    When I open the console and open /mnt/user I see my shares.

    Most of them have User "nobody" and group "users".

    One share has my User as Users and group "Users", too.

    I created a "play-share"

    drwxrwxrwx  1 nobody                    users     6 Oct  2 21:49 TestSMB/

     

    I still have no access to that share when I set it to "secure".

    Do I have to change user or group on the sharedirectory to get access?

     

    Next test :

    I added 

    force create mode = 0666
    force directory mode = 0777

    to Settings -> SMB -> SMB Extra configuration

     

    Then I added another share and set it to "secure" and my User to "read/write".

    Still no access. Neither with Windows, nor with Android...

     

    Next test :

    Deactivated "Netbios" in SMB-Settings. Didn't changed anything...

    Edited by D.Romeleitis
    Link to comment

    One step in the right direction.

    I created a new user "test" with password "Test".

    Then changed SMB Security to "Private" and gave the User "test" Read/Write access.

    Now I have access and can read &write, when I use this user & password.

    My normal User is my email address with @-Char and .-Char.

    The password has characters, numbers and a "."

    This seems to be a problem for Unraid 6.11 with SMB2.

    The combination never was a problem before... Can I change anything so that my normal user & password will work again?

    Link to comment

    OK, Windows and Android are now running with the workaround of the new user & password.

    Does anybody know how to get my printer (EPSON WorkForce Pro WF-4745) working?

    There is no "use SMB2" option. Can't find in the specs if it is only supporting SMB1. But I can't imagine. It's not a cheap or an old printer...

    Link to comment

    If you read what it says, there is a difference in behavior between

     

    'min protocol = SMBv2_02'

                and

    'min protocol = SMB2'

     

    (The parameter 'SMB2' -- or there is no 'min protocol' parameter specified--- actually means that only SMBv2.10 and above is supported! IF you want to use an older protocol than SMBv2.10, you must actually specify that one.)

     

    EDIT:  No guarantee that 2.02 will work but it is probably the last possibility...

     

    EDIT2:  I just looked up the EPSON WorkForce Pro WF-4745 and it a relatively new printer (~2018).  I thought it might be one from prior to 2010.  Not sure what the problem is.  And what does Unraid have to do with this printer?  Unraid does not have provision for mounting any printers...

    Edited by Frank1940
    Link to comment

    Add this to "Settings/SMB/SMB Extras/Samba extra configuration"

     

    ntlm auth = Yes

     

    Please report back if this solves connectivity issues.

    Link to comment
    14 hours ago, limetech said:

    Add this to "Settings/SMB/SMB Extras/Samba extra configuration"

     

    ntlm auth = Yes

     

    Please report back if this solves connectivity issues.

    I tried this NTML and the above SMB version setup.  I tried each by themselves, and together, nothing made any difference... my user with an @ sign don't work, I still get prompted to log in by windows whne accessing share.  If I type in my user without na @ in the username, it works, even if I type the @ user/pass out it does not work.  This is how I'm supposed to enter those right?+

     

    image.thumb.png.72ee6a945d322a767597a8bad0dfe3be.png

    Link to comment
    1 hour ago, onyxdrew said:

    I tried this NTML and the above SMB version setup.  I tried each by themselves, and together, nothing made any difference... my user with an @ sign don't work, I still get prompted to log in by windows whne accessing share.  If I type in my user without na @ in the username, it works, even if I type the @ user/pass out it does not work.  This is how I'm supposed to enter those right?+

     

    image.thumb.png.72ee6a945d322a767597a8bad0dfe3be.png

     

    Change

    #ntlm_auth = Yes

    to

    ntlm_auth = Yes

     

    The # character means it's a comment.

     

    What do you mean by "my user with an @ sign"?

    Link to comment

    The problem with permitting access to shares occurs when your username is your email address. With Windows you normally login with your (Microsoft) email address. Since 6.11 this is a problem. 

    Link to comment
    8 minutes ago, D.Romeleitis said:

    The problem with permitting access to shares occurs when your username is your email address. With Windows you normally login with your (Microsoft) email address. Since 6.11 this is a problem. 

    Please elaborate.

    Link to comment

    You can use a (Microsoft) Email address as account to login to Windows. When you created the same user and password in Unraid you were able to connect to shares without any other information. With 6.10 the usage of e.g. [email protected] was possible. With 6.11 you get an invalid user/password error. A workaround is to create a new user e.g. user1. Now you have to mount these shares with different credentials (user1 and password of user1). 

    Link to comment
    17 minutes ago, D.Romeleitis said:

    With 6.11 you get an invalid user/password error.

    This is reported by windows when trying to connect?

     

    In Unraid OS 6.10 (and all Unraid OS releases I think) it's not possible to set a user name of the form "[email protected]".

    Link to comment

    A valid user name for Unraid consists of lowercase letters a-z, digits 0-9, underscore(s) and dash(es).

     

    An email address as user name is invalid.

     

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.