Windows 10: Mapping as a network drive function not working properly

Hello,

I'm running a Windows 10 Pro 64bit desktop PC and I'm trying to map network drives. I have always been able to map them correctly using the IP Address of the drive and browsing. But for some reason recently (I realized I forgot to map a drive, so I went to add it) I have not been able to. I go to the network drive mapping wizard, type in the IP address and hit browse like I did before and the drive doesn't appear, other PCs I can connect to do, but not the drive. I also tried hitting finish instead of browse and it gives me an error of "Windows cannot access \\ Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve nbetwork problems, click diagnose." I diagnose, and it finds no issues.

When I try instead to map it as a network location, I type in the IP address and click browse, and the drive is there and can map as a network location. But not as a drive. And I have NO idea why. All network sharing is turned on, and I've been searching forums to try to find the solution and haven't found anyone with exactly the same problem yet. I've tried various things and still no luck.

:)

 

Windows 10 bug - USB Drive vs NAS drive mapping conflict

This is a well known long standing Windows issue. Windows does not properly exclude mapped network drives when enumerating USB storage devices. The best practice is to map network drives from the end of the alphabet to avoid it.

 

Windows 10 unable to map network drive Synolgy NAS

Just started having this problem over the weekend, not able to use "map a network drive" to map to my NAS shares even though it was fine previously. Tried everything on this thread with no success. Finally worked after downloading Synology Assistant
and using its map a drive function.

 

I have a network drive shared out on my router. I can map a drive letter to it using the drive mapping wizard by typing:
\\ <IP address of router> \ <share name>

Are you sure the drive you want to map is still shared out on the device you are trying to connect to?

I see this thread is marked 'solved'. Does that mean you have sorted it out for yourself now?