My Windows 10 PC recently stopped being able to view or interact with the Roon NUC on the network when using File Explorer. I suspect the change could be due to a Windows update. Note that I can still use the Roon Remote software on my PC to control and play music from the NUC.
Here are the steps I’ve tried so far, but with no success:
enable SMBv1 client function
disable firewall from virus protection software
disable VPN
Changed Group Policy setting: Computer configuration\administrative templates\network\Lanman Workstation And “Enable insecure guest logons”
Can you try rebooting the modem (if there is one), then router/switch, then PC/NUC. This has helped me in the past. Let them all get new start on life (get IPs reassigned in an orderly manner). sometimes windows does not want to let go of a bad connection for some reason.
Thanks again. I tried rebooting each device in sequence, from the modem to the NUC. Then reset the network stack per the linked article. Still the same situation.
I can ping the Nuc as normal, but still don’t see it in Windows explorer. The error code I see in Windows Explorer is 0x80004005
No luck so far. I tried everything listed here. Thanks for your suggestions.
The only interesting thing to note is that every time I go to “Network and Sharing Options” and select “Turn on Network Discovery” and save the changes, when I go back in to that menu, network discovery has turned off.
Here is a thing to try. However this is a registry edit, so it depends on how confident/comfortable you are with it. Use at your own risk…
There was more on a “windowsreport.com” site but they were pushing “driverfix” program too much for my comfort level. Google “network discovery turns itself off” and you will see it.
Mine (custom built desktop with Win 10 Pro) still sees it too, but it has been flaky in the past with some of the updates. There have been challenges getting Windows to see Rock storage and my TrueNAS storage and be able to map the drives, also. Nock-on-wood, it is working now and has been for me for a while. We now also have a list of stuff (see above) to try the next time network locations disappear…