DHCP Question

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I will be setting up a Windows 2003 Small Business Server running AD.

The domain will consist of 10 workstations and a printer.

The currently just have 2 workstation that connects to the internet
wirelessly using a Netgear 54g router/modem. This router does DHCP and NAT.

My questions is, when i set up the domain, should i continue to allow the
router to give DHCP, fix the router and servers address? or

Allow the server to provide all DHCP?

Please could some explain the pros and cons of each method and wheich one is
best to go with?

Many thanks in advance :)
 
You should allow the server to assign DHCP addresses, putting the server and
the router on fixed IP addressing and making reservations in the server's
DHCP for those reserved addresses. Microsoft Active Directory, DNS and DHCP
all work hand-in-hand to keep network addresses and domain membership
organized correctly.
 
Thaks Richard, that helps.

Can i ask, is it best to leave NAT on the router then so it continues acting
as a firewall?

and i will take DHCP off the router.

Many thanks

Richard G. Harper said:
You should allow the server to assign DHCP addresses, putting the server and
the router on fixed IP addressing and making reservations in the server's
DHCP for those reserved addresses. Microsoft Active Directory, DNS and DHCP
all work hand-in-hand to keep network addresses and domain membership
organized correctly.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


PeOpLeS said:
I will be setting up a Windows 2003 Small Business Server running AD.

The domain will consist of 10 workstations and a printer.

The currently just have 2 workstation that connects to the internet
wirelessly using a Netgear 54g router/modem. This router does DHCP and
NAT.

My questions is, when i set up the domain, should i continue to allow the
router to give DHCP, fix the router and servers address? or

Allow the server to provide all DHCP?

Please could some explain the pros and cons of each method and wheich one
is
best to go with?

Many thanks in advance :)
 
PeOpLeS said:
Thaks Richard, that helps.

Can i ask, is it best to leave NAT on the router then so it continues
acting as a firewall?

In general I'd say yes - but are you using Standard or Premium? Premium has
ISA, so you'll need two NICs. Personally, I don't use ISA (if I want it, I
sure don't want it on my sole DC/server) and use hardware firewalls and a
single NIC in the box.
and i will take DHCP off the router.
Yep.

Many thanks

Richard G. Harper said:
You should allow the server to assign DHCP addresses, putting the
server and the router on fixed IP addressing and making reservations
in the server's DHCP for those reserved addresses. Microsoft Active
Directory, DNS and DHCP all work hand-in-hand to keep network
addresses and domain membership organized correctly.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


PeOpLeS said:
I will be setting up a Windows 2003 Small Business Server running
AD.

The domain will consist of 10 workstations and a printer.

The currently just have 2 workstation that connects to the internet
wirelessly using a Netgear 54g router/modem. This router does DHCP
and NAT.

My questions is, when i set up the domain, should i continue to
allow the router to give DHCP, fix the router and servers address?
or

Allow the server to provide all DHCP?

Please could some explain the pros and cons of each method and
wheich one is
best to go with?

Many thanks in advance :)
 
Its the standard version. So you recommend just using the router for NAT as
a firewall and as my internet connecting device?

Cheers once again

Lanwench said:
PeOpLeS said:
Thaks Richard, that helps.

Can i ask, is it best to leave NAT on the router then so it continues
acting as a firewall?

In general I'd say yes - but are you using Standard or Premium? Premium has
ISA, so you'll need two NICs. Personally, I don't use ISA (if I want it, I
sure don't want it on my sole DC/server) and use hardware firewalls and a
single NIC in the box.
and i will take DHCP off the router.
Yep.

Many thanks

Richard G. Harper said:
You should allow the server to assign DHCP addresses, putting the
server and the router on fixed IP addressing and making reservations
in the server's DHCP for those reserved addresses. Microsoft Active
Directory, DNS and DHCP all work hand-in-hand to keep network
addresses and domain membership organized correctly.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


I will be setting up a Windows 2003 Small Business Server running
AD.

The domain will consist of 10 workstations and a printer.

The currently just have 2 workstation that connects to the internet
wirelessly using a Netgear 54g router/modem. This router does DHCP
and NAT.

My questions is, when i set up the domain, should i continue to
allow the router to give DHCP, fix the router and servers address?
or

Allow the server to provide all DHCP?

Please could some explain the pros and cons of each method and
wheich one is
best to go with?

Many thanks in advance :)
 
PeOpLeS said:
Its the standard version. So you recommend just using the router for
NAT as a firewall and as my internet connecting device?

Yes, I would....ISA is fine, but one of the things about SBS is everything
goes on one server. And I don't want my server acting as a firewall - if you
do buy Premium, I'd *still* want a hardware appliance outside that. But
dual-NIC configs can cause problems on a DC/DNS/WINS server...and I don't
bother with it. SBS folks often insist on this, but I don't.
Cheers once again

Lanwench said:
PeOpLeS said:
Thaks Richard, that helps.

Can i ask, is it best to leave NAT on the router then so it
continues acting as a firewall?

