Windows 10: NAS Drive Inaccessible

I am having a problem with NAS Drives and mapped drives on my Windows 10 Home laptop and a Windows 10 professional desktop My Arkara NAS mapped drive gives the error An error ocurred while reconnecting Q: to \\STORAGE-OC60\LDevlin Microsoft Windows Network The local device name is already in use The connection has not been restored My Linkstation LS-WL478 NAS mapped drives give the error The specified network name is no longer available My DLINK-939329 NAS Drive is working properly The only thing that gets them back is deleting all maps and redoing them.

:)

 

Windows 10 2004 user credential protected NAS folders inaccessible

Windows 10 2004
WD My Cloud PR4100 NAS

I believe this is related to the Windows 10 2004 update. Since the upgrade, I can no longer access credential protected folders on my NAS

I can access the NAS itself. I can get a list of folders using file explorer just fine. Win+R > \\wdmycloudex4100 (ignore the name I kept it the same after an upgrade for convenience) no problem.

I can access Public folders on the NAS fine. However, when I try to access my previously accessible user credential folders (ones that require a user id & password that is setup on the my cloud) I get "access denied" and am queried to reenter my credentials to which I do.

But I receive this pop-up:




I tried:
Going into Windows Credentials and erasing my saved wdmycloud user credentials.
Created a new set of credentials on the NAS and tried those credentials.
I tried reenabling SMB1 (though shouldn't have to since the my cloud is supposed to be SMB3 capable). Didn't work anyway.




SMB3 listed in the NAS Settings:




Any other ideas?

- - - Updated - - -

Nevermind, figured it out.

To help other users: I had mapped drives set up to the NAS. There must have been some kind of credential caching for those mapped drives which wasn't listed in Windows Credentials and was preventing new credentials from being accepted by Windows 10 2004. Presumably disconnecting the mapped drives allowed fresh (even though they're exactly the same) credentials to be accepted rather than rejected by Windows. I was then able to remap the same drives again and it's all fine.

Excuse me while I go and re-disable SMB1. *Wink

 

Windows 10 & NAS Box

Hi Peter,

A few possible reasons can cause this issue. To help us identify the cause of this problem, we would like to know the following information:

• How is your NAS box connected to your computer? (Ethernet, Wi-Fi, or USB)
• Are you using a program provided by the manufacturer of your NAS box to access it?
• Do you receive any error messages when accessing your NAS box? If yes, what is the exact error message?
• What troubleshooting steps have you tried so far?

In the meantime, we suggest that you perform the solution provided by omiklik (Most Helpful Reply)
in the following thread: Unable to see NAS drive on Network - Win 10 PC.

Keep us updated on the status of the issue, and we will be glad to assist you further.

 

Problem accessing a NAS drive


I have 2 NAS drives and 3 computers in my home network. The NAS drives and one PC are Ethernet-connected to a router/wireless access point; the other 2 PCs use wireless connections. All 3 PCs can access one NAS drive with no problem. The drives show up in the Network section of File Explorer, and if I click on the NAS's icon all it's shares are displayed (whether or not the PC has credentials to access the shares). The shares on the other NAS drive can be seen by only 2 of the PCs.

On the failing PC the inaccessible NAS drive shows in File Explorer, but if I click on it I get




However, on that same PC, Firefox can access the FTP server on the NAS drive



so Windows obviously has no trouble communicating with the NAS. And Windows must be configured to allow communication with a NAS in general or it could not successfully connect to the other NAS. (Those two screen snips were stored on that working NAS.)

The problematic PC doesn't really have to reach the NAS, but I would like it to, and I'm frustrated that I can't figure this out. Anyone have any suggestions?

BTW, the error popup says I should ask the administrator of the server about this. I would, but I'm not speaking with myself at the moment.