Jump to content

Unable to access private shares


Go to solution Solved by SliMat,

Recommended Posts

Posted (edited)

Hi All

 

I had my USB key fail today, saying there was a checksum error, so I restored my backup on the same key - I've had this before so do realise I need to update my key again, but have used the automated key replacement process back in January - so am unable to do this again... and havent had time to email in for a key change.

 

So, my question is this... the machine is back up and running, but all my private shares (SMB) are inaccessible. If I set them to public then I can map and access them from my Windows PC, but if they are set to private with my user as having read & write permissions I am unable to access them. I have checked my user password by resetting it in UnRAID in case it had been corrupted... but I am running out if ideas now 🙂

 

This is the error;

 

image.png.da10cd3ee1ef9e64b7cdd81bbad75b93.png

 

I have attached diags too - but can anyone help as I dont really want my kids accessing my personal files ;-)

 

Thanks

 

unraid-diagnostics-20240610-1729.zip

Edited by SliMat
Posted (edited)

A quick update - I now cant access any shares whether public or private.

 

From my windows PC is I use \\192.168.xx.xxx (Unraid IP), I usually get a list of all the shares and can map them. Now I get a login prompt and even if I use the root credentials I get an error...

 

image.png.54fa688df9b973061fed88b20b58c2c9.png

 

Edited by SliMat
Posted

Interestingly, on my Windows 11 laptop I can access the private shares... but my wife is unable to access her data, on her Windows 11 laptop, so I have had to set her share to public... so, I am not sure what is going on!

  • Solution
Posted

OK, I am not sure whether this was the cure, but as nobody was able to offer any advice, I updated the O/S to the latest stable version as I was 1 version behind and it seems to be OK again for the moment... so, fingers crossed it was some corruption on the restored O/S.

Posted

OK.  Let me point you to a thread that discusses a way to avoid the type of problems that you are experiencing.

 

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

 

Download the two documents in the first post and read them.  SMB was designed by, and is still controlled by, Microsoft and it is a minefield to setup for the novice user. (Samba has reversed engineered MS's SMB protocol to work with SMB.  Unfortunately, they are are speaking different languages when it comes to the error codes that MS uses to display messages after a connection failure.  These messages are confusing at best to totally useless.)  Using a cookbook approach to setting things up in a way that meets MS security concerns is the easiest way to use SMB.  Those security concerns for the most part are being driven by their corporate and government clients-- not the average home user!  And there is another change which MS is rolling out called SMB signing which will further restrict access to Public shares for many Windows users. 

Posted

Thanks @Frank1940 - I will take a look through the documents on the link you sent and see if I am able to implement a better way of achieving this. At the moment as long as a user is logged on to their local machine using the same credentials they can seamlessly access their mapped private shares... but if MS are changing things more, which will cause these kind of issues I guess I need to make some changes to ensure people can access their files :)

 

Thanks

Posted

And remember that the login must be to a Share User with credentials on the server.  (Unraid still does permit 'guest' (no user name or password) logins.)  Furthermore Windows will only allow one login to each server.   If Windows has been hacked to allow the guest type of login and does it, you will never be able to access Private shares later even if you are prompted for a login.  And you can not logout from a server using the Windows GUI.  (This problem often occurs if one accesses a Public share first before access the Private share...)  That is the reason for setting the server login using the Windows Credential Manager! 

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
Reply to this topic...

×   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.

×
×
  • Create New...