Having Network Problems on Win2003 SP2?

We've seen quite a few issues recently from customers having network problems on Windows Server 2003 SP2. These issue range from connections being reset to seeing things like database mirroring issues, etc. In other words, anything involving network traffic. In many of these issues, the problem is a new setting in Windows Server 2003 SP2 called TCP Chimney.

TCP Chimney is a new feature that improves network performance by offloading handling of TCP packets to the hardware layer, specifically to the network interface card (NIC). It works great if your NIC and NIC driver are capable. If they aren't, you will see strange network issues such as I described in above.

If you're experiencing problems with your network on SP2, the first step is to look for a new driver for your NIC. A new driver will sometimes correct the problem. In cases where it doesn't, disabling TCP Chimney is a good idea. If that resolves the issue, you can chalk your issue up to a NIC and/or NIC driver that just doesn't work correctly with this new feature.

1. To disable TCP Chimney, follow these steps:

2. Click Start, click Run, type cmd, and then click OK.

3. At the command prompt, type:

Netsh int ip set chimney DISABLED

4. Press the ENTER key.

No reboot or restart is required for this to take effect. It will take effect immediately.

Jim

Published 19 December 07 08:14 by jamesche
Filed under:

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# E-Bitz - SBS MVP the Official Blog of the SBS "Diva" said on December 23, 2007 3:03 AM:

Cheshire's Blog : Having Network Problems on Win2003 SP2?: http://blogs.msdn.com/jamesche/archive

# MVPs said on December 23, 2007 5:04 AM:

Cheshire's Blog : Having Network Problems on Win2003 SP2?: http://blogs.msdn.com/jamesche/archive

# Turner said on February 13, 2008 10:01 PM:

Thanks for this.  4 hours trying to troubleshoot very slow SQL Server connection, updating every device driver, searching all over for any hint of what the problem could be and this one command fixed it.  Although I fear in my case I triggered this problem by updating the Broadcom drivers last night.  So maybe newest drivers are not always best...

Leave a Comment

(required) 
(optional)
(required) 

  
Enter Code Here: Required

Search

This Blog

Syndication

Page view tracker