Hi All,
When I map network drives (from my computer to other machines on the network), it is very often the case that at some point some of these other machines will be turned off, then logged back in at some later point.
So the problem is, when I click on the drive in Windows Explorer and the machine happens to be turned off, Windows explorer completely locks up with an hourglass until Windows finally figures out that the machine is off. This seems to be a full 60 seconds.
My question is, why does it take Windows so long to figure out the simple fact that the machine is not reachable? Even if the connection were via a 2400 modem and the machine an ancient 386, I would think that it would take a minimum of a couple of seconds to get a 'yes' or 'no' as to whether the machine is reachable. Is there some timeout setting in the registry that I can set to reduce this monumental annoyance?
Thanks,
--Jim
When I map network drives (from my computer to other machines on the network), it is very often the case that at some point some of these other machines will be turned off, then logged back in at some later point.
So the problem is, when I click on the drive in Windows Explorer and the machine happens to be turned off, Windows explorer completely locks up with an hourglass until Windows finally figures out that the machine is off. This seems to be a full 60 seconds.
My question is, why does it take Windows so long to figure out the simple fact that the machine is not reachable? Even if the connection were via a 2400 modem and the machine an ancient 386, I would think that it would take a minimum of a couple of seconds to get a 'yes' or 'no' as to whether the machine is reachable. Is there some timeout setting in the registry that I can set to reduce this monumental annoyance?
Thanks,
--Jim