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 cannot access or mount a Windows Server 2008 R2-based NFS share after a failover if the NFS share uses Krb5 or Krb5i authentication


View products that this article applies to.

Symptoms

Issue 1

Consider the following scenario:
  • You install the failover cluster feature and the Services for NFS feature on a computer that is running Windows Server 2008 R2.
  • You configure a Network File System (NFS) share to allow only Kerberos v5 authentication (Krb5) or Kerberos v5 integrity checking and authentication (Krb5i).
  • You export the NFS share to a cluster node.
  • The NFS share fails over to another cluster node.
In this scenario, you can no longer access the NFS share unless you disconnect all connections to the server and then reconnect to the server.

Issue 2

Assume that you configure a Windows Server 2008 R2-based Network File System (NFS) share to allow only Kerberos v5 authentication (Krb5) or Kerberos v5 integrity checking and authentication (Krb5i). In this scenario, some NFS client implementations cannot mount the NFS share from a failover cluster or from a stand-alone server when the AUTH_SYS authentication is disabled. 

↑ 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 Web site: 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 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1).

Registry information

To use the hotfix in this package, 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 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.
    VersionProductSR_LevelService branch
    6.1.760  0.
    16xxx
    Windows Server 2008 R2RTMGDR
    6.1.760  0.
    20xxx
    Windows Server 2008 R2RTMLDR
    6.1.760  1.
    17xxx
    Windows Server 2008 R2SP1GDR
    6.1.760  1.
    21xxx
    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 Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 2008 R2
File nameFile versionFile sizeDateTimePlatform
Rpcxdr.mofNot applicable4,44510-Jun-200921:00Not applicable
Rpcxdr.sys6.1.7600.20880104,96014-Jan-201103:39x64
Rpcxdr.mofNot applicable4,44510-Jun-200921:00Not applicable
Rpcxdr.sys6.1.7601.21641104,96014-Jan-201103:36x64
Msnfsflt.mofNot applicable4,46010-Jun-200921:00Not applicable
Nfs-servercore-ppdlic.xrm-msNot applicable3,00114-Jan-201106:26Not applicable
Nfssvc.exe6.1.7600.2088041,47214-Jan-201106:10x64
Nfssvr.mofNot applicable6,19510-Jun-200921:00Not applicable
Nfssvr.sys6.1.7600.20880735,74414-Jan-201103:40x64
Msnfsflt.mofNot applicable4,46005-Nov-201002:11Not applicable
Msnfsflt.sys6.1.7601.1751431,23220-Nov-201009:27x64
Nfs-servercore-ppdlic.xrm-msNot applicable3,00114-Jan-201106:40Not applicable
Nfssvc.exe6.1.7601.2164141,47214-Jan-201106:16x64
Nfssvr.mofNot applicable6,19505-Nov-201002:11Not applicable
Nfssvr.sys6.1.7601.21641735,74414-Jan-201103:37x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Rpcxdr.mofNot applicable4,44510-Jun-200921:06Not applicable
Rpcxdr.sys6.1.7600.20880261,12014-Jan-201102:55IA-64
Rpcxdr.mofNot applicable4,44510-Jun-200921:06Not applicable
Rpcxdr.sys6.1.7601.21641261,12014-Jan-201102:48IA-64
Msnfsflt.mofNot applicable4,46010-Jun-200921:06Not applicable
Nfs-servercore-ppdlic.xrm-msNot applicable3,00114-Jan-201105:25Not applicable
Nfssvc.exe6.1.7600.2088091,13614-Jan-201105:08IA-64
Nfssvr.mofNot applicable6,19510-Jun-200921:06Not applicable
Nfssvr.sys6.1.7600.208801,589,76014-Jan-201102:57IA-64
Msnfsflt.mofNot applicable4,46005-Nov-201002:11Not applicable
Msnfsflt.sys6.1.7601.1751470,65620-Nov-201008:02IA-64
Nfs-servercore-ppdlic.xrm-msNot applicable3,00114-Jan-201105:27Not applicable
Nfssvc.exe6.1.7601.2164191,13614-Jan-201105:04IA-64
Nfssvr.mofNot applicable6,19505-Nov-201002:11Not applicable
Nfssvr.sys6.1.7601.216411,589,76014-Jan-201102:49IA-64

