DHCP Server on a network that already has a DHCP

  • Thread starter Thread starter Trecius
  • Start date Start date
T

Trecius

Guest
Hello:

I've a question regarding setting up a Windows 2003 SBS. We have our "main
network" at our facility that assigns IP addresses using DHCP and allows
clients to connect to the Internet. Now our group is trying to break away
from the other network. We are trying to create our own tiny network, so we
purchased our own server and our own switch.

We moved all client computers from the main network's switch and plugged
them into our switch. Now we want our server to assign IP addresses using
DHCP, right? This is fine for now. A problem arises when the clients --
that we just switched -- need Internet. The Internet is and will always be
"on" the "main network." To combat this problem, we put an additional NIC --
we'll call it NIC2 -- in our server that allows it to connect to the "main
network." How can I make it so DHCP will only assign addresses to clients
from NIC1 and not from NIC2? The only reason we need NIC2 is to get Internet.

I hope I defined my problem correctly, but should you need additional
information or a better description, please do not hesistate to ask.


Trecius
 
Re: DHCP Server on a network that already has a DHCP

Trecius <Trecius@discussions.microsoft.com> wrote:
> Hello:
>
> I've a question regarding setting up a Windows 2003 SBS. We have our
> "main network" at our facility that assigns IP addresses using DHCP
> and allows clients to connect to the Internet. Now our group is
> trying to break away from the other network.

What's the reason for that, if I might ask? If there's an existing AD
domain, I'm not sure I'd go for SBS here. How is the parent company handling
email? Is there a registered Internet domain in use for email?

Is any connection between the main facility & your own LAN needed, other
than sharing the Internet connection? I think not, but need to ask.

How many public IPs does the main facility have?

> We are trying to create
> our own tiny network, so we purchased our own server and our own
> switch.

A switch alone isn't going to help you create a separate LAN here,
if I understand your desired configuration....you need a router.

I would recommend something like the rudimentary diagram below. Again, I'm
presuming you don't need to share files/whatnot between your LAN and the
rest of the network, which it sounds like you don't.

-------------------------------------------------

*ISP's modem*
|
|-----Ethernet switch-----|
| |
(123.123.123.1) (123.123.123.2)
*RouterA* *RouterB*
| |
|----LANA----| |----LANB----|

-------------------------------------------------



>
> We moved all client computers from the main network's switch and
> plugged
> them into our switch. Now we want our server to assign IP addresses
> using DHCP, right?

Yes, ideally. You need a specific DNS configuration, and the main facility's
router won't hand out the right DNS server addresses or DNS suffix....

> This is fine for now. A problem arises when the
> clients -- that we just switched -- need Internet. The Internet is
> and will always be "on" the "main network." To combat this problem,
> we put an additional NIC -- we'll call it NIC2 -- in our server that
> allows it to connect to the "main network."

Oooh, no. Don't do that. If you aren't using SBS Premium with ISA, two NICs
in a DC is a Bad IDea. You need a router (ideally, a decent firewall
appliance will do this for you, such as a SonicWALL/Watchguard/Pix). See
above.

>How can I make it so
> DHCP will only assign addresses to clients from NIC1 and not from
> NIC2? The only reason we need NIC2 is to get Internet.
>
> I hope I defined my problem correctly, but should you need additional
> information or a better description, please do not hesistate to ask.
>
>
> Trecius

HTH.... and note that as SBS is its own beast, all SBS questions really
belong in microsoft.public.windows.server.sbs. Do not try to set up or
administer SBS without using its wizards, or you will be very sad.
 
Back
Top