Windows 10: Network Storage Shares no longer viewable after Windows last update Solved

  1.    12 Dec 2017 #1

    Network Storage Shares no longer viewable after Windows last update


    I have 4 NAS arrays. When I open Windows Explorer and look under Network there is as there always has been a section for "Computers" and another section for "Storage". Prior to the update, The NAS boxes would also appear in the "Computers" section. This allowed you to click on the NAS name to display the shares and map a drive or create a network location.

    Now after the update, the NAS boxes no longer show up in the "Computer" section. They only show up in the "Storage" section and will not allow me to see the shares or map them in Windowos Explorer.

    Has this functionality been moved? I can't map my shares anymore. The previous shares work on the PCs where they were previously mapped but when I log into the NAS and create a new share, Windows Explorer won't display it so I can't map it.
    Attached Thumbnails Attached Thumbnails WE display.jpg  
      My ComputerSystem Spec

  2.    13 Dec 2017 #2

    answer found on microsoft.com


    Just to pass this on here, I found this information on the Microsoft Support site and it is now the only way I can find to map a drive letter to a share on a NAS in Windows Explorer after the last update due to the changes described above from the update.

    Go into explorer and right click on computer, select, Add A Network Location, and then Choose a custom Network Location and then enter in my \\Nas (old drive location that I can no longer see) then select browse.
    This worked for me, but I also had to add my sharename. ie: \\NASname\Sharename

    This added a link under "This PC" in Windows Explorer. I then was able to map a drive letter to the NAS from that link.
      My ComputerSystem Spec

  3.    15 Dec 2017 #3

    Another issue brought about by Microsoft dropping support for SMB 1.0. It has broken network discovery of devices that use NetBIOS as a discovery method, brought forth authentication issues with certain machines, etc.

    Basically you are being forced to stop using WORKGROUP or if you do use it then mapping drives to network shares is the ONLY alternative or, resort to using HOMEGROUP which is less than desirable!

    You do have a third option, get yourself an AD server! Thanks Microsoft, how hard would it have been to bridge the gap here for users? You could have provided support for NetBIOS in SMB 2 and 3 but NO!
      My ComputerSystem Spec


 

Related Threads
I have two machines: a laptop (Zebedee) and a desktop (Dougal). A couple of days ago I found that the network shares from both machines were no longer visible in Explorer on either machine. I noticed this after Zebedee (but not Dougal) had been...
Hey All, After the recent Wanncry attacks I disabled SMB1 protocol as per the cautionary suggestions from Msft et al. Now I can no longer access my network shares via File Explorer. I am still able to access the network device using IP address...
I just switched to a new router (from DLink DIR-655 to TP-Link Archer C7) and now my Windows 10 Pro cannot see network shares nor can others on the network see its shares. Prior to the router switch, it could see shares and others could see the...
At Last!:) Tried signing in with a pin number today following a bunch of updates. Found my NAS server and other network shares. It may have happened with an earlier update but I kept signing in with full MS account as I needed to see shares
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...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:24.
Find Us