Windows 10: Occasionally unable to see NAS drives in home network, Win10 64-bit

Win 10 64-bit. Paired Drobo 5N2 NAS. These two units (synched with a master and slave) are attached through my home network. Every once in a while, the master unit will become undiscoverable in File Explorer. It remains "ping-able". The resolution of the problem is to reboot, and then, usually after a few minutes, the unit becomes "visible" again. How do I begin approaching how to solve this problem?

Thanks
Ken K

:)

 

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?

 

Windows 10 lost network drives

Windows 10 reset and now all NAS devices are gone. They showed before reset. Win 10 64 bit with all current drivers. NAS devices are visible and usable from other network devices, as they were prior to reset. Home Group joined and discovery set to
on. How do I get the drives back?

 

Have you put a ticket in with the company to see if they are aware of the issue. Have you updated to the latest firmware for the units? Can you use the Dashboard app? Are you using any kind of third party Internet Security software on your computer? Always check the support side of the product first, since they are going to have the most up to date info on any issues.

 

Ticket-yes
Latest firmware-yes
Use dashboard app--ye
Internet security software-yes. Malwarebytes and Windows security.

 

When rebooting, the system has to find out who is master and slave for how Samba is set up. If you have the username and password in Windows Network passwords, you have mapped folders set to reconnect, the systems should connect once they get a wakeup. I usually boot up and go grab a cup of coffee, then log in and I am in. The only thing that has to access my NAS on a regular basis is my Macbook for Time Machine. Otherwise the NAS is there for any backups once a day for our NVIDIA Shield.

 

What I have done is to map the drives. As I understand it, the drives will be attached at boot, as opposed to waiting for polling by a network service. I will see how that goes and get back in a few days unless something untoward happens. Thanks, KK