You are currently offline, waiting for your internet to reconnect

Disabling Automatic Network Shortcut Resolution

This article was previously published under Q150215
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
When you create a shortcut to a resource on a mapped network drive, andthen remap the same drive to a different network resource, Windowsattempts to connect to the original network resource when you access theshortcut.

Furthermore, when you re-establish the original connection, a differentdrive letter may be mapped to the original resource. This may causeprograms to fail because the expected drive mappings are not present.
CAUSE
This behavior is part of the mechanism by which Windows attempts toresolve and automatically maintain shortcuts to network resources.

For additional information about Windows shortcut resolution, pleasesee the following articles in the Microsoft Knowledge Base:
128932 How Windows 95 Resolves Shortcut Links

132658 Shortcut to Deleted NetWare File May Open Wrong File
RESOLUTION
Individual shortcuts can be modified by using the Shortcut.exe tool toremove Universal Naming Convention (UNC) path information from theshortcut.

Note that to successfully use the Shortcut.exe tool to remove UNC pathinformation from a shortcut, it must meet the following criteria:
  • The shortcut must contain both UNC and static path information. You can verify the shortcut contains the static path by right-clicking the shortcut, clicking Properties, and then clicking the Shortcut tab. The path in the Target box should be in the following format:
    <drive>:\folder\filename.ext
    You can verify the shortcut contains the UNC path information by viewing the shortcut in Notepad. To do so, click Start, click Run, and then type the following line in the Open box
    notepad <path>\<shortcut.lnk>
    where <path> is the path to the shortcut you want to change, and <shortcut.lnk> is the name of the shortcut from which you want to remove the UNC path information.

    You may need to click Word Wrap on the Edit menu to view the shortcut file. The shortcut file contains primarily unreadable binary information, however you should be able to read the UNC and mapped drive information. Do not modify or save the shortcut file.
  • The drive specified in the static path has been mapped to a network share different than the original one referred to by the shortcut.
  • The mapped drive must contain a directory path structure and a file whose name matches that of the static path in the shortcut.
The Shortcut.exe tool can be obtained from the following locations:

Windows 95

The Shortcut.exe tool is included in the Microsoft Windows 95 Resource Kitand is also located in the Admin\Apptools\Envvars folder on the Windows 95CD-ROM.

Windows NT

The Shortcut.exe tool is included in the Microsoft Windows NT ServerResource Kit Version 4.0, Supplement One, in the I386\Desktop folder,MIPS\Desktop folder, and ALPHA\Desktop folder on the Windows NT ServerResource Kit CD-ROM.

For more information about how to resolve this issue in Windows NT, pleasesee the following article in the Microsoft Knowledge Base:
158682 Shortcuts Created Under NT 4.0 Resolve to UNC Paths
To remove the UNC information from a shortcut, follow these steps:

NOTE: If you want to disable only the automatic resolution, and you are notconcerned about deleting the UNC path information from the shortcut, youshould perform only steps 1 and 2. The shortcut must contain both a UNCpath and a static path.
  1. Click Start, point to Programs, and then click Command Prompt or MS-DOS Prompt.
  2. Use the Shortcut.exe tool to disable automatic network shortcut resolution with this shortcut. To do so, type the following line at the command prompt, and then press ENTER
    shortcut.exe -s <path><shortcut.lnk>
    where <path> is the path to the shortcut you want to change, and <shortcut.lnk> is the name of the shortcut from which you want to remove the UNC path information.
  3. Click Start, point to Programs, click Windows NT Explorer or Windows Explorer, and then locate the shortcut you specified in step 2.
  4. Rename the shortcut. When you rename the shortcut, Windows updates the shortcut so that it does not perform automatic network shortcut resolution. Do not change the extension of the shortcut.

    For information about how to rename a file, click Start, click Help, click the Index tab, type renaming, and then double-click the "Renaming files" topic.

    NOTE: You must rename the shortcut file in Windows NT Explorer or Windows Explorer. The shortcut is not updated if you rename it at a command prompt.
  5. Use the Shortcut.exe tool to resolve the shortcut to a static location and the delete the UNC path information. To do so, type the following line at a command prompt and then press ENTER
    shortcut.exe -r <path>\<shortcut.lnk>
    where <path> is the path to the shortcut you want to change, and <shortcut.lnk> is the name of the shortcut from which you want to remove the UNC information.
For additional information, please see the following articles in theMicrosoft Knowledge Base:
134401 Windows 95 Resource Kit Readme.txt File

137725 Resource Kit Tools Included on the Windows 95 CD-ROM


The same result can be applied globally to all shortcuts by installing thefollowing 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				
MORE INFORMATION
Automatic resolution may be undesirable if the file pointed to by theshortcut 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 mappedto one of several network resources with identical contents.

When you right-click a shortcut, click Properties, and then click theShortcut tab, the Target box specifies the path to the file and can containeither 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 targetdepending on how it was created. For example, if the shortcut was createdby right-clicking a network file and clicking Create Shortcut, it containsa static path and a UNC path.

When you run Shortcut.exe with the -s parameter to disable automaticnetwork shortcut resolution, depending on the type of shortcut and thestatus of any network drive mappings, the following results occur when youdouble-click the shortcut:

Shortcut Containing UNC Path Only

Disabling automatic shortcut resolution in a local shortcut, or onecontaining only UNC information, has no effect on the manner in whichthe shortcut is resolved.

Shortcut Containing UNC and Static Paths

For a shortcut that contains both UNC and static paths, shortcut resolutionis more complex. If the you have not disabled shortcut resolution, then theoriginal network resource is used. If the shortcut is mapped to the drivespecified in the static path, that drive is used. If the resource is mappedto a different drive, the new drive is used, and the shortcut's static pathis updated with the new drive information. If the resource is not currentlymapped to a drive, one is assigned automatically, and the shortcut isupdated with the new drive information.

If shortcut resolution has been disabled, it is resolved to the specifiedstatic path. Note that the original UNC path information is still containedwithin the shortcut.

If the original network share is mapped to the drive specified in thestatic path, the shortcut is resolved to it, but the UNC path informationis not deleted from the shortcut.

If a different network share has been mapped to the drive indicated by thestatic 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 isresolved like a local shortcut.The update to Shell32.dll causes UNC information in all shortcuts tobe ignored if the DWORD value "LinkResolveIgnoreLinkInfo" is presentin the following registry key, and set to a data value of "1":
   HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer				
If this registry value is not present, this update will function thesame as the released Windows 95 version in this respect. This registryvalue is not added automatically when installing this update.


For additional information about issues resolved by updates to thiscomponent, please see the following articles in the Microsoft KnowledgeBase:
161100 File May Be Truncated When Copied to a Full Network Drive

138014 File May Be Truncated to Zero Bytes When Copied Onto Itself

136834 Error Copying Read-Only Files to Core SMB Server

160807 Cannot Connect to Windows NT Server with Many Shares

For additional information about Windows 95 updates, please see thefollowing article in the Microsoft Knowledge Base:
161020 Implementing Windows 95 Updates
winnt prodnt
Properties

Article ID: 150215 - Last Review: 12/04/2015 14:35:24 - Revision: 1.2

Microsoft Windows 95, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbnetwork kbpolicy kbui KB150215
Feedback