Windows 10: Unable to map NAS drive

I have a NAS drive (WD My Cloud Mirror) that was originally set up and mapped to an older laptop of mine. I have not used this NAS drive in a while. I recently dusted off the drive and tried to connect it to my new laptop when I ran into difficulties.

The NAS drive is directly connected via ethernet cable to my laptop.

Laptop is running Windows 10 Enterprise 1809.

Laptop's IP address on the ethernet card is set to 192.168.1.1

I was able to retrieve the IP address of the WD NAS drive by using the arp command and it's set to 192.168.1.2

I have forgotten the name of the root share folder on the NAS drive.

The problem:

I am unable to map the NAS drive to my laptop. When I try to click on Network in Windows Explorer OR use the Map Network Drive option, I get a "Network Discovery is turned off" error.

To enable Network Discovery, I turned on / enabled all of the below

1. In Advanced Network Sharing, network discovery is turned on for Private, Public, Domain and All Networks

2. DNS Client, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host sevices are running

3. Network Discovery is checked in Windows Defender

4. Ran the following command as administrator netsh advfirewall firewall set rule group=”Network Discovery” new enable=Yes

In spite of this I get the "Network Discovery is turned off' error.

I am able to ping 192.168.1.2 in the command prompt and get a response.

Any suggestions on how to fix the error OR another way to access the NAS drive would be highly appreciated.

Thanks,

Adi.

:)

 

RPC error: cannot connect to NAS drive

Since upgrading from Win7(64) to Win10(64), I have been unable to connect to my NAS drive (\\NET_DRIVE). While I can see the drive in windows for mapping a drive, File Explorer and Network Sharing, when I try to map the drive, I get the following error:
\\NET_DRIVE is not accessible.... A remote procedure call (RPC) protocol error occurred.

• The NAS drive is connected to my WiFi router, not to a remote computer.
• The user profile I'm using has administrative rights
• This problem did not occur when running Windows 7. It started when I upgraded to Windows 10

How can I fix this so I can access my NAS drive?

 

Mapping network devices such as NAS drives.

Dear Support,

I am having a massive problem with finding NAS devices on my network so I map them as network drives.

I had not changed any network configurations, but now I do not see my NAS drives in the list under "Network", nor can I map my NAS drives.

My previous mappings are fine and work OK. However, even the drives that were previously mapped that work OK do not appear in the list for the options of mapping network drives now.

I am running Win 10 latest version on an Intel 7th gen CPU, wired Ethernet.

I have checked to see that all my firmware is up to date, including router, NAS, network driver. I have checked that sharing is on, and turned off firewalls, made my network type private. I have searched every forum and technical note, and tried every video
out there, but I am at the end of my tether with this problem.

The problem seemed to occur after updating Windows. Everything was working fine before, completely flawlessly.

I am basically now completely fed up with the situation, and my only option left is to move all my computers to Linux. The problem has basically cut off access to data I need to work and is costing me money and time. I basically just want to cry as there
is no solution anywhere that I find. The Windows update has broken my network.

If anyone has any answers, please let me know.

Thanks for your time in advance.

Kind regards, Ben.

 

Map NAS drive Windows 10

I see other people noting this issue but on Windows 10 I am no longer able to log into my NAS drive which is sitting on a WiFi router, I was able to do this easily from Windows 8, but sadly not after the upgrade. The issue seems to be the authentication
process that Windows 10 wants to use if you try and map the drive. I can see the NAS drive but just not able to log in. It looks like a domain issue. I have had a read of the posts and this seems quite common, but no workable solutions appear to be proposed
that I can find. Any suggestions?