Mounting a network share as a folder, not as a drive

Is it possible to mount a network shared resource as a folder and not as a
drive? Suppose there was a network share on computer A named "documents".
I want to mount it on computer B as C:\documents, and not as E:\. Help?

I answered this in the other newsgroup.
Just create a shortcut to the folder and name it anything you like.

"Jibba Jabba" <(E-Mail Removed)> wrote in message
news:CMeVb.18607$(E-Mail Removed) link.net...
> Is it possible to mount a network shared resource as a folder and not as a
> drive? Suppose there was a network share on computer A named "documents".
> I want to mount it on computer B as C:\documents, and not as E:\. Help?
>
>

"Rob Elder, MVP-Networking" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I answered this in the other newsgroup.
> Just create a shortcut to the folder and name it anything you like.

Doesn't work for me. The whole point of mounting it as C:\documents\ is so
that in the future, if I run out of disk space, I can just mount more space
from other servers onto subfolders within the C:\documents\ folder.

When you install another hard drive, in disk manager instead of assigning it
a drive letter, mount it to an NTFS folder (would have to be a subfolder of
C:\Documents in your example).

"Jibba Jabba" <(E-Mail Removed)> wrote in message
news:dzfVb.18664$(E-Mail Removed) link.net...
> "Rob Elder, MVP-Networking" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I answered this in the other newsgroup.
> > Just create a shortcut to the folder and name it anything you like.
>
> Doesn't work for me. The whole point of mounting it as C:\documents\ is
so
> that in the future, if I run out of disk space, I can just mount more
space
> from other servers onto subfolders within the C:\documents\ folder.
>
>

"Brendon Rogers" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> When you install another hard drive, in disk manager instead of assigning
it
> a drive letter, mount it to an NTFS folder (would have to be a subfolder
of
> C:\Documents in your example).

That's not what I'm doing. I'm adding a network shared folder, not a local
hard drive.

Setup a DFS namespace. You can connect to it with \\DomainName\RootName -
the folders can be located on multiple servers anywhere on the network and
target folders can be configured to failover to replicas.

See: http://www.microsoft.com/windowsserv...rview/dfs.mspx

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP


"Jibba Jabba" <(E-Mail Removed)> wrote in message
news:LShVb.19007$(E-Mail Removed) link.net...
> "Brendon Rogers" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > When you install another hard drive, in disk manager instead of
assigning
> it
> > a drive letter, mount it to an NTFS folder (would have to be a subfolder
> of
> > C:\Documents in your example).
>
> That's not what I'm doing. I'm adding a network shared folder, not a
local
> hard drive.
>
>

"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Setup a DFS namespace. You can connect to it with \\DomainName\RootName -
> the folders can be located on multiple servers anywhere on the network and
> target folders can be configured to failover to replicas.

Can a DFS client (the one exporting the drive space to the main server) be
Linux or does it need to be another Windows machine?

Dunno for sure, but probably. I think any share which can be accessed by
UNC path from the DFS Root server can be a DFS link. The DFS Root Server
must be NT4.0 Server, Win2k Server, or 2003 Server. Auto replication
requires Active Directory and NTFS. However, a non-replicating DFS link can
be created on a FAT32 partition on Win2k Pro - so I would guess you could
create a DFS link to a Linux machine.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Jibba Jabba" <(E-Mail Removed)> wrote in message
news:ObCVb.20346$(E-Mail Removed) link.net...
> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Setup a DFS namespace. You can connect to it with
\\DomainName\RootName -
> > the folders can be located on multiple servers anywhere on the network
and
> > target folders can be configured to failover to replicas.
>
> Can a DFS client (the one exporting the drive space to the main server) be
> Linux or does it need to be another Windows machine?
>
>