http://weblogs.asp.net/adweigert/archive/tags/Windows+Server+2008/default.aspxTags: Windows Server 2008enCommunityServer 2007 SP1 (Build: 20510.895)http://weblogs.asp.net/adweigert/archive/2008/03/15/windows-server-2008-vista-network-scalability-quot-feature-quot.aspxSun, 16 Mar 2008 00:05:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:5978476adweigertadweigert0http://weblogs.asp.net/adweigert/rsscomments.aspx?PostID=5978476http://weblogs.asp.net/adweigert/archive/2008/03/15/windows-server-2008-vista-network-scalability-quot-feature-quot.aspx#comments<P mce_keep="true">I highly recommend, if you are running Windows Server 2008 or Windows Vista, to disable the network scalability features. If you don't, you run the chance of one day running into "slow" performance of an application between one client or server and another. You will spend countless hours trying to debug why the network communication is so slow to that feature from that one client when it works fine for you and serveral others in the same area and with the same configuration. As far as I am concerned, TCP offloading has been a failure since the beginning, and I am not sure who is to blame, Microsoft or the hardware vendors. Oddly enough, I even saw the "symptoms" on a virtual server.</P> <P mce_keep="true">From an Administrator command prompt:</P> <BLOCKQUOTE> <P mce_keep="true"><FONT size=2>netsh int tcp set global rss=disabled chimney=disabled autotuninglevel=disabled</FONT></P></BLOCKQUOTE> <P mce_keep="true">Enjoy!<FONT size=2></P></FONT><img src="http://weblogs.asp.net/aggbug.aspx?PostID=5978476" width="1" height="1">.netNetwork ScaliblityWindows Server 2008Windows Vista