I have had the same issues of sorts for a long, long time. I have several machines, my gaming PC, my wife's all-in-one and a couple servers all running Windows 10. My gaming PC has always been able to see the Unraid Server. But I believe, at least my for case I figured out what's going on. As a pretense, I scoured the internet for fixes for this and did the recommended regedit with changing the local master server on all the machines to false; although I'm not sure this actually helped. I'm actually pretty sure it didn't.
So my issues were that no other systems other than my gaming PC could see the Unraid server at all, including in file explorer. When I would try and navigate to the Unraid server it would pop open my default internet browser and try and have me login to the web gui.
After many many hours and trying to log issues with Samba I figured out what is going on, again at least in my case and hopefully it will help others as well. The other machines that couldn't see the Unraid server hadn't been given what I would consider "guest" access from what I believe is samba. By default Unraid gives user shares guest access. It took mapping a drive with anonymous credentials to a defaulted user share that had the default permissions for the systems to be able to see the Unraid server. Once I mapped a drive to this user share with guest access I was able to navigate to the Unraid Server in my file explorer without any issues. I was also able to see all the "visable" shares and navigate to them like normal.
Hope this helps other people, so far I've had no issues.
