Win2k Server DHCP or SMC Router DHCP

[Al Taylor]

Hi everybody, I need some opinions please. I have a small win2k network at
home that consist of the following 1 win2k server, 1 win2k pro client and 1
win-xp pro client. these computers are connected to an SMC 7004AWBR Router.
The Router is connected to my DSL line and is currently handing out IP
addresses to all of the computers except the win2k server because it is
doing DNS name resolution so I gave it an IP address.

My question is this. Should I enable the DHCP service at the win2k server or
stick with the router doing DHCP? I think I know which would give me the
most flexibility as far as DHCP goes but I would like some opinions please.

Thanks in advance.

Al Taylor

 

[Kevin D. Goodknecht [MVP]]

In

Hi everybody, I need some opinions please. I have a small win2k
network at home that consist of the following 1 win2k server, 1 win2k
pro client and 1 win-xp pro client. these computers are connected to
an SMC 7004AWBR Router. The Router is connected to my DSL line and is
currently handing out IP addresses to all of the computers except the
win2k server because it is doing DNS name resolution so I gave it an
IP address.

My question is this. Should I enable the DHCP service at the win2k
server or stick with the router doing DHCP? I think I know which
would give me the most flexibility as far as DHCP goes but I would
like some opinions please.

Thanks in advance.

Al Taylor

Is your Win2k server a DC?
If it is, then using Win2k DHCP, while not required, will make life much
easier. For one your router is probably giving out your ISP's DNS, or its
address for DNS which it would forward to your ISP, which would be a major
mistake in an AD domain.

I suggest using Win2k DHCP with a minimum of these options since you have no
legacy OS machines.
003 Routers address (Default Gateway)
006 DNS servers (Your Local DNS servers address)
015 DNS Domain name (Your AD Domain name)

 

[Ace Fekay [MVP]]

In

In

Is your Win2k server a DC?
If it is, then using Win2k DHCP, while not required, will make life
much easier. For one your router is probably giving out your ISP's
DNS, or its address for DNS which it would forward to your ISP, which
would be a major mistake in an AD domain.

I suggest using Win2k DHCP with a minimum of these options since you
have no legacy OS machines.
003 Routers address (Default Gateway)
006 DNS servers (Your Local DNS servers address)
015 DNS Domain name (Your AD Domain name)

Kevin, I agree and just want to add that the MS DHCP service and the MS DNS
service APIs are designed to work hand in hand, which facilitates ease of
registering clients into DNS. Using a router's DHCP is just for a small non
AD network and does not support many options that MS DHCP does.

I hope Al does not use his ISP's DNS addresses in IP properties (DCs or
clients), and just use his internal DNS only on all his machines, or he'll
be posting back questioning why he's getting numerous errors with AD and his
clients, GPOs not working, logon takes forever, etc, etc.

Kevin, thought you would have added this....Configure a forwarder for
efficient Internet resolution: http://support.microsoft.com/?id=300202.



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory