hi there,
Today i did a fresh install of win 10 Home today on my laptop but i'm unable to see my NAS Drive in my network. I can put the nas address into the address bar in my Network and i can access it but i don't like to do it that way. I also use Kodi media center and now my nas is not showing in my network i can't add media content.
Welcome to the club.
This issue has been going on since some Windows 'update' two weeks ago.
Microsoft is playing deaf-mute about this problem, and has still not acknowledged this big issue that many Windows 10 users are now experiencing.
Some users say there might be duct-tape solutions, but I 've tried a few of those and nothing helped.
Also the last 'Cumulative Update' from yesterday that many had some slight hopes on again doesn't fix this.
So we'll probably have to wait for the next glorious Windows 10 update.
Its a pain, when i installed Windows 10 Home on release day its been great but i had to reformat my drive and used the media creation tool and did a fresh today and my nas is knowhere to be seen. very irritating.
I have an old dlink DNS-323 and never have any problem with any build of Windows 10. I even setup to access it to ftp via ddns from outside my house. So maybe it's something that you did not setup correctly.
I've set it up like i have with my htpc and my wifes laptop with windows 10 Home and they are fine.
Do you setup your NAS to have a static IP ?
If you have a Static IP and have the Hosts file or Kodi knowing what the IP and name is. Kodi should find it either way. Personally I would use the IP over the name, because less problems.
I've mapped the nas to a drive with letter Z and Kodi connects to it fine but now. Now i have a problem that when i restart windows and enter the desktop i get a notification saying my mapped drive is diconnected. When i click This PC my mapped drive has a red X through it.
I am interested in this also as I too have NAS boxes and Win10 does not see them. Same applies, I can type it in the address bar and it works, but click on network it does not
That is a user Credentials issue. This explains why it got screwed up when they went from how it was up until 8.1. Microsoft Outlines Windows 10 Security and ID Management Controls -- Redmondmag.com