Article ID: 150604 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft Windows Explorer for Microsoft Windows NT maps network drive letters to network shares even though you did not map any drives.
This behavior occurs in two cases.
Case 1Network drives are mapped to network shares if both of the following conditions are true:
Case 2This behavior also occurs when both of the following conditions are true:
This is system behavior that occurs under Microsoft Windows NT version 4.0. This behavior is exposed when you perform a search against drives that contain shortcuts that point to a target drive is a static drive letter. For example, a shortcut to a Microsoft Word document that uses the following target
<drive>:\Folder\Myfile.docwhere <drive> is a network server, maps a new drive to the server using the next available drive letter in Windows Explorer.
Microsoft Windows NT Workstation or Windows NT Server version 4.0 shortcuts attempt to embed a UNC path, for example, \\<machine>\admin$, for the .lnk file.
For more information about shortcuts under Windows NT 4.0, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/158682/EN-US/ )Shortcuts Created Under NT 4.0 Resolve to UNC Paths
To work around this problem, use the following appropriate methods.
Method 1: Install Microsoft Windows NT 4.0 Service Pack 3For information about obtaining and installing this service pack, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtain Windows NT Versiom 4.0 U.S. Service Pack
Method 2: Avoid Searching Folders That Contain ShortcutsBecause Windows NT maps a network drive for each shortcut with a target drive that uses a drive letter, narrow your search to include only those folders that do not contain shortcuts to documents located on network drives.
Shortcut file names contain the .lnk file name extension. As an alternative, consider moving .lnk files to a different folder before you index or search.
Method 3: Change Shortcut Target Locations to UNC PathsIn the Properties dialog box for each shortcut, change the Target for the shortcut from a static drive letter to a UNC path. For example, change
where <Server> is the name of the computer or server and <Shared Folder> is the shared folder on that drive.
Method 4: Disable Microsoft Find FastDisabling Find Fast may help to minimize this problem. However, this method does not resolve the behavior and may not work in every situation. Microsoft does not recommend disabling Find Fast if you are administering a Microsoft Windows NT server.
NOTE: If you are running Microsoft Windows NT Server and install the Srvpack on the Microsoft Office 97 compact disc, removing Find Fast disables several features, including the Web search features. See the Webadhlp.htm file in the Srvpack folder on your Office 97 compact disc for more information.
For information about removing Find Fast, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/158705/EN-US/ )How to Disable the Find Fast Indexer
Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
The Find Fast program builds indexes to speed up finding documents from the Open and Advanced Find dialog boxes in Microsoft Office programs. Find Fast is installed by the Microsoft Office Setup program as an Office Tools component. Setup automatically creates an index for all of your Office documents on each local drive on the computer.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Contact us for more help