Have you checked if the NIC setting supports TCP Offloading? So, NIC has to offer this is an option to that work correctly. This is stated on the KB: http://support.microsoft.com/kb/951037 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. Some of the NIC manufactures refer this feature as TOE (TCP Offload Engine).

Have you checked if the NIC setting supports TCP Offloading? So, NIC has to offer this is an option to that work correctly. This is stated on the KB: http://support.microsoft.com/kb/951037 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. Some of the NIC manufactures refer this feature as TOE (TCP Offload Engine).

One of nics does (dual port) http://ark.intel.com/products/50486/Intel-PRO1000-MT-Dual-Port-Server-Adapter Two of them do not. http://www.intel.com/content/www/us/en/desktops/intel-pro-1000-gt-desktop-adapter-datasheet.html

One of nics does (dual port) http://ark.intel.com/products/50486/Intel-PRO1000-MT-Dual-Port-Server-Adapter Two of them do not. http://www.intel.com/content/www/us/en/desktops/intel-pro-1000-gt-desktop-adapter-datasheet.html

Hi, Thank you for your post. So one NIC does not support TCP offload? Please check the TCP offload function in Device Manager--the advanced properties page of the network adapter. If there are more inquiries on this issue, please feel free to let us know. Regards, Rick Tan TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Rick Tan TechNet Community Support

Hi, Thank you for your post. So one NIC does not support TCP offload? Please check the TCP offload function in Device Manager--the advanced properties page of the network adapter. If there are more inquiries on this issue, please feel free to let us know. Regards, Rick Tan TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Rick Tan TechNet Community Support

There is one dual port nic in the server that does support TCP offloading. There are two, single port, nics that do not. All nics have TCP offloading enabled as pictured below.

There is one dual port nic in the server that does support TCP offloading. There are two, single port, nics that do not. All nics have TCP offloading enabled as pictured below.

Hi, So you set the two single NIC port as one dual port NIC? Microsoft does not provide any support for NIC teaming, please contact your hardware vendor for assistance. http://support.microsoft.com/kb/968703 Regards, Rick Tan TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Rick Tan TechNet Community Support

Hi, So you set the two single NIC port as one dual port NIC? Microsoft does not provide any support for NIC teaming, please contact your hardware vendor for assistance. http://support.microsoft.com/kb/968703 Regards, Rick Tan TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Rick Tan TechNet Community Support

No, check out the model of the nic. It is one nic that has two ports. There is no teaming involved whatsoever. And the fact that I have two nics in the system that do not support tcp offloading is really irrelevant. I have disabled those nics and attempted to use the 1 nic that does support tcp offloading, but have still been unsuccessful. I'm looking for suggestions as to how to get the offloading features to work properly on a nic that supports it.

No, check out the model of the nic. It is one nic that has two ports. There is no teaming involved whatsoever. And the fact that I have two nics in the system that do not support tcp offloading is really irrelevant. I have disabled those nics and attempted to use the 1 nic that does support tcp offloading, but have still been unsuccessful. I'm looking for suggestions as to how to get the offloading features to work properly on a nic that supports it.

I enabled large send offload, but unfortunately, no change.

I enabled large send offload, but unfortunately, no change.

No, check out the model of the nic. It is one nic that has two ports. There is no teaming involved whatsoever. And the fact that I have two nics in the system that do not support tcp offloading is really irrelevant. I have disabled those nics and attempted to use the 1 nic that does support tcp offloading, but have still been unsuccessful. I'm looking for suggestions as to how to get the offloading features to work properly on a nic that supports it.

There is one dual port nic in the server that does support TCP offloading. There are two, single port, nics that do not. All nics have TCP offloading enabled as pictured below.

One of nics does (dual port) http://ark.intel.com/products/50486/Intel-PRO1000-MT-Dual-Port-Server-Adapter Two of them do not. http://www.intel.com/content/www/us/en/desktops/intel-pro-1000-gt-desktop-adapter-datasheet.html

I enabled large send offload, but unfortunately, no change.

I see you have TCP/UDP and IP checksum offload enabled but they are not related to TCP Chimney (Connection Offload or Full TCP offload). Additionally I see also you have enabled Large Send Offload and this delegates the segmentation of large TCP packets process to the NIC. Currently most of the NICs have them enabled by default. If you read the description above on the Intel NIC when you highlight IPv4 Checksum it says clearly what will offload. However, only some NICs support TCP Chimney (Connection Offload or Full TCP offload). Some manufactures refer to it as TCP offload engine or TOE. TCP offload engine http://en.wikipedia.org/wiki/Tcp_offload_engine I’m summarizing here what NDIS 6.0 supports for task offload: Checksum tasks - The TCP/IP transport can offload the calculation and validation of IP and TCP checksums. Large Send Offload - The TCP/IP transport can offload the segmentation of large TCP packets. Connection offload - Enable configuration of connection offload services such as TCP chimney offload. There are points to differentiate here as TCP/IP has multiple fields each one offers different functions and couple them can be partially offloaded. The first two offload part of those functions (checksum and large segments) and the third will fully offload the connection to the NIC. Reference: NDIS 6.0 Support for Task Offload http://msdn.microsoft.com/en-us/library/windows/hardware/ff564713(v=vs.85).aspx So, at this point recommend you double check with manufacture about if the NIC model you have really supports to TCP Chimney/TOE or Full TCP Offload. I hope this gives you some clarification. -Daniel Mauser

