Article ID: 150215 - View products that this article applies to.
This article was previously published under Q150215
When you create a shortcut to a resource on a mapped network drive, and then remap the same drive to a different network resource, Windows attempts to connect to the original network resource when you access the shortcut.
Furthermore, when you re-establish the original connection, a different drive letter may be mapped to the original resource. This may cause programs to fail because the expected drive mappings are not present.
This behavior is part of the mechanism by which Windows attempts to resolve and automatically maintain shortcuts to network resources.
For additional information about Windows shortcut resolution, please see the following articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/128932/EN-US/ )How Windows 95 Resolves Shortcut Links
(http://support.microsoft.com/kb/132658/EN-US/ )Shortcut to Deleted NetWare File May Open Wrong File
Individual shortcuts can be modified by using the Shortcut.exe tool to remove Universal Naming Convention (UNC) path information from the shortcut.
Note that to successfully use the Shortcut.exe tool to remove UNC path information from a shortcut, it must meet the following criteria:
Windows 95The Shortcut.exe tool is included in the Microsoft Windows 95 Resource Kit and is also located in the Admin\Apptools\Envvars folder on the Windows 95 CD-ROM.
Windows NTThe Shortcut.exe tool is included in the Microsoft Windows NT Server Resource Kit Version 4.0, Supplement One, in the I386\Desktop folder, MIPS\Desktop folder, and ALPHA\Desktop folder on the Windows NT Server Resource Kit CD-ROM.
For more information about how to resolve this issue in Windows NT, please see the following article in the Microsoft Knowledge Base:
158682To remove the UNC information from a shortcut, follow these steps:
(http://support.microsoft.com/kb/158682/EN-US/ )Shortcuts Created Under NT 4.0 Resolve to UNC Paths
NOTE: If you want to disable only the automatic resolution, and you are not concerned about deleting the UNC path information from the shortcut, you should perform only steps 1 and 2. The shortcut must contain both a UNC path and a static path.
(http://support.microsoft.com/kb/134401/EN-US/ )Windows 95 Resource Kit Readme.txt File
(http://support.microsoft.com/kb/137725/EN-US/ )Resource Kit Tools Included on the Windows 95 CD-ROM
The same result can be applied globally to all shortcuts by installing the following updated file for Windows 95, or a later version of this file:
SHELL32.DLL version 4.00.952 dated 11/3/95 817,664 bytes
Automatic resolution may be undesirable if the file pointed to by the shortcut has been deliberately moved to a different resource, or if a load- balancing mechanism is in place so that the same drive letter may be mapped to one of several network resources with identical contents.
When you right-click a shortcut, click Properties, and then click the Shortcut tab, the Target box specifies the path to the file and can contain either a UNC path (\\server\share\directory\filename.ext), or a static path (<drive:>\directory\filename.ext).
A shortcut to a network resource may have either type of path as the target depending on how it was created. For example, if the shortcut was created by right-clicking a network file and clicking Create Shortcut, it contains a static path and a UNC path.
When you run Shortcut.exe with the -s parameter to disable automatic network shortcut resolution, depending on the type of shortcut and the status of any network drive mappings, the following results occur when you double-click the shortcut:
Shortcut Containing UNC Path OnlyDisabling automatic shortcut resolution in a local shortcut, or one containing only UNC information, has no effect on the manner in which the shortcut is resolved.
Shortcut Containing UNC and Static PathsFor a shortcut that contains both UNC and static paths, shortcut resolution is more complex. If the you have not disabled shortcut resolution, then the original network resource is used. If the shortcut is mapped to the drive specified in the static path, that drive is used. If the resource is mapped to a different drive, the new drive is used, and the shortcut's static path is updated with the new drive information. If the resource is not currently mapped to a drive, one is assigned automatically, and the shortcut is updated with the new drive information.
If shortcut resolution has been disabled, it is resolved to the specified static path. Note that the original UNC path information is still contained within the shortcut.
If the original network share is mapped to the drive specified in the static path, the shortcut is resolved to it, but the UNC path information is not deleted from the shortcut.
If a different network share has been mapped to the drive indicated by the static path, and the static path points to an existing file on that drive, then the UNC information is removed from the shortcut, and the shortcut is resolved like a local shortcut. The update to Shell32.dll causes UNC information in all shortcuts to be ignored if the DWORD value "LinkResolveIgnoreLinkInfo" is present in the following registry key, and set to a data value of "1":
If this registry value is not present, this update will function the same as the released Windows 95 version in this respect. This registry value is not added automatically when installing this update.
For additional information about issues resolved by updates to this component, please see the following articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/161100/EN-US/ )File May Be Truncated When Copied to a Full Network Drive
(http://support.microsoft.com/kb/138014/EN-US/ )File May Be Truncated to Zero Bytes When Copied Onto Itself
(http://support.microsoft.com/kb/136834/EN-US/ )Error Copying Read-Only Files to Core SMB Server
(http://support.microsoft.com/kb/160807/EN-US/ )Cannot Connect to Windows NT Server with Many Shares
For additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/161020/EN-US/ )Implementing Windows 95 Updates
Article ID: 150215 - Last Review: November 1, 2006 - Revision: 1.2