May 13, 20215 yr Hi all, Made an account to write this here. I'm running on a fresh install of Unraid 6.9.2. I've got a handful of shares created on my server. Almost all of them are Secure but I have one of them configured as a Public share for testing purposes. All shares I'm attempting to access are set to Export. My computer is running Win10 Pro ver 20H2, build 19042.985. I've tried a number of fixes at this point (the AllowInsecureGuestAuth fix, the Lanman workstation fix, and even the SMB1 fix for a little bit) but am still unable to connect to my shares. My server shows up in the Network section of File Explorer, but when attempting to open that computer I get the following error: My DNS is configured on a Pihole, and that Pihole has a DNS entry configured to point ericserverpc to its private IP address, which I can confirm with an nslookup. I'm at a loss for what might be causing this and how to ultimately resolve it. Anyone have any ideas what else I might be able to try?
May 14, 20215 yr Author Updating my own thread. It seems to work when only SMB1 is enabled. Anyone got this working with SMB2/3 that can share how they accomplished this?
May 14, 20215 yr Since you are running Windows 10 Pro, you also need to make this change: https://forums.unraid.net/topic/59672-solved-w10-you-cant-access-this-shared-folder-because-your-organizations-security-policies-block-unauthenticated-guest-access/?tab=comments#comment-598969
May 15, 20215 yr Author Already done. That’s the Lanman workstation fix I mentioned in my initial post.
May 15, 20215 yr Missed that you indicated that you had done both of them. Have you done the changes in the Control Panel described in this post? https://forums.unraid.net/topic/89452-windows-issues-with-unraid/page/10/?tab=comments#comment-947157
May 15, 20215 yr Author Yup, and on top of that everything is already in the same workgroup. Even changed the workgroup across all of my relevant devices to something other than what it was originally (but still the same one across all my computer, Unraid server, and qnap NAS) and it changed nothing. The only time I was able to remotely navigate to it was when SMB1 was the only SMB protocol active, which is not a configuration I’m willing to keep. Edited May 16, 20215 yr by eroc1990
May 16, 20215 yr Author Somehow missed the password protected sharing toggle but even after I tried that nothing worked. Like I said the only case where it did actually work was when SMB1 was the only SMB protocol enabled, and I'd rather not drop support for SMB 2/3, since my Qnap NAS (per my configuration) requires a minimum SMB version of 2.1. Disabling anything after 1 would break the bulk of my SMB shares.
Archived
This topic is now archived and is closed to further replies.