a) Why is that, when network connection is (connected or) enabled,
there is a long delay on opening local files, however on
using the direct path to files, local files open quickly?

b) Why is that, when network connection is (disconnected or) disabled,
local files open quickly (without using direct path)?

--
randall

Sometimes, this is related to a DNS or name lookup problem. When invoking a
file open process there may be another process performing some kind of DNS,
NetBIOS or name-server lookup (even though the file is local). When there
is no network connection, the lookup process immediately fails - thus, your
file opens immediately.

Some applications may also exhibit this behavior, but without knowing your
network config I couldn't say for sure. If this is a system that is used in
a network environment as well as a stand-alone environment, checked your
network-mapped drives or other network settings. Review your network
settings and see if all looks 'normal'.

If this system moves between networks )and maps drives on both) make sure
that only 'accessible' mapped drives are active when on either network (as
drives may be parsed during file operations and if not available, they will
slowly time-out).

Cheers!

"randall" <rwithrow@swbell.net.(donotspam)> wrote in message
news:22D106BA-00EF-4E27-B6AF-8A948AED06EA@microsoft.com...
> a) Why is that, when network connection is (connected or) enabled,
> there is a long delay on opening local files, however on
> using the direct path to files, local files open quickly?
>
> b) Why is that, when network connection is (disconnected or) disabled,
> local files open quickly (without using direct path)?
>
> --
> randall