|
Home > Archive > alt.certification.mcse > October 2002 > How to setup DHCP behind router???
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
How to setup DHCP behind router???
|
|
|
| I'd like to setup DHCP in Win2k Server to learn it, but I'm on a
network behind a router/firewall (SMC Barracade), would this be
possible to setup without it conflicting with my network?
the DHCP server requires a *static* IP correct? can I use a
192.168.x.x addy my router gives the server as a static IP?
thanks!
| |
| Jeff Woods 2002-10-23, 9:24 pm |
| In article < 54kerukklr212pjrklepgthnp72meu
28d1@4ax.com>,
NOSPAMexoticsportscars@
hotmail.com says...
> I'd like to setup DHCP in Win2k Server to learn it, but I'm on a
> network behind a router/firewall (SMC Barracade), would this be
> possible to setup without it conflicting with my network?
Depends on whether the SMC has a built-in DHCP server. If it does, (and
it probably does) you'll have to disable DHCP in the router.
> the DHCP server requires a *static* IP correct? can I use a
> 192.168.x.x addy my router gives the server as a static IP?
Answered above. Turn OFF DHCP in the router. Assign a static IP
address to the Server box (and yes, it can be in the same 192.168.1.X
pool.... just don't include that address in the assignable pool of the
Server's DHCP server).
Once done, your W2K server will replace the SMC as the DHCP server on
your LAN.
| |
|
| On Wed, 23 Oct 2002 21:58:26 -0400, Jeff Woods <jeff@deltacomm.com>
wrote:
>In article < 54kerukklr212pjrklepgthnp72meu
28d1@4ax.com>,
> NOSPAMexoticsportscars@hotmail
.com says...
>
>> I'd like to setup DHCP in Win2k Server to learn it, but I'm on a
>> network behind a router/firewall (SMC Barracade), would this be
>> possible to setup without it conflicting with my network?
>
>Depends on whether the SMC has a built-in DHCP server. If it does, (and
>it probably does) you'll have to disable DHCP in the router.
>
>> the DHCP server requires a *static* IP correct? can I use a
>> 192.168.x.x addy my router gives the server as a static IP?
>
>Answered above. Turn OFF DHCP in the router. Assign a static IP
>address to the Server box (and yes, it can be in the same 192.168.1.X
>pool.... just don't include that address in the assignable pool of the
>Server's DHCP server).
>
>Once done, your W2K server will replace the SMC as the DHCP server on
>your LAN.
that sounds good.. so if I turn off the DHCP in the router, then the
router will simply act as a simple switch/hub right?
right now I have a win2k server DC and another comp. as a member
server, if I turn off the DHCP in the router, and setup the DC as a
DHCP server, the member server will automatically know to get it's IP
from the DC computer.
that's how I understand it, correct me if I'm wrong. I'll be trying
this out very soon, just want to understand the "theory" first.
| |
| Jeff Woods 2002-10-24, 9:26 am |
| In article < ti2frugoimfnvgnsoek5g8o3cch8fe
paf5@4ax.com>,
NOSPAMexoticsportscars@
hotmail.com says...
> >Answered above. Turn OFF DHCP in the router. Assign a static IP
> >address to the Server box (and yes, it can be in the same 192.168.1.X
> >pool.... just don't include that address in the assignable pool of the
> >Server's DHCP server).
> >
> >Once done, your W2K server will replace the SMC as the DHCP server on
> >your LAN.
>
> that sounds good.. so if I turn off the DHCP in the router, then the
> router will simply act as a simple switch/hub right?
Plus a firewall and ROUTER. It will simply not be a DHCP server. It
will still take packets and route them, determining if they need to stay
on the LAN, or be sent upstream, and will still perform any port-level
forwarding you've set up (i.e. send all requests on port 80 to
192.168.1.9, the WWW server on the LAN).
> right now I have a win2k server DC and another comp. as a member
> server, if I turn off the DHCP in the router, and setup the DC as a
> DHCP server, the member server will automatically know to get it's IP
> from the DC computer.
Correct. DHCP requests are BROADCAST requests. They go to every
machine on the network, which is why you only want one DHCP server per
network. If you left the router serving DHCP while setting up Win2K to
do so as well, BOTH the router and the server would respond when your
member server broadcast a DHCP request at boot time. The 5-step
handshaking that goes on between a DHCP client and a DHCP server would
mean that whichever server was quicker to offer up an IP address would
be the one accepted.... and the DHCP pools cannot overlap, or you'd have
the chance of assigning the same IP address to two different machines
(once from each DHCP server). Thus, only one DHCP server per network.
When the router is no longer a DHCP server, only the W2K server will
answer DHCP queries, but the router will continue to perform all of its
other former functions..... just not DHCP.
| |
| Georges Thibault 2002-10-24, 3:25 pm |
| Make sure that you block packets going to the internet on port udp 67, 68,
your ISP will like that precaution.
"Jeff Woods" <jeff@deltacomm.com> wrote in message
news:MPG.1821cb235333184d989736@east.usenetserver.com...
> In article < ti2frugoimfnvgnsoek5g8o3cch8fe
paf5@4ax.com>,
> NOSPAMexoticsportscars@
hotmail.com says...
>
> > >Answered above. Turn OFF DHCP in the router. Assign a static IP
> > >address to the Server box (and yes, it can be in the same 192.168.1.X
> > >pool.... just don't include that address in the assignable pool of the
> > >Server's DHCP server).
> > >
> > >Once done, your W2K server will replace the SMC as the DHCP server on
> > >your LAN.
> >
> > that sounds good.. so if I turn off the DHCP in the router, then the
> > router will simply act as a simple switch/hub right?
>
> Plus a firewall and ROUTER. It will simply not be a DHCP server. It
> will still take packets and route them, determining if they need to stay
> on the LAN, or be sent upstream, and will still perform any port-level
> forwarding you've set up (i.e. send all requests on port 80 to
> 192.168.1.9, the WWW server on the LAN).
>
> > right now I have a win2k server DC and another comp. as a member
> > server, if I turn off the DHCP in the router, and setup the DC as a
> > DHCP server, the member server will automatically know to get it's IP
> > from the DC computer.
>
> Correct. DHCP requests are BROADCAST requests. They go to every
> machine on the network, which is why you only want one DHCP server per
> network. If you left the router serving DHCP while setting up Win2K to
> do so as well, BOTH the router and the server would respond when your
> member server broadcast a DHCP request at boot time. The 5-step
> handshaking that goes on between a DHCP client and a DHCP server would
> mean that whichever server was quicker to offer up an IP address would
> be the one accepted.... and the DHCP pools cannot overlap, or you'd have
> the chance of assigning the same IP address to two different machines
> (once from each DHCP server). Thus, only one DHCP server per network.
>
> When the router is no longer a DHCP server, only the W2K server will
> answer DHCP queries, but the router will continue to perform all of its
> other former functions..... just not DHCP.
>
>
| |
| scott abra 2002-10-24, 3:25 pm |
| Jeff Woods <jeff@deltacomm.com> wrote in message news:<MPG.1821cb235333184d989736@east.usenetserver.com>...
> In article < ti2frugoimfnvgnsoek5g8o3cch8fe
paf5@4ax.com>,
> NOSPAMexoticsportscars@
hotmail.com says...
>
> > >Answered above. Turn OFF DHCP in the router. Assign a static IP
> > >address to the Server box (and yes, it can be in the same 192.168.1.X
> > >pool.... just don't include that address in the assignable pool of the
> > >Server's DHCP server).
> > >
> > >Once done, your W2K server will replace the SMC as the DHCP server on
> > >your LAN.
> >
> > that sounds good.. so if I turn off the DHCP in the router, then the
> > router will simply act as a simple switch/hub right?
>
> Plus a firewall and ROUTER. It will simply not be a DHCP server. It
> will still take packets and route them, determining if they need to stay
> on the LAN, or be sent upstream, and will still perform any port-level
> forwarding you've set up (i.e. send all requests on port 80 to
> 192.168.1.9, the WWW server on the LAN).
>
> > right now I have a win2k server DC and another comp. as a member
> > server, if I turn off the DHCP in the router, and setup the DC as a
> > DHCP server, the member server will automatically know to get it's IP
> > from the DC computer.
>
> Correct. DHCP requests are BROADCAST requests. They go to every
> machine on the network, which is why you only want one DHCP server per
> network. If you left the router serving DHCP while setting up Win2K to
> do so as well, BOTH the router and the server would respond when your
> member server broadcast a DHCP request at boot time. The 5-step
> handshaking that goes on between a DHCP client and a DHCP server would
> mean that whichever server was quicker to offer up an IP address would
> be the one accepted.... and the DHCP pools cannot overlap, or you'd have
> the chance of assigning the same IP address to two different machines
> (once from each DHCP server). Thus, only one DHCP server per network.
>
> When the router is no longer a DHCP server, only the W2K server will
> answer DHCP queries, but the router will continue to perform all of its
> other former functions..... just not DHCP.
I'm not sure about SMC but i don't think a cisco router will forward
BROADCAST requests with out some help. Something like, IP helper-address
that points to the DHCP Server. Or something like that.
HTH,
Scott
| |
|
| On Thu, 24 Oct 2002 19:36:06 GMT, "Georges Thibault"
<Georges.Thibault@cgocable.ca> wrote:
>Make sure that you block packets going to the internet on port udp 67, 68,
>your ISP will like that precaution.
what would blocking those ports do?
>"Jeff Woods" <jeff@deltacomm.com> wrote in message
>news:MPG.1821cb235333184d989736@east.usenetserver.com...
>> In article < ti2frugoimfnvgnsoek5g8o3cch8fe
paf5@4ax.com>,
>> NOSPAMexoticsportscars@
hotmail.com says...
>>
>> > >Answered above. Turn OFF DHCP in the router. Assign a static IP
>> > >address to the Server box (and yes, it can be in the same 192.168.1.X
>> > >pool.... just don't include that address in the assignable pool of the
>> > >Server's DHCP server).
>> > >
>> > >Once done, your W2K server will replace the SMC as the DHCP server on
>> > >your LAN.
>> >
>> > that sounds good.. so if I turn off the DHCP in the router, then the
>> > router will simply act as a simple switch/hub right?
>>
>> Plus a firewall and ROUTER. It will simply not be a DHCP server. It
>> will still take packets and route them, determining if they need to stay
>> on the LAN, or be sent upstream, and will still perform any port-level
>> forwarding you've set up (i.e. send all requests on port 80 to
>> 192.168.1.9, the WWW server on the LAN).
>>
>> > right now I have a win2k server DC and another comp. as a member
>> > server, if I turn off the DHCP in the router, and setup the DC as a
>> > DHCP server, the member server will automatically know to get it's IP
>> > from the DC computer.
>>
>> Correct. DHCP requests are BROADCAST requests. They go to every
>> machine on the network, which is why you only want one DHCP server per
>> network. If you left the router serving DHCP while setting up Win2K to
>> do so as well, BOTH the router and the server would respond when your
>> member server broadcast a DHCP request at boot time. The 5-step
>> handshaking that goes on between a DHCP client and a DHCP server would
>> mean that whichever server was quicker to offer up an IP address would
>> be the one accepted.... and the DHCP pools cannot overlap, or you'd have
>> the chance of assigning the same IP address to two different machines
>> (once from each DHCP server). Thus, only one DHCP server per network.
>>
>> When the router is no longer a DHCP server, only the W2K server will
>> answer DHCP queries, but the router will continue to perform all of its
>> other former functions..... just not DHCP.
>>
>>
>
| |
|
| On Thu, 24 Oct 2002 10:18:00 -0400, Jeff Woods <jeff@deltacomm.com>
wrote:
ok, I almost got it setup, pretty cool... *but* the client machines
grab a IP fine, but internet pages do not load, on my machine, pages
load fine, what could be wrong? or what should I check?
client IP is: 192.168.2.17
SM: 255.255.255.0
GW: 192.168.2.1
my machine:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : D-Link DFE-53
Physical Address. . . . . . . . . : XXXXXXXXXX
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.13
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 24.69.255.XX
24.69.255.XX
>In article < ti2frugoimfnvgnsoek5g8o3cch8fe
paf5@4ax.com>,
> NOSPAMexoticsportscars@hotmail
.com says...
>
>> >Answered above. Turn OFF DHCP in the router. Assign a static IP
>> >address to the Server box (and yes, it can be in the same 192.168.1.X
>> >pool.... just don't include that address in the assignable pool of the
>> >Server's DHCP server).
>> >
>> >Once done, your W2K server will replace the SMC as the DHCP server on
>> >your LAN.
>>
>> that sounds good.. so if I turn off the DHCP in the router, then the
>> router will simply act as a simple switch/hub right?
>
>Plus a firewall and ROUTER. It will simply not be a DHCP server. It
>will still take packets and route them, determining if they need to stay
>on the LAN, or be sent upstream, and will still perform any port-level
>forwarding you've set up (i.e. send all requests on port 80 to
>192.168.1.9, the WWW server on the LAN).
>
>> right now I have a win2k server DC and another comp. as a member
>> server, if I turn off the DHCP in the router, and setup the DC as a
>> DHCP server, the member server will automatically know to get it's IP
>> from the DC computer.
>
>Correct. DHCP requests are BROADCAST requests. They go to every
>machine on the network, which is why you only want one DHCP server per
>network. If you left the router serving DHCP while setting up Win2K to
>do so as well, BOTH the router and the server would respond when your
>member server broadcast a DHCP request at boot time. The 5-step
>handshaking that goes on between a DHCP client and a DHCP server would
>mean that whichever server was quicker to offer up an IP address would
>be the one accepted.... and the DHCP pools cannot overlap, or you'd have
>the chance of assigning the same IP address to two different machines
>(once from each DHCP server). Thus, only one DHCP server per network.
>
>When the router is no longer a DHCP server, only the W2K server will
>answer DHCP queries, but the router will continue to perform all of its
>other former functions..... just not DHCP.
>
| |
|
| On Fri, 25 Oct 2002 04:52:13 GMT, Rob
< NOSPAMexoticsportscars@hotmail
.com> wrote:
>On Thu, 24 Oct 2002 10:18:00 -0400, Jeff Woods <jeff@deltacomm.com>
>wrote:
>
>ok, I almost got it setup, pretty cool... *but* the client machines
>grab a IP fine, but internet pages do not load, on my machine, pages
>load fine, what could be wrong? or what should I check?
>
Connection-specific DNS Suffix . : vc.shawcable.n
Description . . . . . . . . . . . : D-Link DL10050
Physical Address. . . . . . . . . : 00-05-5D-08-12
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.17
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.13
>my machine:
>
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : D-Link DFE-53
> Physical Address. . . . . . . . . : XXXXXXXXXX
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.2.13
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.1
> DNS Servers . . . . . . . . . . . : 24.69.255.XX
> 24.69.255.XX
>
>
>>In article < ti2frugoimfnvgnsoek5g8o3cch8fe
paf5@4ax.com>,
>> NOSPAMexoticsportscars@hotmail
.com says...
>>
>>> >Answered above. Turn OFF DHCP in the router. Assign a static IP
>>> >address to the Server box (and yes, it can be in the same 192.168.1.X
>>> >pool.... just don't include that address in the assignable pool of the
>>> >Server's DHCP server).
>>> >
>>> >Once done, your W2K server will replace the SMC as the DHCP server on
>>> >your LAN.
>>>
>>> that sounds good.. so if I turn off the DHCP in the router, then the
>>> router will simply act as a simple switch/hub right?
>>
>>Plus a firewall and ROUTER. It will simply not be a DHCP server. It
>>will still take packets and route them, determining if they need to stay
>>on the LAN, or be sent upstream, and will still perform any port-level
>>forwarding you've set up (i.e. send all requests on port 80 to
>>192.168.1.9, the WWW server on the LAN).
>>
>>> right now I have a win2k server DC and another comp. as a member
>>> server, if I turn off the DHCP in the router, and setup the DC as a
>>> DHCP server, the member server will automatically know to get it's IP
>>> from the DC computer.
>>
>>Correct. DHCP requests are BROADCAST requests. They go to every
>>machine on the network, which is why you only want one DHCP server per
>>network. If you left the router serving DHCP while setting up Win2K to
>>do so as well, BOTH the router and the server would respond when your
>>member server broadcast a DHCP request at boot time. The 5-step
>>handshaking that goes on between a DHCP client and a DHCP server would
>>mean that whichever server was quicker to offer up an IP address would
>>be the one accepted.... and the DHCP pools cannot overlap, or you'd have
>>the chance of assigning the same IP address to two different machines
>>(once from each DHCP server). Thus, only one DHCP server per network.
>>
>>When the router is no longer a DHCP server, only the W2K server will
>>answer DHCP queries, but the router will continue to perform all of its
>>other former functions..... just not DHCP.
>>
| |
|
| On Fri, 25 Oct 2002 04:56:02 GMT, Rob
< NOSPAMexoticsportscars@hotmail
.com> wrote:
>On Fri, 25 Oct 2002 04:52:13 GMT, Rob
>< NOSPAMexoticsportscars@hotmail
.com> wrote:
>
>>On Thu, 24 Oct 2002 10:18:00 -0400, Jeff Woods <jeff@deltacomm.com>
>>wrote:
>>
>>ok, I almost got it setup, pretty cool... *but* the client machines
>>grab a IP fine, but internet pages do not load, on my machine, pages
>>load fine, what could be wrong? or what should I check?
>
got it working now, thanks!
|
|
|
|
|