Mapping to its own folder

  • Thread starter Thread starter Norman Risch
  • Start date Start date
N

Norman Risch

I am trying to help someone setup a consistent mapping in his
peer-to-peer XP network. We need to map a newly created set of nested
folders on his workstation/server both to other machines and to itself.

I know that earlier versions of Windows required using SUBST.EXE instead
of allowing network style mapping on a server machine. But I thought
that XP now didn't require that old DOS trick, and now unified the
network mapping technique.

We create the nested folders on the C: drive, and then set their
availability on the network. Then, on the server, we map a drive letter
to the parent folder, as is our intention on the other machines.

We are finding that each nested folder created on the C: drive needs to
have its permission set to allow it to be accessible, but even then, the
folders appear to be inaccessible or write-protected.

Should we just create the parent folder on C:, set its accessibility,
map to it on the server, and from the mapped drive, set the other nested
folders?

Are there any tech notes or other help screens on this?

Thanks
 
I haven't tried doing this, so have no experience to share, but NTFS is
richer in facilities than earlier filesystems, and allows you to mount local
and remote folders anywhere within the folder hierarchy. See:
http://support.microsoft.com/default.aspx?scid=kb;en-us;205524 for more
details. I've used linkd.exe once, and found it easy enough to use. I'd
guess you'd use linkd for the server, and mountvol for clients. (these are
guesses!). I still use subst !
 
Back
Top