For a single server, what you're essentially asking about in maximizing network throughput is not so much load balancing, but teaming.
Load Balancing is typically done by a "front-end" device that doesn't do a whole lot of processing, other than to keep track of traffic, and send any new incoming "requests" to the currently least-used application server. Multiple devices are involved here.
Teaming (or more loosely, bridging) makes multiple network cards appear as one card. So for example if you have 2 NICs at 1Gb speed, you can team them together to get up to 2Gb of throughput. With teaming, it is very important to make sure that the network hardware you're plugging into supports it. Most likely, you will also have to configure the switch, so that it knows to team the physical ports together. Otherwise, traffic can be delivered arbitrarily between the physical ports causing many connection issues (broken connections, lots of retransmissions, severely reduced throughput, etc).
So for the most network throughput on a single server, use NIC teaming. For distributing an application's load across a group of separate servers, think load balancing.
Problem was with Broadcom NIC drivers. This is the reason why network admins generally prefers Intel NICs over Broadcom. Following is the detailed procedure to solve this issue (Note that I have verified this procedure only Dell PE 1950, but it may work for other familities of Dell PE as well)-
NIC loses Static IP Configuration
What to do:
a. Uninstall old Broadcom Advanced Control Suite.
b. Clean the system of older Broadcom file versions.
c. Reinstall the Broadcom Drivers.
How to do it:
a. Download the new Broadcom drivers
i. 32-bit http://ftp.us.dell.com/network/Bcom_LAN_12.4_W2K3_8_A02.exe
ii. 64-bit http://ftp.us.dell.com/network/Bcom_LAN_12.4_W2K3_8_64_A03.exe
Important!
For Server 2008, leave all .Net Framework Versions in place, continue at step D.
b. Ensure Microsoft’s .Net Framework 2.0 SP1 is installed.
c. Install .Net Framework 2.0 SP1 from Microsoft.
d. Ensure .Net Framework 2.0 SP2, 3.0 and 3.5 are NOT installed. They can be reinstalled after installing the new Broadcom drivers.
e. Disable/Pause any Antivirus and Threat-Protection scanners that can interrupt the Broadcom driver installation.
i. Check for Symantec Endpoint.
ii. If it is installed, ensure Endpoint Patch RM4 (or newer) is installed.
iii. If RM4 (or newer) cannot be installed, then uninstall Endpoint. Endpoint may be re-installed later.
f. Extract BCOMRemove.zip
g. Rename the following files:
i. BCOM_Remove.txt -> BCOM_Remove.vbs
ii. BCOM_Finalize.txt -> BCOM_Finalize.vbs
h. Uninstall the existing Broadcom drivers through Add/Remove Programs.
i. Select No for restart now
j. Uninstall all Broadcom NICs and BASFND from Device Manager.
i. Click Start -> Run -> Type CMD.
ii. Type set devmgr_show_nonpresent_devices=1.
iii. Type Start DEVMGMT.MSC.
iv. Click View.
v. Click Show Hidden Devices.
vi. Expand the Network Adapters section on the left.
vii. Remove all listed Broadcom network adapters.
1. Right-click the network adapter
2. Click Uninstall.
viii. Expand the Non-Plug and Play Drivers section on the left.
ix. Remove all instances of BASFND
x. Expand the System devices section on the left.
xi. Remove all instances of BASFND
xii. Remove all listed Broadcom network adapters.
1. Right-click the network adapter
2. Click Uninstall
k. Double-Click BCOM_Remove.vbs
l. Reboot
m. Enable NICs in BIOS.
n. Cancel the Found new hardware wizard
o. Double-click BCOM_Finalize.vbs
p. Install the Broadcom Drivers
i. Double-click the Broadcom installer to extract the files to C:\Broadcom\w2k3_8.
1. 32-bit: Bcom_LAN_12.4_W2K3_8_A02.exe
2. 64-bit: Bcom_LAN_12.4_W2K3_8_64_A03.exe
ii. Navigate to C:\Broadcom\w2k3_8\Driver_Management_Apps_Installer
iii. Double-Click Setup.Exe.
iv. Follow the installation wizard to complete the installation.
q. For Domain Controllers, follow Microsoft KB article 325356 (How to remove and reinstall TCP/IP on a Windows Server 2003 domain controller)
r. For Non-Domain Controllers, follow Microsoft KB article 317518. (How to reset "Internet Protocol (TCP/IP)" in Windows Server 2003)
s. netsh interface ip reset resetlog.txt
Best Answer
Well, guess what is a feature in 2012 "WHat is New"`? Hint - it is NIC teaming.
Pre 2012 there is no operating system level NIC teaming.
That does not mean there is NO nic teaming - just not by the OS. Head over to broadcom and get the latest driver and read the documentation. If you are lucky they can do NIC-Teaming in the driver. Intel CAN do that.
A little google returned to me:
http://www.broadcom.com/support/ethernet_nic/management_applications.php and a youtube video about how to cereate NIC teaming with Broadcom drivers: http://www.youtube.com/watch?v=x2nq-qEwAzg
But generally - upgrading to 2012 is the way to go.