A central computer in the workgroup has 3 folders
shared. 2 desktop computers and 1 notebook all connect to
these shares by way of drive mapping.

It will show mapped drives in My Computer, but the drive
properties (space used and space free) do not identify
correctly. After you double click on one of the "drives"
to explore the contents, the drives properties then
become available. This happens for all three drive maps.

I use the Mapped drives to hold my .PST file and other
data files used by applications. The applications fail to
use the file until the drive has been "explored" after
that everything works fine.

I have a similar problem where the network icon is "X'd out... anyone with any ideas??


"(E-Mail Removed)" wrote:

> A central computer in the workgroup has 3 folders
> shared. 2 desktop computers and 1 notebook all connect to
> these shares by way of drive mapping.
>
> It will show mapped drives in My Computer, but the drive
> properties (space used and space free) do not identify
> correctly. After you double click on one of the "drives"
> to explore the contents, the drives properties then
> become available. This happens for all three drive maps.
>
> I use the Mapped drives to hold my .PST file and other
> data files used by applications. The applications fail to
> use the file until the drive has been "explored" after
> that everything works fine.
>

I have the same issue... anyone have any ideas how to solve this problem?
cmon

"(E-Mail Removed)" wrote:

> A central computer in the workgroup has 3 folders
> shared. 2 desktop computers and 1 notebook all connect to
> these shares by way of drive mapping.
>
> It will show mapped drives in My Computer, but the drive
> properties (space used and space free) do not identify
> correctly. After you double click on one of the "drives"
> to explore the contents, the drives properties then
> become available. This happens for all three drive maps.
>
> I use the Mapped drives to hold my .PST file and other
> data files used by applications. The applications fail to
> use the file until the drive has been "explored" after
> that everything works fine.
>