Hello, I reset my Windows 10 PC (Fresh install), and can no longer write to my samba shares. I figured it was because I was not logged in (Guests only have read access), and now i'm stuck at the login menu, and I cannot login as a user or as root. Windows explorer says Access Denied.

I think this might have something to do with me running "chown -R 0777 /mnt/user/Media/" the other day, instead of "chmod -R 0777 /mnt/user/Media", but honestly i'm not sure. 

I went ahead and ran this : chown -R nobody:users /mnt/user/Media , however still can't login to my private network share. (Set it to private to force credentials prompt)

Please advise ?


 

Quote

FULL ERROR:

\\tower is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. bla bla bla

 

Edited August 24, 20187 yr by ct1996

Not sure if you have one of the Win10 issues or just a more general SMB/Linux user permission problem.  (You have the 'generic' Error Message that Windows throws up with all SMB problems.) You might want to start with the general permission problems and see if any of issues discussed apply to you.  The way Windows handles logins (sometimes in the background) and the fact that each computer/user can only only log into SMB only once can really cause confusion that stumps even the experts at times. 

 

     https://lime-technology.com/forums/topic/25064-user-share-problem/?tab=comments#comment-228392

 

Next thing to look at is whether you can access the shares in question from any other OS's.  

 

Why didn't you use the 'Docker Safe New Permissions' Tool?  This utility is installed by the 'Fix Common Problems' plugin.  

 

Now for the Win10 problem is general.  Start by reading these threads:

 

      https://lime-technology.com/forums/topic/53172-windows-issues-with-unraid/?page=2&tab=comments#comment-625264

 

 

If those don't help, post back and be sure to include what version of Win10 you are using (1803, 1709, etc) and the variety (Home, Pro, etc.).  Unfortunately, Win10 is not a single animal but several quite different ones (in places)!

     

 

14 hours ago, Frank1940 said:

Not sure if you have one of the Win10 issues or just a more general SMB/Linux user permission problem.  (You have the 'generic' Error Message that Windows throws up with all SMB problems.) You might want to start with the general permission problems and see if any of issues discussed apply to you.  The way Windows handles logins (sometimes in the background) and the fact that each computer/user can only only log into SMB only once can really cause confusion that stumps even the experts at times. 

 

     https://lime-technology.com/forums/topic/25064-user-share-problem/?tab=comments#comment-228392

 

Next thing to look at is whether you can access the shares in question from any other OS's.  

 

Why didn't you use the 'Docker Safe New Permissions' Tool?  This utility is installed by the 'Fix Common Problems' plugin.  

 

Now for the Win10 problem is general.  Start by reading these threads:

 

      https://lime-technology.com/forums/topic/53172-windows-issues-with-unraid/?page=2&tab=comments#comment-625264

 

 

If those don't help, post back and be sure to include what version of Win10 you are using (1803, 1709, etc) and the variety (Home, Pro, etc.).  Unfortunately, Win10 is not a single animal but several quite different ones (in places)!

     

 

Thank you for your help Frank, I actually came across that posting while googling and tried it to no avail. I am able to do proper reads/writes on my Macbook, so it appears to be a Win10 problem.. (isn't it always??)

I don't use the new permissions tool because it gave kind of a scary warning 

Quote

This is a mandatory one-time action to be taken after upgrading from a pre-5.0 unRAID server release to unRAID v5 or a later release. Select ALL DISKS when performing this one-time action.

 

and, to be honest, I need to run chmod every few days, due to my torrent docker creating folders that I can't read/write to, which chmod fixes. Probably another issue to address but I just want my write access back on Win10 ?


I read the second post you attached - I believe this is my issue. On my previous install, I had Windows 10 (Pro) installed for months before I used Samba. I'm guessing SMBV1 was  uninstalled and then when I tried to use it, a newer version of Samba (SMBv2???) was used instead. Great, flawless, no problems.

However, I reset my Windows10 and used Samba the same night, leading me to the problems i'm in now.

Windows 10 Pro, version 1803

I am going to begin looking at removing SMBV1, please offer any other advice if that isn't the correct direction.

And again, thank you for your help.

Edited August 24, 20187 yr by ct1996

Update, I actually already had SMBV1 disabled, so I tried enabling it. (Through Windows Features menu) Doing so prompted a restart and allowed me to login to the server using my credentials. However, I still do not have write access..


Edit:

Problem solved. My users (in the unraid GUI) somehow got reset to "read-only". Maybe I set it like that for testing. Anyways, I can do writes again.

to recap...

I went into Windows Features (Search "features" in Cortana/Taskbar) , turned on SMBV1.0 and disabled the newer version of Samba (probably not necessary)

And then I just made sure the accounts had R/W access from unraid GUI for the share in discussion, and boom. 


Attached a picture and marked the post as solved. Thanks Frank!!!

Edited August 24, 20187 yr by ct1996