Windows 2003 Server, Dual Nics and 1 Gateway

I am trying to turn up a second NIC on my Windows 2003 File Server.  The purpose is to try and add additional bandwidth for users.  I am not sure if I need to attempt to bridge the 2 together or give them separate IP Addresses.  I only have 1 gateway address and Windows did not like me putting the same gateway address on 2 different NICs.  This server is using the following roles, File, DNS, DHCP, and License Server.  I would like to get some feedback on the appropriate way to do this to implement this second NIC
mcrouch1Asked:
Who is Participating?
 
Subnet_ThisSystems AdministratorCommented:
This is a pretty good guide to setting this up on 08' server. The setup options aren't that far off from 2003.

http://blogs.technet.com/b/josebda/archive/2010/09/03/using-the-multiple-nics-of-your-file-server-running-windows-server-2008-and-2008-r2.aspx
0
 
Subnet_ThisSystems AdministratorCommented:
Option 2.2 in that link is most likely what you are looking for.
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
juleswaleCommented:
Hi,

Your can use Windows to bridge the Nic's or if teh Network card manufacturers have some teaming software that is the best way to go.

0
 
andyalderCommented:
Teaming also relies on the switch so we need to know what that is.
0
 
mcrouch1Author Commented:
Switch is a Cisco 2970G

Integrated Intel Pro 1000/EB with I/O Acceleration NICs.  

I dont see anything in the Advanced properties of the NICs that would allow me to bridge them.  There is a "Gigabit Master Slave Mode" option?
0
 
Subnet_ThisSystems AdministratorCommented:
Another option would be to just set up the other NIC with an IP sequential to the existing one (ex.- if existing was 192.168.0.5, make the second NIC 192.168.0.6). You can then spread your server connections on the workstation side manually over to the other IP.

When I started at my current job, it was set up like this. We currently have 7 network shares that each workstation connects to upon logging in. So, these shares were set to that alternate IP and the rest of our domain services went through the main IP.

We have since changed this to teaming, but that would be an optional, albeit manual solution to help with load balancing.
0
 
D_VanteCommented:
Usually the cards need to be identical
I would recommend teaming them with the manufactor software not bridging them with the windows software.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.