Windows 10: Can't connect to network drives

Hi,
I recently lost access to my 2 network drives. Both are connected to the router via Ethernet and I myself am connected to the router via Ethernet as well. Internet access is not a problem nor is file sharing with my girlfriend's laptop connected via Wifi.

I doubt it's router-related because my girlfriend still has access (via Wifi) to the 2 NAS. Although, I'm not sure but I think the problem started maybe after yesterday's Windows update but for which I can't find much useful information about: KB4087256 & KB4074588 (Security Update). Another reason I feel it might explain something is that my girlfriend has been unable to update her Win10 laptop for a while now because of lack of space so she doesn't have this latest update.

There where the difference is very visible is when clicking 'Network' in Windows File Explorer. I no longer have my 2 NAS show up as 'Computer' and am therefore unable to browse them and map a drive letter to them.

This is the way it looks on my PC now (look at top row):





And this is my girlfriend's view from her laptop (those 2 other items in the top row are the NAS):



Any idea what could be wrong?
Thanks!


:)

 

Unable to connect to mount network drives to my computer from my IBM AIX server

Hi jake,

I suggest you to post your query in
TechNet forum which is better suited for the issue. Thank you.

 

Cannot connect to network drives after Windows update on 2-13-2018

Yes it is called the Network public folders, copy or move them there.

C:\USERS\PUBLIC

any folder here or create folders here or just copy or move anything anywhere in this folder

OR

Right click on an item and in properties>Sharing Tab, use the advanced sharing at bottom for network folders and files and select to share and change permissions to full control if you want more than just read permissions.

That's it

 

Have you tried typing the computer name or IP in " File Explorer "

EG:
Code: \\PCH-A100[/quote] or
Code: \\192.168.x.x[/quote]

 

Tried now and I get this error:

 

Some folks have fixed it [including myself] by going to Control Panel, Programs and Features, and in Turn Windows features off or on assuring a checkmark is in SMB 1.0/CIF but also unchecking the sub entry of Automatic Removal. Having that SMB 1.0 unchecked is a default of latter updates.

 

If the machine name isn't decoding properly it's fair (and reasonable) to suspect NetBIOS name resolution problems. You could cobble up a quick LMHOSTS file to see if that's what's causing your problem. You'll need to look up the IP addresses for those two devices -- namely PCH-100 and V00-USB -- for this to work. For the following example, I'm going to give the first one an address of 192.168.1.17 and the second one an address of 192.168.1.18 (when you see <tab> use a TAB character instead).

192.168.1.17 <tab> PCH-100 <tab> #comments are OK, but must be preceded with hashmark
192.168.1.18 <tab> V00-USB

Save the file in your text editor as "LMHOSTS" (no extension) into the Code: C:\Windows\System32\Drivers\etc[/quote] folder. In fact, you should find a sample LMHOSTS file there named LMHOSTS.sam. Here's a nice tutorial on all the details: Easily Edit the Hosts File in Windows 10 - Petri.

If this doesn't work -- and it very well might not -- there's more than simple NetBIOS name resolution problems involved. Indeed, turning SMB 1 back on (it's off by default in Win10 now) might help. There are lots of other fixes to try, too -- a distressingly large number, in fact!
HTH,
--Ed--