stazza Posted June 11, 2021 Share Posted June 11, 2021 I get this error box when I try to access a share even with sufficient permissions. Accessing public shares are no issue though. Any insight is appreciated Quote Link to comment
stazza Posted June 11, 2021 Author Share Posted June 11, 2021 It was a simple fix. Just restart your computer! Should've done that before posting smh. But if you encounter this in the future, you know what to do! Quote Link to comment
ChatNoir Posted June 11, 2021 Share Posted June 11, 2021 Good to know, however, I cannot see the image. For the next time, you can simply paste the picture in the text box. 1 Quote Link to comment
Frank1940 Posted June 11, 2021 Share Posted June 11, 2021 2 hours ago, Stev said: It was a simple fix. Just restart your computer! Should've done that before posting smh. But if you encounter this in the future, you know what to do! Not quite, I suspect you got bit by this 'gotcha' of SMB: Quote Let me give you an operational example. Let's say your windows PC netbios name is "mypc" and your windows login name is "larry". Further let's say your server netbios name is "tower" and you have a single user defined on unRaid side named "curly". Now you open Network and click on "tower" and a window opens showing all the shares. In this state, if you now click on a "public" share, what happens behind the scenes is windows tries to authenticate with the server as user "mypc\larry". On unRaid side, samba (linux smb protocol module) will check if "larry" exists. In this case no, so samba will check if user "mypc" exists, in this case also no. So samba will now see that "guest" access is enabled for the server, so it will reply to Windows with "success" but on the samba side, will associate any further access with the "nobody" user on the linux side. Plus, SMB will only allow one login form any Client. Hence, once you login with 'Guest' (user = "nobody") credentials to the Unraid server, you can't login a second time with the Unraid user name that has access to the Share. Rebooting your client will fix the problem because it breaks the client-server connection. Quote from this post: 1 Quote Link to comment
Recommended Posts
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.