Client Cannot Access Dfs Link Target If Share and Fault Tolerant Dfs Root Names Differ (326070)
The information in this article applies to:
- Microsoft Windows Millennium Edition
- Microsoft Windows 98 Second Edition
- Microsoft Windows 98
- Microsoft Windows 95
This article was previously published under Q326070 SYMPTOMS The Directory Service Client for Windows 95, Windows 98,
and Windows 98 Second Edition may not be able to connect to a Distributed File
System (Dfs) link. This problem may occur if the link is hosted on a fault
tolerant root (FT root) replica whose Dfs name is different from the host share
name. This includes share names that are exactly the same as the root name, but
are hidden (with a '$' character appended). For error message details, see the
"More Information" section of this article. For example, the DS
Client cannot connect to a Dfs path in an FT root configuration such as the
following (notice the FT root name and host share values):
FT Root name: \\domainname\ftroot
FT Root Replica: \\replicaserver\sharename
DFS Link name: linkname
DFS Path: \\domainname\ftroot\linkname
Link Target: \\server\sharename
The following configuration works properly; notice
the FT root name and host share values:
FT Root name: \\domainname\ftroot
FT Root Replica: \\replicaserver\ftroot
DFS Link name: linkname
DFS Path: \\domainname\ftroot\linkname
Link Target: \\server\sharename
Dfs stand-alone root names always match the
underlying host server share name. CAUSE This is a limitation of the Windows 95 and Windows 98 DS
Client, and does not apply to the Microsoft Windows NT DS Client, Microsoft
Windows 2000, or Microsoft Windows XP.
RESOLUTIONThis
behavior is by design.WORKAROUND When you create a domain Dfs root (FT root) or add a root
replica to an existing FT Root, allow the Dfs root name to remain the same as
the selected share name.
For existing FT roots, delete the root
replicas that have mismatched share names (or root, if only one replica
exists). Create them again, by using the share name. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 8/15/2006 |
---|
Keywords: | kbprb kbQFE KB326070 |
---|
|