· Something else
· None of the above
· Other
Solved - Windows 10-Update kicked out WD-NAS by DNS as accessible network drive.
WD MyCloud NAS, Windows 10, Telekom-Router, all in same LAN, wired
Just for others, who might run into a similar issue.
Yesterday my Windows 10 PC, acting as Roon-Server rebooted unexpecteldy, might have been a Windows Update.
It was connected to my NAS from WD.
Now it refused to connect at all, despite showing up as NAS in the Network Section of the Explorer.
From macOS the NAS was accessible as before.
In Roon I could set up the same path by smb://NASNAME/sharedfolder and for one or two seconds, it would have access (could see all the subfolders). But once the path was rendered windowslike to "\NASNAME\sharedfolder it lost the access.
Rebooting the NAS and the Windows didn’t help. Cutting all network connections either.
reinstalling smb1-support (helpful page with the exact errorcode 0x80004005 as topic: Fehler 0x80004005 bei Laufwerkverbindungen | TECH FAQ) … it all failed.
So in Roon itself I could access everything again by using the IP-Adress instead of the NASNAME
like smb://192.168.2.169/ and logging in with my NAS-user account. The latter was not needed before.
In case others run into a similar issue with Windows 10 suddenly acting strange, I hope this helps.
Case closed so to say 
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.