I wanted to let you know about this TCP command that I highly recommend that you apply on all Windows Server SP 2 servers. While this functionality is designed to improve the overall functionality and scalability of TCP connectivity, there can be problems where the offloading of packets do to high traffic demand exceeds the network cards physical capability. I have seen all of these problems related to this issue. Usually you will need to update the NIC drivers as well since most will include new support for this capability. You will see this same issue on Windows 2008 and Vista.
After applying Service Pack 2 on your Windows Server 2003 computer, you may experience one or more of the following symptoms: 1. If it is an Exchange server, Exchange Queues become clogged in the MAPI delivery queue. Messages get stuck in this queue and cannot be delivered properly. 2. ActiveSync may not work on the Exchange Server 2003. 3. For the IIS server, browsing the Public and/or Default Website in IIS results in error "Page cannot be displayed" including SharePoint4. Non-Paged Pool (KERNEL) memory becomes exhausted. 5. For a printer server, the printing job may be partially missing.
6. Content Deployment Fails or slow Performance when accessing Sharepoint
Netsh int ip set chimney DISABLED
Set the following registry keys on both source and destination servers and reboot:[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]EnableTCPChimney = 0 (DWORD)EnableRSS = 0 (DWORD)EnableTCPA = 0 (DWORD)
More information can be found at:
Scalable Networking: Network Protocol Offload - Introducing TCP Chimneyhttp://www.microsoft.com/whdc/device/network/TCP_Chimney.mspx
Scalable Networking: Network Protocol Offload - Introducing TCP Chimneyhttp://www.microsoft.com/downloads/details.aspx?FamilyId=6AEE2E62-B708-44C1-BABE-FC0E7B0F02BD&displaylang=en