Share via

Network attached storage not appearing in Windows 10 Network since recent update

Question

Thursday, December 21, 2017 1:15 PM | 1 vote

Since the Windows 10 Creators update my home network PCs all show different items in the File Explorer Network pane.  On the network I have 2 x NAS boxes and 3 x Windows 10 laptops, call them A, B and C.  When all 5 devices are on I get the following results:

PC A with Windows 10 Home shows all 5 devices

PC B with Windows 10 Pro shows itself and PC C only

PC C with Windows 10 Pro shows itself only

This is a home network - I don't want to have to map network drives on each PC, I just want all the devices to show on all PCs as they did before this Win 10 update.  And I don't want to have to type \<NASname> into the address bar to access the files on either of the NAS boxes!  Any help would be greatly appreciated.

All replies (6)

Thursday, December 21, 2017 9:58 PM

same problem here..

No solution yet

Thursday, December 21, 2017 11:14 PM | 2 votes

Hi GeoffD33,

(1) check if connection is OK by PING:
    in command prompt, type ping <IP address> of NAS

(2) use IP address, instead of <NASname>, for mapping network drive.

(3) check if SMB 1.0 active:
   [Control Panel] > [Programs and features] > [Turn Windows features on or off] (top left corner of window) >
   

Regards,

Ashidacchi

Friday, December 22, 2017 10:50 AM | 1 vote

Hi ,

Firstly, I suggest that you disable Fast Boot to check if it is helpful.

https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

After upgrade to Windows 10 1709 version, some people met the issue. It always could be caused the SMB 1.0 and Master Browser. SMB1.0 is not installed by default in Windows 10 1709。

If you make the NAS the Master Browser and disable the browser on ALL the Windows machines, shut down the Windows machines and reboot your router to check.

Also it could be caused by permission. You could follow the steps in the link below.

https://appuals.com/fix-cannot-access-network-shares-after-update-1709/

Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Hope it will be helpful to you

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Friday, December 22, 2017 11:13 AM

SMB1.0 was indeed not turned on. However, turning it on did not solve the issue. The group policy setting was the problem for me. 

Another workaround is to edit the group policy for insecure logins. Do note that the group policy editor is a powerful tool and changing keys which you don’t know about can make your computer unusable.

  1. Press Windows + R to launch the Run application. Type “gpedit.msc” in the dialogue box and press Enter.
  2. Once in the editor, navigate to the following path:

Computer Configuration > Administrative Templates > Network > Lanman Workstation

  1. At the right side, you will see an entry named “Enable insecure guest logons”. Double-click it to change its properties.
  1. Change the option from “Not Configured” to “Enabled”. Press Apply to save changes and exit. Now restart your computer and check if the problem got solved.

Sunday, December 24, 2017 5:59 PM

This solved my problem.  The drivers were missing after a recent update by Windows, so I ask the question: How would a person who is not willing to investigate and has some computer savvy solve this problem?

I spent several days looking for an answer and this is the first place that presented the SMB fix.  THANK YOU!

Todd

Wednesday, January 8, 2020 11:57 PM

    I have tried everything and this made it happen! Wish I would have seen your comment firstly but in the end we got it................THANKS BUDDY!

Computer Configuration > Administrative Templates > Network > Lanman Workstation