So a couple weeks ago I had the 24H2 update install on my home PC. Lost access to shares. Google and this forum help me figure out I had to set up a user on unraid. I did this, added credential to win11 pc and all was well until this morning when i tried to copy some files from my PC to unraid shares.

Getting access denied errors with using explorer copy & paste and using TeraCopy 3.17. Reading files and playing media woks as expected. Can also copy from array to desktop without issue.

Tried deleting user from unraid and clearing credentials in windows. rebooted both windows client and unraid. Added user again and set up credential in windows. rebooted both again, no change.

I hope the experts here can help me learn what the heck is gong on!tower-diagnostics-20250309-1531.zip

Edited March 10, 20251 yr by wirenut

I looked at your Shares that exist with files.  I noticed that several of them were being exported as 'hidden'.  Try removing that by changing that to a simple SMB export and see if that fixes the problem.  (Since you now have credentials on your server, you can make those shares 'Private' and that will prevent access from unauthorized LAN users.) 

 

Also check your Minimum Free Space on the shares that you are using. 

 

If you are still having problems, please provide the first and last letter of the share name for the share(s) you are having problems with.  (You have checked to verify that this problem exists on all shares???)

Edited March 9, 20251 yr by Frank1940

@Frank1940 thanks for the support.

So think i did what you recommended what you stated about the hidden shares.

then tested this:

QUOTE - If you are still having problems, please provide the first and last letter of the share name for the share(s) you are having problems with. 

copy to Ml   --  ok

copy to Ml - sub folder - no go

 

tried with others and same problem

 

set up test share "test" and try, asks for password as expected, enter and no go. same error, not accessible

 

what can i do next? new diags attached.tower-diagnostics-20250309-1820.zip

50 minutes ago, wirenut said:

asks for password as expected

If you already have connected with some credential, and then Windows asks for a password, it won't work because Windows won't allow another connection with different credentials.

 

This is an old post from limetech, but Windows still works that way.

 

IF you set the security to Private for a share, you have to grant access to that share by setting the permission for each user.  Example below:

2 hours ago, wirenut said:

copy to Ml   --  ok

copy to Ml - sub folder - no go

 

You have one share that begins with an "M" and ends with an "A".

You have another share that begins with an "M" and ends with an "e".

 

Both of the "M" shares were 'Public' in your your first Diagnostics file but the M-----------e share was 'Private' in the second Diagnostics file.  That share also had an indication that you  had assigned read-write permissions to one of the Share Access users.  Did you set up a Windows Credential (in Windows Credential Manager) for that Share Access user.  You also have to reboot the Windows machine any time you make a change to SMB on that computer.  

 

EDIT  Setting up a Windows Credential avoids most of the issues that are described by LimeTech in that link that @trurl provided.

Edited March 10, 20251 yr by Frank1940

Yes, have user credentials set up in windows.tower-diagnostics-20250310-0047.zip

Yes, I changed the public'hidden to private as you suggested.

Yes, forgot to add permission for SMB user on new TEST share, now works ok.

If i try to copy a file to root of M--------a share it copies fine. If i try to copy one or two directories in, it fails. But strangely this is not consistent with all sub folders...? 

 

6 hours ago, wirenut said:

If i try to copy a file to root of M--------a share it copies fine. If i try to copy one or two directories in, it fails. But strangely this is not consistent with all sub folders...? 

How were these directories created?

 

Try running New Permissions on just the M--------a share

10 hours ago, trurl said:

Try running New Permissions on just the M--------a share

 

OK! That seems to have done the trick!

No idea why or how this happened, but every directory i tried copying to yesterday that failed now works.

 

@Frank1940 @trurl

 

THANK YOU!

 

Edited March 10, 20251 yr by wirenut

13 minutes ago, wirenut said:

No idea why or how this happened

Then you aren't done. I wouldn't be surprised if it happens again.

 

11 hours ago, trurl said:

How were these directories created?

 

The one that started me looking into this issue was recently created by sonarr. Then I chose a couple at random that were also created by sonarr at one time or another as well as manually by me from a Windows client.

Post docker run

docker run

  -d

  --name='Sonarr'

  --net='bridge'

  --pids-limit 2048

  -e TZ="America/Chicago"

  -e HOST_OS="Unraid"

  -e HOST_HOSTNAME="Tower"

  -e HOST_CONTAINERNAME="Sonarr"

  -e 'PUID'='99'

  -e 'PGID'='100'

  -l net.unraid.docker.managed=dockerman

  -l net.unraid.docker.webui='http://[IP]:[PORT:8989]/'

  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sonarr-icon.png'

  -p '8989:8989/tcp'

  -v '/mnt/cache/appdata/sonarr/':'/config':'rw'

  -v '/dev/rtc':'/dev/rtc':'ro'

  -v '/mnt/user/MEDIA/TV shows/':'/tv':'rw'

  -v '/mnt/cache/downloads/':'/downloads':'rw'

  -v '/mnt/user/MEDIA/Monkey Butt Channel/':'/john':'rw'

  -v '/mnt/user/MEDIA/TV Documentaries/':'/tv documentary':'rw'

  -v '/mnt/user/MEDIA/TV Shows Animated/':'/tv show animated':'rw'

  -v '/mnt/user/MEDIA/TV Shows Comedy/':'/tv show comedy':'rw'

  -v '/mnt/user/MEDIA/TV Shows Classic/':'/tv shows classic':'rw' 'linuxserver/sonarr'

8745827540c1b16552ed475220428d0e9df3df84e0bd59ae2ac27213d0705c75

Add UMASK variable to the Docker container.

 

You may have to click on 'Show more settings" to see the PUID and PGID ones.

 

The reason for this is that many Linux distributions set the permissions as 755 for directories and 644 for files.  Unraid requires that the permissions be 777 and 666 respectfully.  A UMASK of 000 forces the proper permissions.

3 hours ago, Frank1940 said:

Add UMASK variable to the Docker container.

OK! Docker run now says:

-e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="Sonarr"
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='000'

 

Thinking now this is the permanent fix and will prevent issue going forward? Or is there more to do? (other than updating my other 'arrs' container)

7 minutes ago, wirenut said:

Or is there more to do? (other than updating my other 'arrs' container)

Probably not. But if you are a bit paranoid (as I am), you might want to check the permissions of newly written files from Sonarr (use the built-in Dynamix File Manager) to be sure that the permissions are at least 777 for directories and 666 for files.   (777 is ok for files except that the file is being marked as executable which could be considered a bit of a security risk.)

I don't actually have that umask for Sonarr and I don't have this problem.

 

I do have that umask within the settings of NZBGet at Settings - Security - UMask and also for my only other downloader, transmission in its settings.json file.

30 minutes ago, Frank1940 said:

you might want to check the permissions of newly written files from Sonarr

i will check as some new ones come in to be sure its working going forward

 

23 minutes ago, trurl said:

I don't actually have that umask for Sonarr and I don't have this problem.

I didn't either (obviously) and hadn't had this problem while shares were set to public and/or public (hidden) and guest access from windows wasn't an issue.

No more guest access allowed from windows without credentials, that's when this became an issue for me . I guess that unrestricted guest access just didn't care?

Coincidence or not, I dont know, but hopefully this is the final answer and its fixed.

 

Thanks again @Frank1940 and @trurl for all the help!