Readynas not showing in Network view Windows 10 Build 10586 but connects ok

Does this new system still rely on a workgroup master browser?  That's where I've had trouble.  My network currently has three devices reporting to be a master browser, and two of them are ReadyNAS's (one running OS6 and one RAIDiator).  But the NAS's do not seem to be equipped to be a master browser.  So if the one computer that should be the master goes offline, network discovery breaks.  If the NAS's weren't claiming to be master, another computer would be "elected" as master, and all would be fine.  But no such election is performed becase a device incapable of being one is claiming that it is.  I've read of folks having a network printer do the same.

Here is a good article on this and a link to a program that will tell you who the master(s) is/are.:http://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/.

Unfortunately, fixing the issue of the master browser does not seem to be that simple.  When I finally took down an old XP machine that was the master, I had to force the issue.  I turned everything on the network off, then turned on the computer I wanted to be master (one I normally leave on and has a reserved address in my router),  Then, one at a time, I turned on the other devices and did a "NET VIEW" in a CMD window to see that  the device became visible.  It all worked with that Win7 computer.  I have not tried to get it to work with a Win10 one, as I have heard that that Microsoft changed the discovery protocols supported in Win8 and on.

OS4.x had the ability to designate a NAS as a WINS server, which I think would also help with this, so long as that NAS is always on.  But OS6 appears to have dropped that capability.