I have some shares quick access in Windows explorer, but when I click on it it says something about the location was not accessible.
BUT, when I do win+R and \\NAS it gets the same error first time usually, but if I do it twice I do get access just fine. When that is done pressing the share in Explorer works just fine.
Restart of NAS also fixes it.
This has not always been the case, it worked fine some unknown amount of months ago.

 

Anyone know why?

Edited August 16, 20205 yr by Mihle

Try logging in via the GUI and spin the drives on the array up first before you try to access the shares with Windows Explorer.

29 minutes ago, Frank1940 said:

Try logging in via the GUI and spin the drives on the array up first before you try to access the shares with Windows Explorer.

I have them set to always be spinning.

If I didnt, they would be spinning anyway because no cache drives.

 

And accessing files via Nextcloud for example is the same as before.
I dont know if it is Unraid, SMB or Windows that causes it.

Edited August 15, 20205 yr by Mihle

It happens every time my PC starts basically.

First time when pressing it in Explorer:

But then if I wait some time (some sec) and click again then it works.
Same thing with Windows+R.
I suspect it is maybe a windows thing?

I have had this is the past.  I think it is some kind of race condition with Windows on Startup.   What could be happening is that when Windows attempts to connect to the server, the networking setup in Windows has not yet completed.  The other possibility is that the Antivirus/malware software has not completed its initialization process.  (I suspect that the Windows startup process is multi-threaded.)

 

I know it is extremely annoying if you have an Windows app that is attempting to connect with the mapped drive.  (I actually wrote a batch program to check that the drive was mapped before the app was launched!) 

 

In my case, when I later clicked on the drive, it would mount.  However, I can't recall ever trying it before the Boot process had completed.  (Win10 has the Desktop visible and working before it has finished booting completely.  Win7 appeared to complete the boot process before the Desktop would appear.  I suspect that is part of the reason why Win10 seems to boot faster...)

But how do I fix it?

In my case (apparently), one of the Windows updates 'fixed' it.  (It just started mapping at boot time one morning...)  Currently, I am on WIN10 1909. 

3 minutes ago, Frank1940 said:

In my case (apparently), one of the Windows updates 'fixed' it.  (It just started mapping at boot time one morning...)  Currently, I am on WIN10 1909. 

Well, I am running 1909 right now, for what I know that might be the one that broke it for me, who knows.

Edited September 5, 20205 yr by Mihle

2004 seem to have fixed it for now