Scope:

Discusses possible cause of slow file transfer and connectivity with Windows 2003 SP2, and all newer operating systems due to TCP Chimney Offloading.

Original – 5/2009
Edit: 8/19/2009 – Reworded for syntax, as well as included a disclaimer about DC multihoming, and restructured paragraphs to be more concise.
10/26/2014 – Updated.
—

Preface

You notice that network shares (UNC and mapped drives) disconnect from the server, after a server has been running for a period of time such as a couple of weeks, and in some cases with heavy usage, a few hours. A server restart temporarily fixes the issue only to return.

This may be due to the new RSS TCP Chimney Offload feature enabled on 2003 SP2 and newer servers.

You may or may not be seeing the following errors when this occurs:
System Error 64
System Error 53

Disclaimer based on your infrastructure configuration

I just want to point out a common configuration error before making any changes and assuming this issue is to blame on the RSS TCP Chimney feature. Any one of the following configurations can contribute or be the sole cause of this issue. Therefore, please make sure none of the following exist:

1. None of the machines (DCs, member servers and/or desktops and laptops), have been configured with an external DNS server, the router as a DNS server, or the ISP’s DNS server. This can surely cause this type of issue.

2. The AD DNS domain name is not a single label name, such as “domain” and not the minimally required format of “domain.something.”

3. The DCs are not multihomed. A multihomed DC means it may have more than one unteamed NIC on separate subnets or unteamed and on the same subnet, or a single NIC with more than one IP address.

4. RRAS is not installed on any of the DCs. RRAS introduces extra interfaces that get registered into DNS, which causes issues just as a multihomed DC.

For more information on DC multihoming and RRAS on a DC, and DNS implications such a configuration *will* cause, please read the following blog:

Multihomed DCs with DNS, RRAS, and/or PPPoE adapters
http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx

TCP Chimney Offload overview

TCP Chimney Offload is a networking technology that helps transfer the workload from the CPU to a network adapter during network data transfer. In Windows Server 2008, TCP Chimney Offload enables the Windows networking subsystem to offload the processing of a TCP/IP connection to a network adapter that includes special support for TCP/IP offload processing.

TCP Chimney Offload is available in all versions of Windows Server 2008 and Windows Vista. Both TCP/IPv4 connections and TCP/IPv6 connections can be offloaded if the network adapter supports this feature.

You must check with your network adapter vendor’s documentation or support department, to find out if the adapter supports this feature or not. If not, I would suggest to disable the TCP Chimney/RSS feature in Windows.

Two ways to handle this issue

Option 1. Disable RSS using the netsh command (preferred)
Option 2. Disable RSS in the registry

Option 1

Disable RSS using the netsh command:

netsh interface tcp set global rss=disabled
netsh interface tcp set global autotuninglevel=disabled
Reboot the server

More information on RSS and TCP Chimney Offloading on a Windows 2008 server can be found at:

Information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008
http://support.microsoft.com/kb/951037

Option 2

Disable RSS in the Registry

Add a DWORD registry key value for
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableRSS
and setting it to 0. A reboot is required to make the value go in to effect.
Set DisableTaskOffload in the Registry

Use the steps in KB904946 (link posted below) to create a DWORD value for
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DisableTaskOffload
and set it to 1.

A reboot is required to make this value go in to effect.

More information on the registry changes can be found at:

You cannot host TCP connections when Receive Side Scaling is enabled in Windows Server 2003 with Service Pack 2
http://support.microsoft.com/kb/927695

Summary

I hope this helped you to easily configure your time service and what to do if it didn’t work.

Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP – Directory Services