Hi
Actually, a quick test shows it may recognize it if you are already logged under certain circumstances (though I haven't tried it with the PC hibernated beforehand / 'just woken' - but different PCs (NICs, etc) react differently anyway). So, it may be that it really is the drive 'sleeping' which is the problem. Or, the network infrastructure on your PC hasn't fully woken from sleep itself. If so, Windows is presumably giving up before one or the other is ready, which we can't do anything about 'internally'. You may find a Programs-Before batch file (or script) is necessary to wake the device (for example, by PINGing it). Or, try setting a delay in the Misc settings page (Expert mode)
Note that the underlying error is being returned to SBF by Windows either way. But dropping the mapping and using a UNC path may remove one hurdle ('resolving the mapping') from the process.
Actually, a quick test shows it may recognize it if you are already logged under certain circumstances (though I haven't tried it with the PC hibernated beforehand / 'just woken' - but different PCs (NICs, etc) react differently anyway). So, it may be that it really is the drive 'sleeping' which is the problem. Or, the network infrastructure on your PC hasn't fully woken from sleep itself. If so, Windows is presumably giving up before one or the other is ready, which we can't do anything about 'internally'. You may find a Programs-Before batch file (or script) is necessary to wake the device (for example, by PINGing it). Or, try setting a delay in the Misc settings page (Expert mode)
Note that the underlying error is being returned to SBF by Windows either way. But dropping the mapping and using a UNC path may remove one hurdle ('resolving the mapping') from the process.