↑ 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

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_11c7423277db5d3856be2f8dd9019a76_31bf3856ad364e35_6.1.7600.20880_none_2cd1b727daa4b999.manifest
File versionNot applicable
File size706
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable
File nameAmd64_2ef0889c5f697de0d5ba94373e2848ed_31bf3856ad364e35_6.1.7601.21641_none_269773502e5db68f.manifest
File versionNot applicable
File size703
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable
File nameAmd64_7c28b662e313c74657ff4255d50411cd_31bf3856ad364e35_6.1.7600.20880_none_d9b6af91cd325681.manifest
File versionNot applicable
File size703
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable
File nameAmd64_ff69bc9745923039dd763cca719c4eb3_31bf3856ad364e35_6.1.7601.21641_none_69ff9605cef92ade.manifest
File versionNot applicable
File size706
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-openrpc_31bf3856ad364e35_6.1.7600.20880_none_40338d017ddb7bf7.manifest
File versionNot applicable
File size9,501
Date (UTC)14-Jan-2011
Time (UTC)06:59
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-openrpc_31bf3856ad364e35_6.1.7601.21641_none_42462a017ae09176.manifest
File versionNot applicable
File size9,501
Date (UTC)14-Jan-2011
Time (UTC)07:17
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.1.7600.20880_none_b81e3d0c3a1ecf58.manifest
File versionNot applicable
File size41,883
Date (UTC)14-Jan-2011
Time (UTC)17:07
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.1.7601.21641_none_ba30da0c3723e4d7.manifest
File versionNot applicable
File size41,883
Date (UTC)14-Jan-2011
Time (UTC)17:07
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,583
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_026cb5794f56cfe364fc2fe0b03b4e29_31bf3856ad364e35_6.1.7600.20880_none_2390c9fd7ab4a23e.manifest
File versionNot applicable
File size704
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable
File nameIa64_1e8b982e4c2ff7ca7bf523396ab36826_31bf3856ad364e35_6.1.7600.20880_none_17337d3bfd6b5b0a.manifest
File versionNot applicable
File size701
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable
File nameIa64_527ca8c2024cec19dec865a62f06ef65_31bf3856ad364e35_6.1.7601.21641_none_75a9fba1b2a16968.manifest
File versionNot applicable
File size704
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable
File nameIa64_c3c80656b429ff20ad2f240a214d0ae0_31bf3856ad364e35_6.1.7601.21641_none_f5b67ca85844b9b2.manifest
File versionNot applicable
File size701
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable
File nameIa64_microsoft-windows-nfs-openrpc_31bf3856ad364e35_6.1.7600.20880_none_e4169573c57c13bd.manifest
File versionNot applicable
File size9,499
Date (UTC)14-Jan-2011
Time (UTC)06:44
PlatformNot applicable
File nameIa64_microsoft-windows-nfs-openrpc_31bf3856ad364e35_6.1.7601.21641_none_e6293273c281293c.manifest
File versionNot applicable
File size9,499
Date (UTC)14-Jan-2011
Time (UTC)06:58
PlatformNot applicable
File nameIa64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.1.7600.20880_none_5c01457e81bf671e.manifest
File versionNot applicable
File size41,881
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable
File nameIa64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.1.7601.21641_none_5e13e27e7ec47c9d.manifest
File versionNot applicable
File size41,881
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,965
Date (UTC)14-Jan-2011
Time (UTC)17:05
PlatformNot applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2485543
Revision : 1
Created on : 1/7/2017
Published on : 2/10/2011
Exists online : False
Views : 174