[Bigpants2k]

Hi there,

Here is my problem, I am running Win2k server sp4.
I connect using a boot disk which pulls down a DHCP address, which works fine.

I want to add more nics to my server, so I can have different people connecting to different nics, so I can get a gig throughput to each of my switches.

But when I add more nics, DHCP won't push addresses down through them, even though I have tried to bind them in the advanced settings.

I have tried splitting my address range into different scopes i.e.:
192.168.100.10-192.168.100.40, the first range works fine then when I try and add a new range i.e.: 192.168.100.41-192.168.100.100 it says that this range has already being used.(these are all on the same subnet mask)

My router is on 192.168.100.1. and I need everyone to access this.

How would you set up this config?

Thanks guys.

[Curlyben]

OK a very odd set up here.

The best course of action is to assign static IP address to your server NIC, then you should be able to Team/Bind more together and use some fault tolerance.

Windows 2000 IP changing
Teaming

Each NIC then appears to the rest of the network as ONE unit
IP Address: 192.168.100.x
Subnet 255.255.255.0
Gateway 192.168.100.1


WHat box is doing the DHCP function ?
Have you tried setting the scope up for a larger range, e.g. 192.168.100.10 to 192.168.100.100 ?
Do you have any static addresses already assigned ?
Are clients setup for Dynamic DHCP ?

Hope this helps

[Bigpants2k]

Sorry I forgot to mention that all the nics in my server have static addresses.

What I am trying to acheave is this:

I have about 10 guys, who will be downloading ghost images from my server.(This box is my DHCP server and also has attached storage, somewhere about 1TB).
I have guys in different departments,but all in the same location. So idealy I would like each department to have 1 GB nic, to themselves. This would then be attached to a switch.
I need DHCP running as this is the way I boot to the server.

If you have any other ideas please feel free to tell me.

Thanks

[Curlyben]

I still believe that your best course of action is to team the NIC and use some form of load balancing.
Something like this would probably be your best bet.

Transmit Load Balancing (TLB) - balances the transmit traffic among the team members, but does not require any special switch intelligence or switch configuration. In addition, TLB teams can be split across switches as long as all members are in the same layer 2 network. In TLB teams, receive traffic is not load balanced, but is received on a single team member. TLB is a standard feature of ProLiant Teaming.

Does your server OEM supply any form of Teaming software ?

I personally use this method on all my servers for redundancy and its works great.

Trying to assign different IP's to different NIC's in the same box will cause you a MAJOR headache.

[Bigpants2k]

Im using a DL380 at the moment.

My old setup I used to have 2 x nics teamed.

Im just configuring my new box at the moment.

To be honest I don't need redundancy, I just need as much throughput as possible.

[Curlyben]

TLB, as mentioned above, does exactly that.
I'm running it on my ML370 Db server. 2x 100 Meg NIC get 200 Meg thro' put.

This is all done using the HP Teaming software

Here's what the team looks like: