Steps to reproduce the problem
Note You must have two computers to follow these steps.
- On a Windows Server 2003-based computer
(Server1), create a folder structure that resembles the following:
C:\DFSRoot\F1
- Open Disk Manager, and then mount a hard disk in the C:\DFSRoot\F1
folder.
- In the DFS snap-in, create a stand-alone DFS root. Set the
root folder as C:\Data and use the following parameters:
Server Name = Server1
Root Name = Data
Folder to Share = C:\DFSRoot
- Try to create a DFS link
(DFS folder) from the DFS root that you created. Use
the following parameters:
Link Name = F1
Path of target = \\Server2\Share (The target path can be any share. It is irrelevant to the scenario.)
Expected result: The DFS link is created.
Actual result: You
receive the error message that is mentioned in the Symptoms section.
Note You
cannot
create
a DFS link
under a mount point.
However,
you
can create a "DFS link target" to
a folder that is at, under, or before a volume mount point.
In other words, a "DFS link target" can be any UNC path that resolves to a
directory. In
order to demonstrate this scenario, consider the following example:
- On Server2, you create a folder structure that resembles the
following:
C:\Data\F1
- You open Disk Manager, and then you mount a hard disk in the
C:\Data\F1 folder.
- You create an additional C:\Data\F1\F2 folder under the mounted
drive, and then you share C:\data, C:\data\f1, and C:\data\f1\f2 to the following corresponding
shares on Server2:
- \\server2\data
- \\server2\f1
- \\server2\f2
After you do this, "DFS
link
targets" will be created by using parameters that resemble the following:
Link Name =
Link (Any valid link name may be used. It is
irrelevant to the scenario.)
Path of target =
\\server2\data or
\\server2\data\f1
or
\\server2\data\f1\f2
or \\server2\f1 or
\\server2\f2