DFS shares appear to be empty when they are accessed by client computers that are running Windows 95, Windows 98, or Windows 98 Second Edition (819106)
The information in this article applies to:
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Server
- Microsoft Windows 95
- Microsoft Windows 98
- Microsoft Windows 98 Second Edition
CAUSEThese problems may occur if either of the following
conditions is true:
- You replaced a link target that was a normal share with a
nested DFS root, but you did not delete the link target on the DFS root server
and then re-create it in the same DFS root.
- You implemented a nested DFS structure and restored the DFS
namespace by using an outdated Dfsutil.exe tool.
RESOLUTIONTo resolve this problem, if you replaced a link target that
was a normal share with a nested DFS root, delete the link target on the DFS
root server, and then re-create it by using the Distributed File System Manager
snap-in. If you implemented a nested DFS structure and restored the
DFS namespace by using the Dfsutil.exe tool, use either of the following
methods, or use a combination of both. Method 1 Use the Dfscmd.exe tool to save and to restore the DFS namespace.
Make sure that you do not use the /restore option for nested root servers in your import script. Method 2 Use this method if you have to restore TTL/Timeout settings.
- Use the dfsutil /import command to restore the DFS namespace.
- Use the graphical user interface (GUI) to manually delete
and re-create the links to nested root servers.
The Dfsutil.exe tool that is included with Windows 2000
Support Tools provides no command-line option to specify that a DFS link points
to a nested DFS root. You cannot rely on this version of Dfsutil.exe tool alone
to import or restore a DFS structure that includes nested stand-alone DFS root
servers. An updated version of the Dfsutil.exe tool is now available
in hotfix 834656. For additional
information about this hotfix, click the following article number to view the
article in the Microsoft Knowledge Base: 834656
Dfsutil.exe does not exit correctly when you export DFS roots in Windows 2000
The main differences between the Dfsutil.exe tool and the
Dfscmd.exe tool in this context are the following:
- The Dfscmd.exe tool, like the GUI mode, checks for the
existence of the target servers and queries them for their settings as long as
you do not use the /restore option in the restore script.
- The Dfsutil.exe tool only reads the import scripts and
saves the settings without checking for the existence of the target servers.
WORKAROUNDTo work around this problem, delete the DFS links to nested
DFS roots, and then re-create them. If you want to make a link to a link target
that will ultimately be a DFS root, first make the link target a nested DFS
root. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.REFERENCES For additional information about this problem, click the
following article numbers to view the articles in the Microsoft Knowledge Base:
269372
How to back up and restore the DFS structure in Windows 2000
322326 Error messages when you try to access a drive that is mapped to domain DFS root by using NetBIOS domain name
323466 Availability of the Active Directory client extension update for Windows 98
For additional information about the Dfsutil.exe tool
that correctly exports the volume type, click the following article number to
view the article in the Microsoft Knowledge Base: 834656
Dfsutil.exe does not exit correctly when you export DFS roots in Windows 2000
For additional information, click the
following article number to view the article in the Microsoft Knowledge Base: 824718
The Distributed File System (DFS) utility incorrectly reports volume types when you use the EXPORT switch
For additional information about the Distributed
File System, obtain the following white papers by visiting the following
Microsoft Web sites:
Modification Type: | Major | Last Reviewed: | 8/15/2006 |
---|
Keywords: | KB819106 |
---|
|