Microsoft KB Archive/942868

= Virtual machines on a computer that is running ESX Server may not connect to a computer that is running WSS 2003 R2 and Server for Network File System (NFS) or to a computer that is running any edition of Windows Server 2003 R2 and Server for NFS =

Article ID: 942868

Article Last Modified on 10/17/2007

-

APPLIES TO


 * Microsoft Windows Server 2003 R2 Standard x64 Edition
 * Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003 R2 Enterprise x64 Edition
 * Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
 * Microsoft Windows Server 2003 R2 Datacenter x64 Edition
 * Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
 * Microsoft Windows Storage Server 2003 R2 x32 Enterprise
 * Microsoft Windows Storage Server 2003 R2 x32 Standard
 * Microsoft Windows Storage Server 2003 R2 x64 Enterprise
 * Microsoft Windows Storage Server 2003 R2 x64 Standard

-



SYMPTOMS
Consider the following scenario:
 * You use a computer that is running VMware ESX Server to host virtual machines.
 * These virtual machines keep their virtual machine data on a computer that is running Windows Storage Server (WSS) 2003 R2.
 * The computer that is running WSS 2003 R2 is also running Server for Network File System (NFS).
 * Each virtual machine on the ESX Server-based server opens two NFS port connections on the computer that is running WSS 2003 R2.

In this scenario, if there is a network connectivity break between the ESX Server-based server and the NFS-based WSS 2003 R2 server, the NFS-based WSS 2003 R2 server still keeps the two NFS connections from the ESX server.

After network connectivity is restored between the two servers, the older NFS connections are still persistent on the NFS-based WSS 2003 R2 server. The newer NFS connections for the virtual machines that are hosted on the ESX Server-based server are also still persistent on the NFS-based WSS 2003 R2 server.

After some network breaks occur between the ESX Server-based server and the NFS-based WSS 2003 R2 server, you cannot connect to the NFS-based WSS 2003 R2 server. This issue occurs because the limitation of the maximum number of NFS connections for a single IP address has been reached.

Note This issue also occurs on any edition of Windows Server 2003 R2 that is also running Server for NFS.



Hotfix information
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

Prerequisites
This hotfix requires that you have Windows Server 2003 SP1 or Windows Server 2003 SP2 installed on the computer.

889100 How to obtain the latest service pack for Windows Server 2003

Restart requirement
You have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

Hotfix installation information
After you install this hotfix, you must create the tcpkeepalivetime and tcpkeepaliveinterval registry entries to enable the hotfix. To create these registry entries, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate and then double-click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcXdr\Parameters

 On the Edit menu, point to New, and then click DWORD Value. In the details pane, type tcpkeepalivetime for the new registry entry, and then press ENTER. On the Edit menu, point to New, and then click DWORD Value. In the details pane, type tcpkeepaliveinterval for the new registry entry, and then press ENTER. Right-click tcpkeepalivetime, and then click Modify.</li> In the Edit DWORD Value dialog box, under Base, click Decimal.</li> In the Value data box, type 120, and then click OK.</li> Right-click tcpkeepaliveinterval, and then click Modify.</li> In the Edit DWORD Value dialog box, under Base, click Decimal.</li> In the Value data box, type 2, and then click OK.</li> On the File menu, click Exit to close Registry Editor.</li></ol>

Note The value of the tcpkeepalivetime registry entry should be between 60 and 7200. The value of the tcpkeepaliveinterval entry should be between 1 and 60. If the values are beyond the specified values, reset them to the default values. These default values are 120 for the tcpkeepalivetime entry and 2 for the tcpkeepaliveinterval entry.

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 item in Control Panel.

Windows Server 2003 with Service Pack 2, x64-based versions
<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
For more information about the connection limitation from a single IP address to a Windows Storage Server 2003 R2-based computer that is running Server for NFS, click the following article number to view the article in the Microsoft Knowledge Base:

916794 When 16 concurrent connections have been made from a single IP address to a Windows Storage Server 2003 R2-based computer that is running Server for NFS, no additional connections can be made

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Keywords: kbexpertiseinter kbqfe kbfix KB942868

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.