Hello,

 

I am running a unRaid 6.6 and noticed that my server does not show up under Network/Computers on Windows 10 computers.   I can reach it with the IP address of course.  For my macOS computers, the server automatically shows up.

 

The I run a Seagate DP-6 NAS device and it shows up on both my Windows 10 and macOS computers.

 

Does anyone know if there is a special setting I need to use to get unRaid to broadcast itself to Windows PCs?

Start at the end of this page and work your way back up the thread: 

 

       https://forums.unraid.net/topic/53172-windows-issues-with-unraid/?page=3

 

MS is trying to secure WIN10 by limiting access to both guest accounts and resource browsing (via SMBv1).  As a result, you have to jump through hoops if you want to use any of these features.  

 

Make notes of what you did and if you can't get things to work, post back with details (including the Win10 version and release version) and, perhaps, we can figure out what your problem is. 

 

Edited April 9, 20197 yr by Frank1940

This was the thorn in my network's visibility...

 

I decided to take another crack at this after several months, and only ended up changing two settings that worked. (Although I can't speak to anything else in the past I've done that might have contributed to this like adding the Local Master plugin to Unraid.)

 

I followed @Frank1940's link, and moving from the bottom as suggested. Starting at StrandedPirate's post to have no effect after restarting my computer. Continuing up I went through @Frank1940's suggested link, bringing me three more links deep to find How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server.



Checked the client box only, required a reboot.... and FINALLY! It's back to being usable!....

 

Glad to see you got it working!  As a point of interest, this is what that same Setting looks like in Window 10 Pro, version 1809!

 

 

Notice the extra option (SMB 1.0/CIFS Automatic Removal).  I have been given to understand that it automatically will turn off both the SMB 1.0/CIFS Client and Server options after a fixed period of time!  (Clicking on the SMB 1.0/CIFS File Sharing Support turns on all three of these options.)  This is one of the reasons it is necessary to know what favor and version of Windows 10 folks are using when they have a problem.

Edited April 10, 20197 yr by Frank1940

Makes complete sense 

 

Glad to be of help.

Edited April 10, 20197 yr by TheInfamousWaffles

So bit of an update. As I was curious if this was some setting/registry edit I had altered on my computer before.

 

I created a new VM running Win 10 Pro 1809, confirmed I couldn't see my Unraid network drive, then only changed this one setting and it works!

 

. Like @Frank1940 pointed out, 1809 does add the option for automatic removal, and it's probably best to avoid that unless you only want to utilize it for a short period of time.

 

I hope Unraid ends up supporting SMB 3 so this issue goes away for all.

 

Edited May 3, 20197 yr by TheInfamousWaffles

On 5/3/2019 at 12:19 PM, TheInfamousWaffles said:

 

I hope Unraid ends up supporting SMB 3 so this issue goes away for all.

It already does!  See here:

 

      https://en.wikipedia.org/wiki/Samba_(software)#Version_history

 

I am not sure what 'issue' you are talking about.  Realize that MS is concerned about the corporate environment and the security requirements that having 'deep pockets' present.  Many features that us home users 'love-and-use' are the things that give Security IT people nightmares...

On 5/3/2019 at 5:19 PM, TheInfamousWaffles said:

I hope Unraid ends up supporting SMB 3 so this issue goes away for all.

As was mentioned this is not the problem as Unraid already supports SMB3 and has for some time.   The issue is that the Network discovery capability that SMB1 supported is not part of the later SMB versions.    In a corporate environment this will not be an issue as in those cases there will almost certainly be dedicated WINS and Domain Controller servers.  In a home environment one is unlikely to have this type of capability set up.