No longer see Network Attached Storage in Network View on Build 10049

SkyNet3 · 09 Apr 2015

I can no longer see my Network Attached Storage in this build(10049) Enterprise. I have Network Discovery enabled and can get to the device by IP Address in a browser but am unable to map a drive to any share. Anyone else having these issues. I have Windows Credentials setup properly(at least it worked in previous builds) lol.

linw · 14 Apr 2015

I'm in the same boat. Mine disappeared on 10049 after the 10th of April. No idea why.

SkyNet3 · 15 Apr 2015

You can get to it by IP address to be able to map a drive but that still doesn't fix what Microsoft has once again broke!

linw said:

I'm in the same boat. Mine disappeared on 10049 after the 10th of April. No idea why.

fixit038 · 15 Apr 2015

SkyNet3 said:

You can get to it by IP address to be able to map a drive but that still doesn't fix what Microsoft has once again broke!

My issue's the same only it started with 10041 update (haven't done a clean install). re-did all the 'share' things to no avail. Have got 10 pc's with Win7, Win 8, Win 10 10041 and 10049. Win 10 can see rest but can't access - consistently - and then only the Public shares.

badrobot · 15 Apr 2015

I fixed mine by clean installing 10041 and then upgraded immediately to 10049.

SkyNet3 · 15 Apr 2015

I have done clean installs of 10049 and 10056 and both are not able to see the NAS

badrobot · 15 Apr 2015

SkyNet3 said:

I have done clean installs of 10049 and 10056 and both are not able to see the NAS

10056 will definitely not see it. 10056 is a leaked ISO upgraded from 10051 (because of the windows.old folder in it). I also clean installed 10049 from ISO I created with no success (there is no official ISO for 10049).
But the clean install of 10041 (official ISO) upgraded (online) to 10049 fixed it.

Here's the proof (it even sees my Rapsberry Pi

):

No longer see Network Attached Storage in Network View on Build 10049-10049_network.png

Bottom line, you need clean installs from clean ISO. Not upgraded or leaked ISO. Why? That's how it worked for me.

SkyNet3 · 15 Apr 2015

Thanks BADROBOT. MS needs to put out something new soon hopefully..

badrobot · 15 Apr 2015

SkyNet3 said:

Thanks BADROBOT. MS needs to put out something new soon hopefully..

No problem. It's been my motto here for the longest time. If something doesn't work right, clean install (from clean ISO) will always fix it (at least 99% of the time...

).

fixit038 · 15 Apr 2015

badrobot said:

No problem. It's been my motto here for the longest time. If something doesn't work right, clean install (from clean ISO) will always fix it (at least 99% of the time...

).

Thanks BadRobot!! An additional favor please? Do you use the 'Credentials' or just the 'Share this...' process? If credentials, would you go into some detail as to where each component comes from?

--------------

--------------
The user Name I used in the credentials is from my logon account/Outlook address.

Right? Wrong?

Nothing seems to work for me.

Again, all Win10 installs are upgrades. Either way, what are the correct components to enter into
Credentials? Should I be using fixed IP's for all devices? Still need Credentials?

TIA

Ed