So I configured several SMB shares on my newly built Unraid server, but the only time I can get them to show up in Windows 10 is when I enable NetBIOS on Unraid and re-enable SMBv1/CIFS on Windows 10. Something that nobody should be doing due to the insecurities involved in it.

 

I can access the server just fine using the \\server-name method, which allowed me to pin it to quick access, however this is not ideal as it's not obvious or simple to use (despite telling my Father where I'd linked it he still couldn't find it).

 

I assumed that WS-Discovery being enabled on Unraid should allow for the shares to be seen in Windows 10's "Network", but this doesn't seem to make any difference even though I can see from a port scan that port 3702 for Web Services Discovery and port 5355 for LLMNR are active along with 139 for NetBIOS Session Service & 445 for SMB.

 

I've had issues with Windows before, but usually it eventually works itself out. I've already checked Windows has the Network set to Private and all the appropriate services (FDHost etc etc) are enabled and running. The Workgroups match (both set to HOME), and like I said it is possible to access it manually, but it just doesn't appear in the Network List until you turn to insecure methods.

 

Is this just one of those limitations of Unraid that because it's not Windows Server it just won't appear unless you use SMBv1/CIFS?

3 hours ago, Sergeant_Stevie said:

Is this just one of those limitations of Unraid that because it's not Windows Server it just won't appear unless you use SMBv1/CIFS?

 

That portion of Windows File Explorer Manager has been "broken" since SMBv1 was turned off in Windows.  MS has never come up with a replacement that works consistently.   If you are looking for something that will help in enabling quick access via Windows File Manager, see the first post in this thread. 

 

         https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-1011-smb-setup/

 

There are two methods in that post.   The Alternative Method seems to work better with Windows 11.

on any version of Windows 11
If you get error 8004005 

I have found that windows no longer prompt for credentials when goinf to a network resource.
Instead, the default send broken windows live account data to connect to a nas.

To fix this you have to go to the unraid Web UI > Users
Make a samba user 
On Window
Go to control Panel > Credential Manger > Windows Credential
click "add new" at the top ish page in the list...

set the unriad IP \\unraid-ip
set the samba user you made in unraid and the password
Then try to go to the nas by going to \\Unraid-IP

Did it work add the unraid name to the credentail manger... as well....

Thnxs Microsoft /windows 11 on breaking samba again...

Some other side things to check for samba windwos shairng fixes:
ne may do on windows is Program and features install smb 1.0 client and SMB direct "for smb3"
May need to open gpedit.msc for a GPO set for allow unsecure guest access, and confirm samba server signing....