This article was previously published under Q294687
This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
When you enter a UNC path to a distributed file system (Dfs) share where the domain name is different from the network basic input/output system (NetBIOS) name, you receive an error message similar to the following:
You do not have access to the folder '\\Dfs domain name'. See your administrator for access to this folder.
Or, you receive the following error message:
'\\domainname' could not be found. Check the spelling of the file name, and verify that the file location is correct. If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted.
Note In this error message, domainname is the NetBIOS domain name.
The NetBIOS name of the domain is different from the Domain Name System (DNS) name.
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Office 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
276367 How to obtain the latest Office 2000 service pack
After you install the latest service pack, you must add and set a registry value as described in the "More Information" section of this article.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Size File name ------------------------------------------------------ 14-Jul-2001 02:19 4,028,572 Mso9_admin.msp (Admin) 13-Jul-2001 22:30 1,948,212 Mso9.msp (Client)
After the hotfix is installed, the following files will have the listed attributes or later:
Date Time Version Size File name ----------------------------------------------------- 13-Jul-2001 15:33 22.214.171.12412 5,595,185 Mso9.dll
To work around this problem, map a network drive directly to \\Dfs domain name\share name.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft Office 2000 Service Pack 3 (SP-3).
New registry value required
To activate the hotfix for this issue, you must add and set a registry value. You can use the file 3307on.reg to set this value, or you can set the value manually. To do this manually, follow these steps.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Start Registry Editor (Regedit.exe).
Locate and select the following key in the registry: