Hi guys - i am hoping someone could help!

 

I am having a knightmare trying to setup private shares on my unraid server.

I create the share, make it private and then assign my user read/write access.

 

I then try to map the drive in windows. It asks me for credentials, which it then accepts and maps the drive. I then try to write to the share and it says that i do not have permission. I have rebooted and run 'Docker Safe New Perms' but nothing seems to work. It looks like i can create a file sometimes on the share, and then it just stops working and i can read only.

 

Any ideas please?

 

 

 

7 minutes ago, trurl said:

I have read a few posts about this - and this link takes me to another link which is then quite old.

I have tried adding a user to unraid as the same name as windows and then clearing the saved credentials and net use * /delete. I then reboot server and PC but i still do not have write permissions. A lot of the posts talk about generally accessing the share (which i can do), i just have read only permissions when my user is set to read/write.

Be sure that you have read the half-dozen or so posts that follow the link that @trurl pointed you to. 

 

You may have bitten by one of the many SMB and windows gotchas.  Be sure to understand about the problems with reusing user names.  If one of those situations does not apply to your case, you will have to post up complete details (all user names (both Windows and unRAID), version of Win10, etc.).   You also have to realize that the actual SMB 'spec' is controlled by Microsoft and the samba crew has reversed engineered it.  When MS makes a change, it can take some time until they can catch.  MS has also decided to tighten security in WIN10 and that caused issues back when it was first released.  Plus, SMB started out life back with Windows for Workgroups 3.1 in the 1990's.  It was intended to allow a small group of  computer of PC's to be networked together without requiring a dedicated server.  It was a bit of kludge in those days and remains one today.   But it mostly works-- if you know and can deal with its many eccentricities.

Edited September 26, 20178 yr by Frank1940

OK i think i am getting somewhere. I created a new share and it now works.

So i tried to delete my old share (which has disappeared from the unraid gui) but it still shows when i browse to my unraid server?

 

I think the issue is that it is remembering old share names. If i create a new name share then it works?! Is there a cleanup tool i can run??

New update - OK so i have now removed the ghost share and it seems to be working. What does break it is if you try and redirect your documents folder to the mapped drive. This then completely breaks the permissions so badly that you need to delete the share in order to get write permissions working again!!