Hi, Well, I know you have three NIC and you have disabled the two NIC which do not support TCP Chimney offload. Now, in your NIC Advanced properties, please check if you enable Large Send Offload(IPv4) options. Regards, Rick Tan TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here. Rick Tan TechNet Community Support

I'm trying to enable TCP Offloading on a 2008R2 box. Everything I try doesn't seem to work. I am checking weather it is offloading by using the following command netstat -t, as listed in the following article. http://support.microsoft.com/kb/951037 This is what I have tried: - netsh int tcp set global chimney=enabled (restarted) - added the following registry entry " HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" EnableTCPChimney set to 1 (Restarted) - Enabled all TCP offload features within the NIC Configuration page (Restarted) According to the article, this is what I should see: This is what I keep getting after applying all the changes that should enable it. Here is that status of the tcp parameters

Hi, So you set the two single NIC port as one dual port NIC? Microsoft does not provide any support for NIC teaming, please contact your hardware vendor for assistance. http://support.microsoft.com/kb/968703 Regards, Rick Tan TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Rick Tan TechNet Community Support

Have you checked if the NIC setting supports TCP Offloading? So, NIC has to offer this is an option to that work correctly. This is stated on the KB: http://support.microsoft.com/kb/951037 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. Some of the NIC manufactures refer this feature as TOE (TCP Offload Engine).

Hi, Thank you for your post. So one NIC does not support TCP offload? Please check the TCP offload function in Device Manager--the advanced properties page of the network adapter. If there are more inquiries on this issue, please feel free to let us know. Regards, Rick Tan TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Rick Tan TechNet Community Support

I see you have TCP/UDP and IP checksum offload enabled but they are not related to TCP Chimney (Connection Offload or Full TCP offload). Additionally I see also you have enabled Large Send Offload and this delegates the segmentation of large TCP packets process to the NIC. Currently most of the NICs have them enabled by default. If you read the description above on the Intel NIC when you highlight IPv4 Checksum it says clearly what will offload. However, only some NICs support TCP Chimney (Connection Offload or Full TCP offload). Some manufactures refer to it as TCP offload engine or TOE. TCP offload engine http://en.wikipedia.org/wiki/Tcp_offload_engine I’m summarizing here what NDIS 6.0 supports for task offload: Checksum tasks - The TCP/IP transport can offload the calculation and validation of IP and TCP checksums. Large Send Offload - The TCP/IP transport can offload the segmentation of large TCP packets. Connection offload - Enable configuration of connection offload services such as TCP chimney offload. There are points to differentiate here as TCP/IP has multiple fields each one offers different functions and couple them can be partially offloaded. The first two offload part of those functions (checksum and large segments) and the third will fully offload the connection to the NIC. Reference: NDIS 6.0 Support for Task Offload http://msdn.microsoft.com/en-us/library/windows/hardware/ff564713(v=vs.85).aspx So, at this point recommend you double check with manufacture about if the NIC model you have really supports to TCP Chimney/TOE or Full TCP Offload. I hope this gives you some clarification. -Daniel Mauser

Hi, I would like to confirm what is the current situation? If there is anything that I can do for you, please do not hesitate to let me know, and I will be happy to help. Regards, Rick Tan TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.Rick Tan TechNet Community Support

Hi, I would like to confirm what is the current situation? If there is anything that I can do for you, please do not hesitate to let me know, and I will be happy to help. Regards, Rick Tan TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.Rick Tan TechNet Community Support

Daniel, it appears that you are correct. These nics support some offloading features, but not Full TOE. Intel has what they call I/OAT, which is their answer to TOE. http://www.intel.com/content/www/us/en/wireless-network/accel-technology.html Unfortunately HP servers do not support this I/OAT technology because they are not Intel boards. They have the required intel chipset, but the boards have to be manufactured by intel as well. Kinda lame. Thanks for the help guys!

Daniel, it appears that you are correct. These nics support some offloading features, but not Full TOE. Intel has what they call I/OAT, which is their answer to TOE. http://www.intel.com/content/www/us/en/wireless-network/accel-technology.html Unfortunately HP servers do not support this I/OAT technology because they are not Intel boards. They have the required intel chipset, but the boards have to be manufactured by intel as well. Kinda lame. Thanks for the help guys!

Daniel, it appears that you are correct. These nics support some offloading features, but not Full TOE. Intel has what they call I/OAT, which is their answer to TOE. http://www.intel.com/content/www/us/en/wireless-network/accel-technology.html Unfortunately HP servers do not support this I/OAT technology because they are not Intel boards. They have the required intel chipset, but the boards have to be manufactured by intel as well. Kinda lame. Thanks for the help guys!

Hi, I would like to confirm what is the current situation? If there is anything that I can do for you, please do not hesitate to let me know, and I will be happy to help. Regards, Rick Tan TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.Rick Tan TechNet Community Support