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.

NFS version 4.1 and version 3 work unexpectedly in Windows Server 2012 R2 or Windows Server 2012


View products that this article applies to.

Symptoms

Issue 1

After you restart the Microsoft iSCSI Software Target service on a Network File System (NFS) server that runs Windows Server 2012 R2 or Windows Server 2012, you cannot access the NFS shares through NFS version 3.

Note: This issue does not occur on NFS version 4.1.

Issue 2

Assume that you have an NFS server that runs Windows Server 2012 R2 or Windows Server 2012. Additionally, assume that an NFS client which uses NFS version 4.1 does not have the access permissions for the NFS shares. In this situation, the client can access (in read-only mode) the shares unexpectedly.
Note: This issue does not occur on NFS version 3.

↑ Back to the top


Resolution

To resolve this issue, install update 2919355 in Windows Server 2012 R2 or update rollup 2934016 in Windows Server 2012, or install the hotfix that is described in this article.

Update information

For more information about how to obtain update 2919355, click the following article number to view the article in the Microsoft Knowledge Base:
2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014
For more information about how to obtain update 2934016, click the following article number to view the article in the Microsoft Knowledge Base:
2934016 Windows RT, Windows 8, and Windows Server 2012 update rollup: April 2014

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: 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 Server 2012 R2 or Windows Server 2012.

Registry information

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

Restart requirement

You may have to 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 Server 2012 R2 file information notes
Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    Version Product Milestone Service branch
    6.3.960 0.17 xxxWindows Server 2012 R2 RTM GDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Msnfsflt.mofNot applicable4,46018-Jun-201315:17Not applicable
Nfs-servercore-ppdlic.xrm-msNot applicable2,89306-Mar-201413:37Not applicable
Nfssvr.mofNot applicable6,23318-Jun-201315:17Not applicable
Nfssvr.sys6.3.9600.170411,236,48006-Mar-201409:20x64
Windows Server 2012 file information notes
Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" 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.2.920 0.16 xxxWindows Server 2012RTMGDR
    6.2.920 0.20xxxWindows Server 2012RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Msnfsflt.mofNot applicable4,46006-Jul-201220:34Not applicable
Msnfsflt.sys6.2.9200.1645332,25608-Nov-201204:00x64
Nfs-servercore-ppdlic.xrm-msNot applicable2,89315-Feb-201407:34Not applicable
Nfssvc.exe6.2.9200.1645367,58408-Nov-201204:22x64
Nfssvr.mofNot applicable6,23306-Jul-201220:34Not applicable
Nfssvr.sys6.2.9200.168481,249,79215-Feb-201404:11x64
Msnfsflt.mofNot applicable4,46002-Jun-201214:44Not applicable
Msnfsflt.sys6.2.9200.1638432,25626-Jul-201202:29x64
Nfs-servercore-ppdlic.xrm-msNot applicable2,89315-Feb-201405:41Not applicable
Nfssvc.exe6.2.9200.1638467,58426-Jul-201203:08x64
Nfssvr.mofNot applicable6,23302-Jun-201214:44Not applicable
Nfssvr.sys6.2.9200.209681,249,79215-Feb-201404:31x64

↑ Back to the top


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

For more information about NFS, go to the following Microsoft website:
Additional file information

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File propertyValue
File nameAmd64_b1b7f8411e4f2457583e50cf7da61865_31bf3856ad364e35_6.3.9600.17041_none_61adaa052b83cb60.manifest
File versionNot applicable
File size706
Date (UTC)06-Mar-2014
Time (UTC)23:41
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.3.9600.17041_none_4c8b2ad6db251fd5.manifest
File versionNot applicable
File size38,355
Date (UTC)06-Mar-2014
Time (UTC)23:41
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,609
Date (UTC)06-Mar-2014
Time (UTC)23:41
PlatformNot applicable

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File propertyValue
File nameAmd64_493764ae7ba9bffa332558318c73aced_31bf3856ad364e35_6.2.9200.20968_none_953c36a87bc84d16.manifest
File versionNot applicable
File size706
Date (UTC)17-Feb-2014
Time (UTC)08:52
PlatformNot applicable
File nameAmd64_6e2187a916e98fe90835f22010231ccf_31bf3856ad364e35_6.2.9200.16848_none_09ffee30a377c704.manifest
File versionNot applicable
File size706
Date (UTC)17-Feb-2014
Time (UTC)08:52
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.2.9200.16848_none_b49d9a2e90ebd050.manifest
File versionNot applicable
File size38,339
Date (UTC)17-Feb-2014
Time (UTC)08:52
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.2.9200.20968_none_b5119721aa19a7fc.manifest
File versionNot applicable
File size38,339
Date (UTC)17-Feb-2014
Time (UTC)08:52
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,609
Date (UTC)17-Feb-2014
Time (UTC)08:52
PlatformNot applicable

↑ Back to the top


Keywords: kbsurveynew, kbexpertiseadvanced, kbfix, kbqfe, kbhotfixserver, kbautohotfix, kb

↑ Back to the top

Article Info
Article ID : 2934249
Revision : 1
Created on : 1/7/2017
Published on : 4/28/2014
Exists online : False
Views : 325