Windows 10: Unable to access network drive in Explorer

I have a NAS (WD MyBookLive) which cannot be accessed in Windows Explorer on my brand new Surface by IP address (or name- though that doesn't work on any of my devices for some reason). I can access the config page in my browser by IP, and two other Win10 devices on my network can access the NAS by IP in Explorer fine, and I can access other devices on my network by IP fine on the Surface but for whatever reason only this computer can't access that NAS in Win Explorer.

I just got the Surface yesterday and was able to access the NAS fine, the only thing that's changed is I renamed the device and restarted and since then haven't been able to connect. I've restarted both the PC again and the NAS but no change.

:)

 

Mapping A WDMYCLOUD in Windows 10

I am unable to may me WDMyCloud as a network drive discoverable in explorer. The WDMyCloud is accessible through installed software, can be seen in files explorer, my is not selectable when trying to assign the WDMyCloud to a drive letter.

Any solutions out there?

 

PC Freezes when I run a Network Reset

BTW: the reason I tried doing a Network Reset in the first place was because I was unable to see a computer on my home network. I could access the other PC in Windows Explorer by typing \\ComputerName or by mapping a Network drive, but it would not show
up in Windows Explorer. I research this problem and the suggestion was to do a Network Reset. Not only did I have the problem of freezing, now I can't access the other PC at all!

 

There are Networking bugs in the latest update. Read all the posts on here. Some solutions we've discovered so far might work temporarily until MS fixes the problem.

 

Any particular post you recommend reading?

Also, after trying a few more things, it seems I get the "Windows cannot access" message trying to access the root of the NAS and one of the shares on it, however the other share (which is set to Public) prompts for a username and password. The other two devices on my network don't get that prompt, and since it's public there is no info to enter, I tried just leaving it blank but of course it comes right back.

I fixed the issue where other devices can't access the NAS by name (simply renaming it, then renaming it back to the original name), and now it doesn't even show under network. I can access other network devices in Windows Explorer on this computer though. If this were a networking issue caused by a Win update, I'd think it would affect all network devices I would attempt to connect to, not just this one

 

I have the same problem. I also have a MyBookLive. The difference between this device and other windows devices is that the NAS runs Linux, not windows. There is a problem with comms protocols.

We just have to wait till MS provides an update, but, in the meantime, you could create shortcuts to the NAS resources e.g. \\name. I have a shortcut for \\MYBOOKLIVE and when dbl clicked, it pops up the File Explorer window with shares displayed.

Meanwhile, we wait...........................

 

Ok that makes sense about Linux vs other Windows devices. Guess the other Windows devices maybe just don't have the same update my Surface does which is why they still work.

Manually typing the name/a shortcut doesn't work. I have a network drive mapped to the IP (from before I got the name issue fixed) and it doesn't work, typing the IP and name manually both say Windows can't access, check the name, network connection, etc.

Guess maybe I just won't be able to connect until they fix it. Hope it's soon!

 

Oh, damn, my \\NASname is giving the 80070035 error now as well.

That's another symptom - it comes and goes.

Grrrrrrrr

 

Same here. Got everything perfect then it all messed up by itself again. There appears to be both Networking and Firewall issues that are sporadic. I turned Firewall off today and it brought back the panel contents instantly. Turned it on and they were still there. That was the first time I tried Firewall on/off to see if it was a bug there also. On the next boot later in the day after lunch everything on the network was invisable again. Tried Firewall on/off again and everything stayed invisible. So that on/off worked in the morning but not in the afternoon.

This bug(s) has a mind of its own. It's become unpredictable and comical at this point.

 

Turning Windows Firewall off allowed my NAS to show up under Network, but it was prompting me to login to access either of the shares which are both Public, and by IP it wasn't connecting at all. Turned firewall back on and it's gone again. Firewall back off, now the IP shows in the list of Network devices but not the NAS name (and won't connect by IP or by name manually). Firewall back on, can connect to the root manually but get a login prompt. Off, gone again, back on and can't access it at all! Renamed the NAS due to issues with the name on my other devices, restarted the Surface (fw still off), can connect by name again. Firewall back on, still working (by name and IP)!

What a mess, but fingers crossed it keeps working. (And now it needs to restart for another update, hope this doesn't break it again!)

 

I think I kind of have the same/similar problem. I have two NAS drives, one is mybooklive and the other is an iomega hmnhd. I have mapped both drives so they show up as X and Z under 'This PC'. What I am finding is sometimes I boot, go into THIS PC and either the green bar along the top is filling up slowly or the drives will have a red x through them. Initial clicks on them say the resource is unavailable or in use or something along those lines. Even if I go into my network list the same can happen. Say after a minute or so they become available and all is absolutely fine. All the while my other devices such as Windows 7 laptop never have an issue accessing them.

It's a very intermittent and sporadic issue though. Most of the time all is fine. I think the pattern is if I reboot my machine or switch it off and turn it back on a few mins later the problem is more likely to happen. Generally if I switch off and then turn my machine on the next day then I will never see this issue. Maybe it's something to do with fast startup (which is pretty darned fast) or maybe just a glitch currently in windows 10. Perhaps it has trouble reconnecting to a NAS it was just connected to moments before. Not a huge issue as the unavailability isn't for very long when it happens. But it's sort of thing that makes me levitate towards preferring my older Windows 7 laptop just because it works much better overall. The new machine with Windows 10 is infinitely more powerful but all the little quirks just make me like it less!

 

After an update and reboot the NAS isn't showing in the list of Network devices anymore but my mapped drives still work, good enough for now! Fingers crossed it doesn't break again