• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win 2003 Small business: DHCP SUBNET question

M

mmx

Diamond Member
I got a new poweredge 2900 with dual NIC cards.

In the office we have a cisco router connected to a t1/dsl line. The router does not have DHCP, but is firewall enable. The idea is to have the server act as a DHCP SERVER for the computers.
One NIC is connected from the router to the server, and the other nic goes to a 24 port switch where all the computers are connected to.

The problem that I have, being a newbie with win2003 is that I need the subnet to be 192.168.1.14 for all the computers(this is the subnet STATIC of the router too) however one nic is connected to the router with the .14, but the one to the switch is .6

How do I get both NICs to have the .14 subnet?
 
you can't drop this kind of post without giving the info about netmask. Looking at those, both ARE in the same subnet
 
what do you mean?

Basically, in the old server which only had one NIC, it was configured to be .14 subnet DHCP, so the server gave IP's and everyone was under .14 including the router.

But with dual nic, I can't get both nic's to act as one.
Reason I need to .14 is that the firewall, and other computers are configured to the .14, so it will be a hassle to change all.
 
mmx,

Your topic title suggests you are using Windows Small Business Server 2003 in dual-NIC mode.

If so, then once you do some reading and figure out what you want to do with your NIC addresses, BE SURE to use the SBS "Change Server IP Address" Wizard to change the IP address/subnet of the "internal" NIC. If you make the changes manually, you will likely mess up your SBS server so badly that you'll have to re-install SBS to fix it.

There are several internal dependencies on that internal NIC address that will bring SBS to a standstill if not modified correctly. Just use that Wizard and you'll be fine.

Also, as a general hint, the subnet of your "Internet" NIC MUST be different than the subnet of your "Internal" NIC. If you put them on the same subnet, your Windows Server is going to get really confused as to which direction to send data.
 
So I shouldn't configure both NICS? wHATS THE POINT OF GETTING DUAL NIC THEN? wouldn't it translate into better performance?

I just want the DHCP to the switch to act as it was talking directly to the Router.
 
Originally posted by: mmx
So I shouldn't configure both NICS? wHATS THE POINT OF GETTING DUAL NIC THEN? wouldn't it translate into better performance?

I just want the DHCP to the switch to act as it was talking directly to the Router.
Click to expand...
I didn't say not to configure the NICs. I said you should let SBS do it for you.

Dual-NIC mode is the preferred way of installing SBS 2003, since it allows SBS's firewall to function, avoids many common configuration errors, and is the only way that will allow ISA 2004 (if you install it) to monitor Internet traffic.

If you are going to use Dual-NIC mode, you'll be using SBS's built-in DHCP Server, as well as its DNS and WINS Servers for your client PCs. Any hardware router ahead of the SBS Server is used only as a preliminary firewall and as the Default Gateway for the SBS Server.

I recommend you take a look at a good book on installing SBS. Harry Brelsford's book is a good starting point, and will help you install SBS using acknowledged Best Practices. A mis-configured SBS Server is pretty worthless.
 
Originally posted by: mmx
So I shouldn't configure both NICS? wHATS THE POINT OF GETTING DUAL NIC THEN? wouldn't it translate into better performance?

I just want the DHCP to the switch to act as it was talking directly to the Router.
Click to expand...

I would REALLY suggest getting an SBS consultant in there to ensure proper setup. It sounds like you are not a network guy, and this requires "network guy" type skills.
 
I'm not an expert.I'm still learing. I got everything working, except working in a dual NIC setup is sometthing new to me.
 
dual NICS isn't for performance, its to seperate the outside traffic from the internal.

One is hooked to the internet and one to your LAN.
 
Right no I connected with only one nic which helpen the subnet issue,

If I were to use dual nics - how would I tell a static IP to pass through 2 firewalls? one from the server the other from the cisco router?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top