DrQ

Resolved my issue. Also my win11 pro that was working was set to "Not Defined". The one that did not work was "Send LM & NTLM - use NTLMv2 session security if negotiated" and changing that to "Send NTLMv2 response only" allows me to connect to the private shares again. Not sure what in the past may have set this to something other than "Not defined" Thanks for the time and resolution to this issue.

This is correct. One win11 Pro connects the other claims auth error when connecting to the samba server. I checked Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters and only difference is the one that does connect has FileInfoCacheLifetime -> 0x0 and FileNotFoundCacheLifetime -> 0x0 but seems not relevant to SMB auth. Also when on 6.11 I delete the Stored Credentials on the computer that would not connect and had no effect. Ran a sfc /scannow to rule out bad files. Not sure what else to check on the windows settings for issues so falling back to just running 6.10

Confirmed that the issue with authenticated connections from one of my two windows 11 Pro PCs is tied to 6.11 as rolling back to 6.10 works. Did it twice and just will not work in 6.11. There clearly is some breaking change in 6.11 samba affecting multiple users. Guess just have to roll back to 6.10 and monitor for a fix.

Same here I think. I have two windows 11 clients. One connects the other does not. The client that does not connect to unraided share will connect to a windows share. I will have to try restoring back to 6.10 and see if it works again once a data move operation completes on the unraided server. This seems to be more than a single user issue with unaided samba why was this thread closed?

KuroSetsuna29 had the solution some sort of bad cached data. In Chrome right click on page and select Inspect to pull up the dev tools when on any page for the unraid server. Then goto the Application tab, and in the left select storage. From there I cleared the site data and third-party cookies and now it loads with incognito mode. Now if my Recreating database … will ever complete

One other thing I noticed with this docker is the contain had a high writable size after getting high docker container utilization warnings. I ended up adding in another contain path map /usr/share/elasticsearch/logs TO /mnt/user/appdata/elasticsearch/logs/ to push this large folder out of the container. Does anyone know if there is a downside to this? Not sure why a folder in the GB size was not in the docker template unless maybe created some issues?

I am running into this exact same issue where the mover is halting my dockers until it completes. Seems this topic died out 2 years ago with no suggested resolution. Any know how to get mover to go slower (less disk io) to allow the dockers to keep running? I cannot even pull up the docker screen when mover runs.