You cannot access or mount an NFS share in Windows Server 2003 R2 SP2

Article translations Article translations
Article ID: 2028587 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Issue 1

When you share some files on a computer that is running Windows Server 2003 R2, a client computer may be unable to access the NFS share. Additionally, the following Network File System (NFS) event is logged in the System log:
Event Type: Warning
Event Source: NfsSvr
Event ID: 1003
Description:
Mapping information could not be obtained from Username mapping. Another attempt will be made after 30 minutes.

Issue 2

When you try to mount an NFS share on a client computer that is running Windows Server 2003 R2, you receive an error message. Additionally, the following event is logged in the System log:
Event Type: Warning
Event Source: NfsRdr
Event ID: 16384
Description:
The remote server does not have locking support. A mount was requested with locking enabled. The share is being mounted anyway. Some functionality may not be available.
Note These issues usually occur on a computer that has a fast CPU.

CAUSE

This issue occurs because the current NFS implementation generates TCP port numbers by using the current time stamp.

When the computer has some high speed CPUs, the current NFS implementation may be called multiple times to generate some TCP port numbers by using the same time stamp. When the same time stamp is used, the same TCP port number is generated. Therefore, several different requests try to create different TCP connections by using the same TCP port. This behavior causes all the requests except the first request to fail. Additionally, the NFS client computer may be unable to communicate to the NFS server and be unable to mount an NFS share.

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 this specific problem.

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, submit a request to 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:
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 Server 2003 R2 Service Pack 2 (SP2). Additionally, you must have the Client for NFS service installed or the Server for NFS service installed.

For more information about how to obtain a Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

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 English (United States) 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 2003 R2 file information notes
  • In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2003 R2 SP2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Rpcxdr.sys5.2.3790.471070,14414-May-201013:08x86SP2SP2QFE
For all supported x64-based versions of Windows Server 2003 R2 SP2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Rpcxdr.sys5.2.3790.4710106,49614-May-201012:50x64

STATUS

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

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

Properties

Article ID: 2028587 - Last Review: June 22, 2010 - Revision: 1.0
APPLIES TO
  • Microsoft Windows Server 2003 Service Pack 2, when used with:
    • Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
    • Microsoft Windows Server 2003 R2 Datacenter x64 Edition
    • Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
    • Microsoft Windows Server 2003 R2 Enterprise x64 Edition
    • Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86)
    • Microsoft Windows Server 2003 R2 Standard x64 Edition
Keywords: 
kbqfe kbHotfixServer kbfix kbsurveynew kbexpertiseinter kbautohotfix KB2028587

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com