Bear with me as I am pretty sure this is a Windows problem but am wondering if others have it and what might fix it.

 

I have updated all my PCs to latest "fall update" (new name for service packs lol) Windows 10 version 10586. Immediately after the update, I was unable to see ANY workgroup members (pc or unraid) in the Network app. Was able to map shares by manual typing but the browse function did not show any machines other than the local PC.

 

Yesterday (11/18), they pushed out a "cumulative update version 1511". That fixed showing PC members of the workgroup in Network, but Tower is still absent. I can map shares but that is not going to work long term due to the sheer number of them. No amount of rebooting (pc or tower), refreshing, etc makes it appear.

 

I have all the standard services and permissions in place, and it all worked fine before and as far back as factory W8.1. Any ideas?

Should mention that I am able to read/write at full speed to shares on Tower. Just can't see it.

I have the same issue and found this thread which is active and might have a fix for you..... 

 

http://www.tenforums.com/network-sharing/7386-cant-see-other-computers-workgroup-windows-10-computer.html?s=460878d0231be20cf29a3c0d0a45ab4b

 

The only fix I haven't tried is

http://www.tenforums.com/network-sharing/7386-cant-see-other-computers-workgroup-windows-10-computer-7.html

which is:

"I discovered that my server on the network had defaulted to smb2. I changed the server to smb1, and yikes everything appeared under Network in Win 10 Pro 64. It seems any networked computer not on smb1 will cause all network browse to fail. " 

 

"CMD (admin)

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi

sc.exe config mrxsmb20 start= disabled"

 

I did not try this yet because I don't know enough about SMB. Maybe someone here can enlighten me on whether or not this is a safe move to make with unRaid?

I have the same issue and found this thread which is active and might have a fix for you..... 

 

http://www.tenforums.com/network-sharing/7386-cant-see-other-computers-workgroup-windows-10-computer.html?s=460878d0231be20cf29a3c0d0a45ab4b

 

The only fix I haven't tried is

http://www.tenforums.com/network-sharing/7386-cant-see-other-computers-workgroup-windows-10-computer-7.html

which is:

"I discovered that my server on the network had defaulted to smb2. I changed the server to smb1, and yikes everything appeared under Network in Win 10 Pro 64. It seems any networked computer not on smb1 will cause all network browse to fail. " 

 

"CMD (admin)

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi

sc.exe config mrxsmb20 start= disabled"

 

I did not try this yet because I don't know enough about SMB. Maybe someone here can enlighten me on whether or not this is a safe move to make with unRaid?

 

I disabled SMB2&3 because there is currently a compatability issue with SMB2&3 as implemented by SAMBA and SMB2&3 as implemented by Windows.

 

I'm not sure that's how I did it exactly, but it did involve the command line. If you google how to disable it, there is a Windows support page on Microsofts website that describes the process.

 

Edit: Found the Page

You want to follow the instructions for "How to enable or disable SMB protocols on the SMB client"

 

Honestly though, I think this will be fixed when unRAID updates to the latest version of SAMBA.

 

Also if we can agree on a fix, can we perhaps sticky the solution since I've seen this question about a dozen times now.

I have the same issue and found this thread which is active and might have a fix for you..... 

 

http://www.tenforums.com/network-sharing/7386-cant-see-other-computers-workgroup-windows-10-computer.html?s=460878d0231be20cf29a3c0d0a45ab4b

 

The only fix I haven't tried is

http://www.tenforums.com/network-sharing/7386-cant-see-other-computers-workgroup-windows-10-computer-7.html

which is:

"I discovered that my server on the network had defaulted to smb2. I changed the server to smb1, and yikes everything appeared under Network in Win 10 Pro 64. It seems any networked computer not on smb1 will cause all network browse to fail. " 

 

"CMD (admin)

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi

sc.exe config mrxsmb20 start= disabled"

 

I did not try this yet because I don't know enough about SMB. Maybe someone here can enlighten me on whether or not this is a safe move to make with unRaid?

 

I disabled SMB2&3 because there is currently a compatability issue with SMB2&3 as implemented by SAMBA and SMB2&3 as implemented by Windows.

 

I'm not sure that's how I did it exactly, but it did involve the command line. If you google how to disable it, there is a Windows support page on Microsofts website that describes the process.

 

Edit: Found the Page

You want to follow the instructions for "How to enable or disable SMB protocols on the SMB client"

 

Honestly though, I think this will be fixed when unRAID updates to the latest version of SAMBA.

 

Also if we can agree on a fix, can we perhaps sticky the solution since I've seen this question about a dozen times now.

 

Really appreciate your reply, thanks!