In general I'd say yes - but are you using Standard or Premium?
Premium has ISA, so you'll need two NICs. Personally, I don't use
ISA (if I want it, I sure don't want it on my sole DC/server) and
use hardware firewalls and a single NIC in the box.
and i will take DHCP off the router.
Yep.

Many thanks

:

You should allow the server to assign DHCP addresses, putting the
server and the router on fixed IP addressing and making
reservations in the server's DHCP for those reserved addresses.
Microsoft Active Directory, DNS and DHCP all work hand-in-hand to
keep network addresses and domain membership organized correctly.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


I will be setting up a Windows 2003 Small Business Server running
AD.

The domain will consist of 10 workstations and a printer.

The currently just have 2 workstation that connects to the
internet wirelessly using a Netgear 54g router/modem. This router
does DHCP and NAT.

My questions is, when i set up the domain, should i continue to
allow the router to give DHCP, fix the router and servers address?
or

Allow the server to provide all DHCP?

Please could some explain the pros and cons of each method and
wheich one is
best to go with?

Many thanks in advance :)
 
I think SBS standard edition only requires i NIC. Am i right? i think so ?

Lanwench said:
PeOpLeS said:
Its the standard version. So you recommend just using the router for
NAT as a firewall and as my internet connecting device?

Yes, I would....ISA is fine, but one of the things about SBS is everything
goes on one server. And I don't want my server acting as a firewall - if you
do buy Premium, I'd *still* want a hardware appliance outside that. But
dual-NIC configs can cause problems on a DC/DNS/WINS server...and I don't
bother with it. SBS folks often insist on this, but I don't.
Cheers once again

Lanwench said:
PeOpLeS wrote:
Thaks Richard, that helps.

Can i ask, is it best to leave NAT on the router then so it
continues acting as a firewall?

In general I'd say yes - but are you using Standard or Premium?
Premium has ISA, so you'll need two NICs. Personally, I don't use
ISA (if I want it, I sure don't want it on my sole DC/server) and
use hardware firewalls and a single NIC in the box.

and i will take DHCP off the router.

Yep.

Many thanks

:

You should allow the server to assign DHCP addresses, putting the
server and the router on fixed IP addressing and making
reservations in the server's DHCP for those reserved addresses.
Microsoft Active Directory, DNS and DHCP all work hand-in-hand to
keep network addresses and domain membership organized correctly.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


I will be setting up a Windows 2003 Small Business Server running
AD.

The domain will consist of 10 workstations and a printer.

The currently just have 2 workstation that connects to the
internet wirelessly using a Netgear 54g router/modem. This router
does DHCP and NAT.

My questions is, when i set up the domain, should i continue to
allow the router to give DHCP, fix the router and servers address?
or

Allow the server to provide all DHCP?

Please could some explain the pros and cons of each method and
wheich one is
best to go with?

Many thanks in advance :)
 
I see that you have advice that agrees with mine, so I will say nothing
more. :-)

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


PeOpLeS said:
Thaks Richard, that helps.

Can i ask, is it best to leave NAT on the router then so it continues
acting
as a firewall?

and i will take DHCP off the router.

Many thanks

Richard G. Harper said:
You should allow the server to assign DHCP addresses, putting the server
and
the router on fixed IP addressing and making reservations in the server's
DHCP for those reserved addresses. Microsoft Active Directory, DNS and
DHCP
all work hand-in-hand to keep network addresses and domain membership
organized correctly.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


PeOpLeS said:
I will be setting up a Windows 2003 Small Business Server running AD.

The domain will consist of 10 workstations and a printer.

The currently just have 2 workstation that connects to the internet
wirelessly using a Netgear 54g router/modem. This router does DHCP and
NAT.

My questions is, when i set up the domain, should i continue to allow
the
router to give DHCP, fix the router and servers address? or

Allow the server to provide all DHCP?

Please could some explain the pros and cons of each method and wheich
one
is
best to go with?

Many thanks in advance :)
 
in message
:I think SBS standard edition only requires i NIC. Am i right? i think so ?

LW was referring to ISA needing two NICs. SBS 2K3 Standard doesn't come
with ISA so 1 NIC is sufficient.
You may find this beneficial...

http://www.experts-exchange.com/Operating_Systems/Q_20832831.html


--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382
 
You are all so helpful. I know i am going to like it around here.

Thanks again gents :)

Richard G. Harper said:
I see that you have advice that agrees with mine, so I will say nothing
more. :-)

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


PeOpLeS said:
Thaks Richard, that helps.

Can i ask, is it best to leave NAT on the router then so it continues
acting
as a firewall?

and i will take DHCP off the router.

Many thanks

Richard G. Harper said:
You should allow the server to assign DHCP addresses, putting the server
and
the router on fixed IP addressing and making reservations in the server's
DHCP for those reserved addresses. Microsoft Active Directory, DNS and
DHCP
all work hand-in-hand to keep network addresses and domain membership
organized correctly.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


I will be setting up a Windows 2003 Small Business Server running AD.

The domain will consist of 10 workstations and a printer.

The currently just have 2 workstation that connects to the internet
wirelessly using a Netgear 54g router/modem. This router does DHCP and
NAT.

My questions is, when i set up the domain, should i continue to allow
the
router to give DHCP, fix the router and servers address? or

Allow the server to provide all DHCP?

Please could some explain the pros and cons of each method and wheich
one
is
best to go with?

Many thanks in advance :)
 
: You are all so helpful. I know i am going to like it around here.
:
: Thanks again gents :)

and all this time I thought Lanwench was a gentette.
 
Howard Hartman said:

The Window's major networking services (DNS, WINS, DHCP) are designed to all
work togther and compliment each other. Run the DHCP on the Windows Server
so that it works properly with DNS.
 
Back
Top