Windows 10: I cant connect to network drives

it was working back on 10049 and then i updated to 10051 and it still was working fine. but recently i did a fresh install and now i can re add a network device

i have a "New" Nintendo 3ds and i cant setup the MicroSD management which requires you to add it as a network drive

like \\N3DS

in the network tab i can see it but when i click it it says

windows cannot access \\N3DS

error code 0x80070035
the network path was not found
upon clicking troubleshooting the problem says
the remote device or resource wont accept the connection..

can i fix this?

:)

 

Unable to connect to all Network Drives. How can I stop it happening.

Hi Gerald,

Thank you for posting your query in Microsoft Community.

I understand the inconvenience you are facing currently.

I would appreciate if you can provide us the following information to help us understand the issue better.

Is the machine added to the domain?

If it is on a domain, then, your query would be better suited in the TechNet forum. Please post your query by following this link:

Technet forums

Hope the information helps. Please let us know if the issue persist and we will be happy to assist you further.

 

Unable to connect to all Network Drives. How can I stop it happening.

A green notice Unable to connect to all Network Drives appears and stays despite all attempts to remove.

How can I stop it happening.

Original title: Network Connection Notice

 

Shot in the dark . . . I've been having trouble with Internet since 10041 and this morning . . .

Go to Device Manager and see if your "Bluetooth" shows to not be working properly. I updated mine and I'm finally back in good business.

 

I've now got the same problem with 10049. It was getting to my NAS 4 days ago but since then it can't see a darn thing except itself. It seems to be a name server problem. The command, net view, comes up with nothing.

I have another desktop with 10041 on it and it is networking fine. A difference I can see is that the 100041 has 'NetBIOS over Tcpip' enabled (seen with ipconfig /all) whereas 10049 has it disabled.

The problem is compounded by the inability to alter the properties of the NIC in 10049. I have tried a couple of command line 'fixes' to no avail.

Pretty frustrating, especially as it was accessing the NAS up to four days ago.

Sorry I couldn't help you but at least you are not alone!!

Maybe peeps with a working network could check whether their NetBIOS over Tcpip is enabled and reply.

TIA.

 

Things have improved after rebooting both routers. I can see other shared resources but I have a problem with my NAS so I will have to investigate further.

As an aside, turned off NetBIOS over Tcpip on my 10041 system and it still was able to see shares. Net view list blank.

 

i also tried at my workplace and i cant connect to any to any network PC's or servers

 

Just turned my 10041 machine on and it now can't see the NAS! Pretty frustrating trying to figure out what it is that is causing the problem with the MyBookLive. Being Linux may have something to do with it??

Oh, well, just have to hope the networking gets better in the next release.

 

Are you seeing the shares? Do you get error messages when trying to connect?

 

Yep,I can see the network devices just fine but I can't connect

 

Let's hope the next release solves your issues. Mine is OK now, but don't know what the problem was I had earlier.

 

Have you tried updating firmware on your WD?
How did you fix it?

 

Yes, certainly checked the WD version. It updates itself, anyway.

Not sure what fixed my sharing problem. It was OK up till 11 Apr so I restored my machine back to 7 Apr and all came right. So it must have been something altered in my PC - weird that it only affected the NAS, though.

Anyway, all backups to the NAS are going fine again.

 

I'm seeing the same issue here. All of my Synology NAS shares haven't been reachable by my Windows 10 clients for a couple of weeks. I should add that this issue only exists for me over wireless connections. As well, my other windows server shares seem ok so this seems to be isolated to Synology shares (Linux\Samba?) only for me. Also, if I connect using an Ethernet cable then the shares are available again.

As others have mentioned, this is difficult to fix/troubleshoot given we don't have access to the Network Properties of our connection.

I've experienced this on an Asus N53SV Laptop and Surface Pro 3 running Windows 10. I had to restore my SP3 to Windows 8.1 as I needed wireless access to the shares from one of these clients.

Finally, I only run released builds and have upgraded to each new one as they've been released. Hopefully, a fix or new build will take care of this issue as a re-install from an ISO would take me a while given all my required apps.

 

Welcome to the forum, cipher. My main machine is cabled and now is fine with the NAS but I also have an older Toshiba laptop (win 10049 ISO install) on wifi and it is not seeing the NAS. I thought it was seeing it a few days ago, though!

A lot of us are keen to see the next release! Hopefully the network/sharing code will be in better shape.