Windows 10: Cannot map shared network drive

I have just upgraded from Win7 Pro to Win10 Pro and have a problem with a shared network drive. Under Win7 and 8.1 I had no difficulty mapping this drive which is attached directly to my access point. However, since upgrade, I can log into the drive using a browser but cannot map it using File Explorer. Other network resources which are attached to my home router still work fine. Any ideas?

Thanks,
Mike

:)

 

Able to ping network path but not able to map network drive on Windows 10

So i ran into this situation today. Computer A (Windows 7 professional) and Computer B (Windows 10) both connected to same domain.

Computer A can access network drive, but computer B cannot

This is what i tried on computer B, which has Windows 10

Verified advanced network sharing settings are enabled

Verified computer B can ping network path, but unable to map network drive

flushed DNS. Tried browsing to network drive, no good

Tried accessing network path with IPv4 address, network path, but no success

Not sure why computer B can ping the network drive but cannot map to network drive

Also verified NetBIOS is enabled.

Are there any other troubleshooting steps that i missed or what else should i check on Windows 10 about mapping network drive?

 

Unable to Map a Network Drive in Windows 10

Hi Team,

When we are trying to access/Map a Network Drive we are getting an error mentioned below

Error:- Windows cannot access\\path\

When I clicked on diagnose it says problems found as:- file and print sharing resources(Netwok Drive address) is online but isn't responding to connection attempts)

But we are able to access/Map the same network Drive in Windows 7 OS environment.

what might be causing the issue.

 

Hi Mike, have you tried going to 'Control Panel -> Network and Sharing -> Change advanced sharing settings (on left)', and turn on 'network discovery' and 'file and printer sharing'?

 

Yes, that was one of the first things I checked. The shared drive (WD Mybook Live) is asking for a login and password to access it. The logins are computer names and there are no passwords. My Win8.1 machine sitting next to this one has no difficulty attaching.

 

Have you checked the 'Homegroup connections'? By default, Win 10 seems to want to be part of a homegroup to connect to all of your devices, but there is a setting that says 'use user accounts, and passwords' ... try that one.

 

Homegroup is on user accounts. We are in the same Workgroup. The computer name is built into the shared drive. In fact nothing else has changed except the upgrade. All the control panel options I know which may affect this are where they should be.

 

Now i'm stumped! I have three shared network locations, and they all worked after the upgrade.

 

FlyBoy check the post at https://www.tenforums.com/newreply.ph...reply&p=330519 and see if it resolves your issue.

 

Sorry, but no. My issue is not addressed in that post. I am not trying to share from one computer to another. I am trying to access a shared network drive (WD Mybook Live) which has its own IP address. I can get it from every computer in the house as well as my Android tablet. But I cannot attach to it with my single Windows 10 machine. When attempting to map the drive, after about a 1 minute wait, I get a Windows Security box asking for my login and password. This drive has no logins or passwords. It is open to everyone on the network. I've tried adding logins and passwords with no change. I have no difficulty logging into the web based interface of the drive from my W10 machine. So, I'm more than mystified.

 

I have the same NAS as you and my sharing works! Win 10 does apply tighter security measures as you have found out.

You don't need to map it but you have to make sure the username login is like this - mybooklive\username. Also tell that security box to Remember credentials.

As for the password, I would add one, especially if you intend to share it from the Internet! Mine has one and I am not sure, but I think win 10 will demand one.

Good luck.

Edit:- fixed error in username.