P
Paul
Guest
Users on my W2K3 domain are experiencing the following problem: Their logon
scripts map multiple shared drives, all from a single Network Appliance
fileserver. The mappings include H: (their home directory), P: (public
share), and G: (groupdata share), etc.
The problem occurs when a user enables offline files on their PC, and
configures their home directory (mapped as H to synchronize. The
synchronization works fine, BUT when the user attempts to access the other
shared directories, such as P: (public), or G: (groupdata), they see only
the empty root folder of that share, none of the subfolders or contents,
even though the drives have multiple subfolders and files, and were mapped
at logon. If I disable synchronization of the H: drive, all of the contents
of the mapped P and G drives magically are once again visible and available,
so permissions are not an issue. If you attempt to manually map one of these
drives while synchonization of H: is enabled, you receive an error stating
the "network drive is not found", almost as if the user is working offline,
but they are working online.
I have seen this issue on client machines on my network in the past, and the
problem does not affect all systems, only some. So far, I have been unable
find anything to help resolve it. It's been an ongoing issue for more than a
few months. Any input at all is greatly appreciated.
scripts map multiple shared drives, all from a single Network Appliance
fileserver. The mappings include H: (their home directory), P: (public
share), and G: (groupdata share), etc.
The problem occurs when a user enables offline files on their PC, and
configures their home directory (mapped as H to synchronize. The
synchronization works fine, BUT when the user attempts to access the other
shared directories, such as P: (public), or G: (groupdata), they see only
the empty root folder of that share, none of the subfolders or contents,
even though the drives have multiple subfolders and files, and were mapped
at logon. If I disable synchronization of the H: drive, all of the contents
of the mapped P and G drives magically are once again visible and available,
so permissions are not an issue. If you attempt to manually map one of these
drives while synchonization of H: is enabled, you receive an error stating
the "network drive is not found", almost as if the user is working offline,
but they are working online.
I have seen this issue on client machines on my network in the past, and the
problem does not affect all systems, only some. So far, I have been unable
find anything to help resolve it. It's been an ongoing issue for more than a
few months. Any input at all is greatly appreciated.