Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You are redirected to a wrong NFS share when you try to access the share by using Windows Explorer or UNC in Windows 7 or Windows Server 2008 R2 SP1


View products that this article applies to.

Symptoms

Assume that you have a network file system (NFS) server that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. You have some exported NFS shares on a Unix NFS server. For example, you have the following exported NFS shares:

  • Share
  • Share1
  • Share2
  • Share3

When you try to access the "Share1" share by typing the following path in Windows Explorer or by typing the Universal Naming Convention (UNC) path, you are redirected to the "Share" export:

   \\server\share1

More specifically, you are redirected to the "Share" export unexpectedly when you try to access any share that begins with the "Share" prefix by using Windows Explorer or UNC.

↑ Back to the top


Cause

This issue occurs because of an issue that occurs in the share name comparison logic that is performed by NFS network provider.

↑ Back to the top


Resolution

Hotfix information

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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 website:

http://support.microsoft.com/contactus/?ws=support

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.

Prerequisites

To apply this hotfix, you must be running Windows 7 SP1 or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760  1.22xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

 For all supported x86-based versions of Windows 7

File nameNfs-clientcore-ppdlic.xrm-ms
File versionNot applicable
File size3,001
Date (UTC)26-Jul-2013
Time (UTC)02:13
PlatformNot applicable
File nameNfsclnt.exe
File version6.1.7601.22403
File size52,736
Date (UTC)26-Jul-2013
Time (UTC)00:56
Platformx86
File nameNfsnp.dll
File version6.1.7601.22403
File size60,416
Date (UTC)26-Jul-2013
Time (UTC)01:55
Platformx86
File nameNfsrdr.mof
File versionNot applicable
File size4,471
Date (UTC)10-Jun-2009
Time (UTC)21:40
PlatformNot applicable
File nameNfsrdr.sys
File version6.1.7601.22403
File size202,240
Date (UTC)26-Jul-2013
Time (UTC)00:56
Platformx86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File nameNfs-clientcore-ppdlic.xrm-ms
File versionNot applicable
File size3,001
Date (UTC)26-Jul-2013
Time (UTC)02:42
PlatformNot applicable
File nameNfsclnt.exe
File version6.1.7601.22403
File size65,536
Date (UTC)26-Jul-2013
Time (UTC)01:11
Platformx64
File nameNfsnp.dll
File version6.1.7601.22403
File size72,192
Date (UTC)26-Jul-2013
Time (UTC)02:23
Platformx64
File nameNfsrdr.mof
File versionNot applicable
File size4,471
Date (UTC)10-Jun-2009
Time (UTC)21:02
PlatformNot applicable
File nameNfsrdr.sys
File version6.1.7601.22403
File size247,296
Date (UTC)26-Jul-2013
Time (UTC)01:11
Platformx64

For all supported IA-64-based versions of Windows Server 2008 R2

File nameNfs-clientcore-ppdlic.xrm-ms
File versionNot applicable
File size3,001
Date (UTC)26-Jul-2013
Time (UTC)01:53
PlatformNot applicable
File nameNfsclnt.exe
File version6.1.7601.22403
File size156,160
Date (UTC)26-Jul-2013
Time (UTC)00:39
PlatformIA-64
File nameNfsnp.dll
File version6.1.7601.22403
File size159,744
Date (UTC)26-Jul-2013
Time (UTC)01:34
PlatformIA-64
File nameNfsrdr.mof
File versionNot applicable
File size4,471
Date (UTC)10-Jun-2009
Time (UTC)21:07
PlatformNot applicable
File nameNfsrdr.sys
File version6.1.7601.22403
File size589,824
Date (UTC)26-Jul-2013
Time (UTC)00:39
PlatformIA-64

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 

↑ Back to the top


More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

   824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File nameX86_dd1cbc11f2a4525b667c2d1566829e25_31bf3856ad364e35_6.1.7601.22403_none_eae2ef18e2334df4.manifest
File versionNot applicable
File size702
Date (UTC)26-Jul-2013
Time (UTC)05:25
PlatformNot applicable
File nameX86_microsoft-windows-nfs-clientcore_31bf3856ad364e35_6.1.7601.22403_none_af7d3879b9ecb904.manifest
File versionNot applicable
File size28,372
Date (UTC)26-Jul-2013
Time (UTC)02:19
PlatformNot applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File nameAmd64_0e5e91b9ae7fa2c3d6862f10c08ebef8_31bf3856ad364e35_6.1.7601.22403_none_43b2fb5cc7ab23f7.manifest
File versionNot applicable
File size706
Date (UTC)26-Jul-2013
Time (UTC)05:25
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-clientcore_31bf3856ad364e35_6.1.7601.22403_none_0b9bd3fd724a2a3a.manifest
File versionNot applicable
File size28,376
Date (UTC)26-Jul-2013
Time (UTC)02:49
PlatformNot applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File nameIa64_dea62be463d7b660bced8eeea9a634d8_31bf3856ad364e35_6.1.7601.22403_none_01e50db8582d116b.manifest
File versionNot applicable
File size704
Date (UTC)26-Jul-2013
Time (UTC)05:25
PlatformNot applicable
File nameIa64_microsoft-windows-nfs-clientcore_31bf3856ad364e35_6.1.7601.22403_none_af7edc6fb9eac200.manifest
File versionNot applicable
File size28,374
Date (UTC)26-Jul-2013
Time (UTC)02:08
PlatformNot applicable

↑ Back to the top


Keywords: kbqfe, kbautohotfix, kbhotfixserver, kbsurveynew, kbexpertisadvance, kbfix, vkball, kb

↑ Back to the top

Article Info
Article ID : 2874401
Revision : 2
Created on : 9/19/2018
Published on : 9/19/2018
Exists online : False
Views : 166