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

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.

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: 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.

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.

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:
   Collapse this tableExpand this table

   Value Name	TcpTimedWaitDelay
   Data Type	REG_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.

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

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