November 21, 20232 yr A recent Windows 11 update left me again unable to access my shares. Most of the machines that I use with Unraid are Azure AD joined. Whatever update I acquired on Nov 19th seemed to only affect my Windows 11 laptop. I figured this is a good time to finally get off my butt and do away with SMBv1. Unraid has been running in various incarnations for almost 10 years. Might as well set it up right. I undid the changes made to Win11 that were allowing me to access shares as guest. Disabling "enable insecure guest logons" Turning on Password Protected Sharing I also set AllowInsecureGuestAuth to 0 in the registry for good measure. I disabled NetBIOS in Unraid and ensured that WSD was enabled. I created user accounts as required I set all of my shared to Private and assigned permissions to users accordingly I created a credential in Credential Manager and tested I downloaded Frank1940's SMB Setup document and walked through it step-by-step to make sure that I didn't miss anything. My shares work just fine now, they even appear in the left pane in Windows Explorer in Win11 and Win10 with SMBv1 disabled. I added credentials to my Kodi boxes and ensured that those worked again. I checked a Windows 10 VM that was NOT Azure AD joined just for good measure. Once I gave it credentials all was well. For the sake of testing I removed the credential in my Win11 laptop and the Win10 non-AzureAD VM and retested. In both cases clicking on the hostname in File Explorer prompted for creds just as expected. Entering \\<HOSTNAME> or \\<IPADDRESS> in the address bar also now prompted for creds. Also as expected. Entering the credentials again in Credential Manager had everything back to normal. What has me scratching my head is that from any machine, that does not have creds in Credential Manager, if I enter \\<HOSTNAME>.<WORKGROUP> I get immediate access to all shares. I don't have a domain in-house. Only the machines related to my business are AzureAD joined. I run a DNS server in pfSense that ensures that HOSTNAME and HOSTNAME.WORKGROUP resolve correctly to the same place as I have several VLAN's and use DNS to resolve hosts in the subnets on other VLAN's using other Workgroups. I'm assuming that since Unraid and all of my machines have been running for years that they must have credentials cached as \\<HOSTNAME>.<WORKGROUP> but they aren't in Credential Manager and I can't for the life of me figure out if they are hiding somewhere or there is some other reason that I can access shares by using what is, sort of, an FQDN address. Has anyone else run into this?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.