• 6.8.3 - AD joined Unraid and inconsistent user creation cleanup


    start846432
    • Minor

    Recently had a problem where I frequently was unable to browse secure shares on my AD joined Unraid instance - whenever I tried to access a share using my account, I would continually be prompted for a username and password. Using any other AD account worked fine.

     

    Suspect this is due to my trying to create a user in the webUI with the same username - it appears that while the user is not created and passwd/shadow remain clear, the user is still created in the samba user directory (tdbsam?). When trying to browse secure shares, it would authenticate using my AD account and then try to authenticate using the tdbsam one. Details of what (I believe) the problem is in the thread below:

     

     

    I haven't tried to reproduce this issue as I do not want to go through that hassle again. Also, there was no error generated when the user creation failed - the Unraid 'loading' logo was present for a few seconds then just disappears.




    User Feedback

    Recommended Comments

    There are no comments to display.



    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.