Sounds like Windows Task Scheduler security token issues. Sometimes deleting and re-creating the Tasks helps, but once it starts, it often recurs (sometimes for a few runs, sometimes for just one, etc)
It's odd that it occurred on 2 PCs but not the 3rd (and with a mix of OS's too) but coincidences happen. So do Windows Updates...
Have you added credentials for the NAS to the Destination boxes on the Network settings page in the profiles? Experiment with format, as indicated. You might also want to experiment with toggling which are tried first ('supplied' in the profile versus 'implied' i.e, those the Scheduler logged in with) on Network > Advanced page. Don't ignore this, as sometimes devices where you try the wrong one first 'sulk' thereafter, and won't talk to anyone![:)]( "Smile")
Also check you don't have the option 'Do not store password' checked in your Scheduled Tasks. That should in fact stop network access at all, but sometimes it's flaky (and may also depend if there is an open connection to that resource already on that system)
It's odd that it occurred on 2 PCs but not the 3rd (and with a mix of OS's too) but coincidences happen. So do Windows Updates...
Have you added credentials for the NAS to the Destination boxes on the Network settings page in the profiles? Experiment with format, as indicated. You might also want to experiment with toggling which are tried first ('supplied' in the profile versus 'implied' i.e, those the Scheduler logged in with) on Network > Advanced page. Don't ignore this, as sometimes devices where you try the wrong one first 'sulk' thereafter, and won't talk to anyone
Also check you don't have the option 'Do not store password' checked in your Scheduled Tasks. That should in fact stop network access at all, but sometimes it's flaky (and may also depend if there is an open connection to that resource already on that system)