FIX: The Windows Services for UNIX Client for Network File System (NFS) stops responding when you use Windows 2000 with Service Pack 4 as the Client for NFS and Linux as the Server for NFS (884852)


The information in this article applies to:

  • Microsoft Windows Services for UNIX 3.5

SYMPTOMS

The Microsoft Windows Services for UNIX Client for Network File System (NFS) stops responding (hangs) and CPU utilization approaches 100 percent when you use Microsoft Windows 2000 with Service Pack 4 (SP4) as a Client for NFS and Linux as a Server for NFS.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. 
   Date         Time   Version      Size     File name
   ------------------------------------------------------
   26-Aug-2004  09:20  8.0.1969.15  313,984  Nfsgwrdr.sys
   26-Aug-2004  09:20  8.0.1969.15  310,400  Nfsrdr.sys

WORKAROUND

To work around this problem, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following subkey in the registry:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\tcpip\Parameters

  3. On the Edit menu, click New, and then click DWORD Value.
  4. Add the following value:
    Value Name TcpTimedWaitDelay
    Data TypeREG_DWORD
    Value 30-300 (Decimal) - time in seconds
    Note We recommended that you set the TIME_WAIT time to 20 to 30 seconds.
  5. On the File menu, click Exit.
  6. Restart the computer.

STATUS

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

REFERENCES

For more information about Windows Services for UNIX, visit the following Microsoft Web site:

http://www.microsoft.com/windows/sfu/productinfo/default.asp

Modification Type:MinorLast Reviewed:6/2/2006
Keywords:kbBug kbstoprespond kbRegistry kbfix kbQFE kbHotfixServer KB884852 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.