I have to admit that I've struggled with this since I started using Unraid and often revert to public shares just because this seems to be so temperamental, its about time I got this working and tried to understand what the issue is.

I have several shares mostly default but some i've created myself:

I try to make these private so that they are secured and inaccessible unless you have permissions but whenever I do so I get this error constantly:

The password is correct, or at least it is the same password I copy/pasted into the users section of Unraid on this page, which also shows that the account should had read/write access.

So how do I start to troubleshoot this I am now on 7.1.4, I've had this issues since I started in 2022 with Unraid 6.10 ... I really want to be able to reliably use credentials to secure share access from my windows 11 machine.

Details:

Unraid 7.1.4 OS Plus

Fix Common problems doesn't report any issues

All plugins and containers up to date

Windows 11 pro fully patched

I can access the Unraid Admin GUI from the windows 11 PC (as is demonstrated by the screenshots) so network is up and working

If I make the shares public they are all accessible.

I suspect this is a Windows 11 "feature" but I still don't know where to start looking

Make sure there aren't any other credentials saved for that share, then create a new; see here: https://forums.unraid.net/topic/177975-formatted-my-pc-and-installed-fresh-windows-11-now-cant-access-smb-shares/?do=findComment&comment=1478526

Have you made sure that the credentials in Windows Credentials Manager match what you have set in Unraid.

Plus, you have some 'Public' Shares. If you don;t have a valid Windows Credential set up, you could be logging in using Unraid's 'Guest' account. Windows will only allow one log-in from any client computer to any server.

See here if you want more info on what is happening in the background:

https://forums.unraid.net/topic/25064-user-share-problem?tab=comments#comment-228392

I understand that If a Windows Credential exists for a server, Windows will always use it first (in the background) to log into the server. It then tries several other sets of credentials until one works. (This could result in a 'Guest' connection.) At last resort, Unraid presents a login windows if none of the previous attempts have worked. Unfortunately, Windows will not allow the connection if that client is already logged in as another user. And the error message provides no information as why it failed.