Microsoft KB Archive/888750

= Slow performance when you try to access resources on your Virtual Server 2005 host computer from a guest virtual machine =

Article ID: 888750

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft Virtual Server 2005 Standard Edition
 * Microsoft Virtual Server 2005 Enterprise Edition
 * Microsoft Virtual PC 2004

-



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
When you try to access resources on your Microsoft Virtual Server 2005 host computer from a guest virtual machine, the performance is very slow. When you try to copy a large file, the file copy may take minutes when you expect it to take seconds. Or, the large file transfer may not be completed. You may also experience that the guest virtual machine or other guest virtual machines that are attached to the same virtual network may disconnect from the virtual network.

This problem may also cause actual non-virtual network connections to the host machine to be disconnected. You may see an event log entry that is similar to the following event log entry : Event ID: 2025

Source: SRV

Description: The server has detected an attempted Denial-of-Service attack from client \\, and has disconnected the connection.



CAUSE
This problem may occur if you have Transmission Control Protocol (TCP) segmentation offloading enabled on the host computer's network adapter. The Digital Equipment Corporation (DEC)/Intel 21140A chipset that Virtual Server 2005 emulates does not support TCP segmentation offloading. Therefore, the Virtual Server Network Driver Interface Specification (NDIS) filter driver must offload the TCP segmentation on the network adapter. This may cause slow performance and other network problems when you use Virtual Server 2005.



WORKAROUND
To work around this problem, use one of the following methods:

Note If you have any network adapters that Virtual Server 2005 guests use, Microsoft recommends that you disable TCP segmentation offloading.

Method 1
Enable local area network (LAN) routing on the host computer, and then move the virtual network to the Microsoft Loopback Adapter.

Note To perform this procedure, your host computer must be running Microsoft Windows Server 2003.

To enable LAN routing on the host computer, follow these steps:  Click Start, point to Administrative Tools, and then click Routing and Remote Access. Right-click your server name. If remote access is already enabled, follow these steps:  Click Properties, and then click the General tab. Make sure that the Router check box is selected, and then click OK.

If remote access is disabled, follow these steps:  Click Configure and Enable Routing and Remote Access.

The Routing and Remote Access Server Setup Wizard starts.</li> Click Next.</li> On the Configuration page, click Custom configuration, and then click Next.</li> On the Custom Configuration page, click to select the LAN routing check box.</li> Click Next, and then click Finish.</li> Click Yes if you are prompted to start the Routing and Remote Access service.</li></ol> </li></ol>

For information about how to move the virtual network to the Microsoft Loopback Adapter, see the &quot;Using Microsoft Loopback Adapter&quot; and the &quot;Setting up virtual networks&quot; topics in Virtual Server 2005 Help.

Method 2
Disable TCP task offloading in the registry of the host computer. To do this, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.  Click Start, click Run, type regedit, and then click OK .</li> Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

</li> Click Edit, point to New, and then click DWORD Value.</li> Type DisableTaskOffload as the entry name, and then press ENTER.</li> Right-click DisableTaskOffload, and then click Modify.</li> In the Value data box, type a value of 1, and then click OK.</li> Quit Registry Editor.</li> Restart your computer.</li></ol>

Method 3
If you do not want to disable TCP segmentation offloading on the whole system, and you want to only disable TCP segmentation offloading on the network adapters that Virtual Server 2005 guests use, you must not add the DisableTaskOffload registry entry that is described in Method 2. Instead, you can disable the task offload properties on the Advanced tab of the Properties dialog box of the network adapter.

Warning When you disable the task offload properties, guest virtual machines that are attached to the same virtual network may temporarily disconnect from the virtual network.

To disable the task offload properties, follow these steps:
 * 1) Click Start, click Run, type ncpa.cpl, and then click OK.
 * 2) Right-click your network adapter, and then click Properties.
 * 3) Click the General tab, and then click Configure.
 * 4) Click the Advanced tab.
 * 5) In the Property box, click the Offload TCP Segmentation property.
 * 6) In the Value list, click Off, and then click OK.
 * 7) If you also have the following task offload properties in the Property box, you must repeat step 5 to step 6 to disable these properties:
 * 8) * Offload Receive IP Checksum
 * 9) * Offload Receive TCP Checksum
 * 10) * Offload Transmit IP Checksum
 * 11) * Offload Transmit TCP Checksum

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

Keywords: kbtshoot kbbug KB888750

-

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

© Microsoft Corporation. All rights reserved.