Windows 10: Unable to connect to mapped drives

Well, not exactly. I have NAS drives and mapped them just like I did on my Windows 7 laptop. It all works fine and the NAS drives show up just fine in network link too. Everything is Ethernet connected. But I see anomalies. If I reboot my machine, or even turn it off and switch it back on fairly soon after then I occasionally get a message about one of the drives being unable to connect. So I then go to 'this pc' and see a Red Cross through one of the drives. If I double click it then it either connects instantly or I will get the green bar filling for about 20-30 secs before it connects. I only have to do it once as after that access is instant every time I go to it. Now this doesn't happen all the time and it never happens if I turn the machine off and start it up after leaving it alone for an extended period. It just seems to be more likely after doing a restart or turning back on within minutes of it last being on.

but I do also notice that when I am in outlook and someone sends me a file (such as jpg pic) that I want to save to my NAS drives. I will click the attachment and select ' save as' and navigate to one of the NAS drives and it will not browse its contents straight away, you can kind of see it trying to open up and eventually after a few seconds it suddenly responds. And again it only occurs once, subsequent navigations all react instantly , for example I go into a second attachment to save down. It's hard to explain but I am inclined to think Windows 10 is just plain buggy . It's not as if the networking is a complete fail. It works but it's just unpredictable. My other Windows 7 machine (which I will never ever let Windows 10 get into it) behaves flawlessly with the NAS drives. They are always live and instantly accessible to it regardless of whether the machine has recently been on or restarted.

I dont think there are really any answers here as it's just seemingly a Windows 10 'thing' and maybe in future builds things will get better. I just wanted to share my observations in case anyone else is tearing their hair out over things like this. Sometimes it's re assuring to know your not alone!

cheers, Wayne

:)

 

Unable to set up mapped drives on my own PC or use previously mapped drives

I am a Microsoft Access developer whose customers often use mapped drives. To be able to develop my apps to fit their setup, I set up mapped drives on my own computer with the same drive letters as they have, but have now hit some problems and I'm afraid
my explanation will be a bit vague in terms of the timing of when things went wrong. Some mapped drives (corresponding to customers I no longer have) stopped working a while back (as observed by a big red X in File Explorer), but I postponed sorting them out
since they were no longer customers. I was still able to map a couple of new drives on my machine corresponding to those used by a new customer (I think that was the order of things). Those new drives now don't work, but that may be due to me now using Dropbox
Business which has changed some things around and they were mapped to folders in Dropbox.

However, and this is the main point, I can no longer map any new drives to shared folders on my PC. I can share folders using "Give access to" from File Explorer (I'm on Windows 10 Fall Creators Update), but when I try to map that shared folder I get the
following error message:

Problems found

file and print sharing resource (ALAN-PC) is online but isn't responding to connection attempts

Clicking on "See details" tells me, "Error code: 0x80070035. The network path was not found." and clicking on "Diagnose" just gives me the original error message above.

I've tried sharing the folder again ( C:\TestShare) and when I do that I am assured that "Your folder is shared" and when I click on "Show me all network network shares on this computer" I am shown all the folders I have previously shared, but if I double-click
on the folder I just shared, I get "Windows cannot access \\ALAN-PC\TestShare". Again I get the option to Diagnose, but clicking that just gives me the original error message above. I get the same message if I click other items at Network > ALAN-PC in File
Explorer.

Note one customer required that I log into his system using WatchGuard Firebox SSL VPN, so I have an extra item under Control Panel > Network and Internet > Network Connections, but that works OK when I connect and my problems started occurring sometime
after this was installed so I don't think this is the problem. I also have a vEthernet (Default Switch) item from when I was using Hyper-V several months ago.

I would be forever grateful if someone can show me what I need to do to be able to map drives on my own PC once again.

 

Unable to set up mapped drives on my own PC or use previously mapped drives

Panic over. I found https://support.microsoft.com/en-us/help/10741/windows-10-fix-network-connection-issues and got part way through this. One of the early items sorted me out and I can now map my drives again.

 

10 is not buggy. Just that you have to treat it like a new car, and not go overboard on making a bunch of huge changes, that can cause any OS to break.

Unless you are physically running Windows 10, there is really nothing that we cannot answer, that has already been stated in various threads on this site. If you are having issues with Windows 7, I suggest that you go to sevenforums.com.

 

Thanks for responding. Unfortunately I would say 10 is quite buggy (no OS is totally bug free). The high level of posts shows that. We fired up my mother in laws laptop running 10 to test and observed similar behaviour. The fact that 2 machines running Windows 7 and an older laptop (now sold) running vista doesn't do this points at Windows 10 being the issue. Also we have iOS devices/media servers/tv streaming boxes whilst all different OS but none of them displaying this intermittent access issue to the NAS shares it again singles out 10.

Cheers for the pointer on Windows 7 but no need to suggest sevenforums.com, I have no issues with 7, it's a great OS. Just mentioned 7 as a comparison.

cheers, Wayne