A
AlHolden
After my PC updated to Win 10 ver 2004 on 2-2-2021, my NAS device has been consistently unreachable by direct run or shortcut on each morning startup. Windows says the device is simply not there.
The "fix" has been to restart Windows entirely, at which point it works fine.
(fyi restarting the Server daemon alone does not resolve the problem)
The link was created under Network Locations long ago, referenced by name and mapped to the G: drive via SMB (I presume). All other protocols (TCP, FTP, DLNA) work fine, only the NAS under Samba fails after a cold start.
Can anyone advise the correct fix for this specific problem? Various solutions are posted for other problems that come close, but they are for others Windows versions (like 7) and slightly different symptoms.
That or I'm lousy at searching this site ;-]
TIA, AL
Continue reading...
The "fix" has been to restart Windows entirely, at which point it works fine.
(fyi restarting the Server daemon alone does not resolve the problem)
The link was created under Network Locations long ago, referenced by name and mapped to the G: drive via SMB (I presume). All other protocols (TCP, FTP, DLNA) work fine, only the NAS under Samba fails after a cold start.
Can anyone advise the correct fix for this specific problem? Various solutions are posted for other problems that come close, but they are for others Windows versions (like 7) and slightly different symptoms.
That or I'm lousy at searching this site ;-]
TIA, AL
Continue reading...