Best SOHO network topology with w2k server

[Guest]

Presently we have a w2k server running as DC. DHCP is provided by a
one-piece router/switch/wireless-access-point. there are 5 clients: 4 win2k,
one winxp As such, my clients are set up to have primary DNS as IP of the
router, which is DHCP server and alternate DNS as IP of the DC. This works
ok on w2k clents, but poorly on WinXP as it can't reliably either get onto
domain or the internet. I want to set my DC to also be my DHCP server.
So presently topology is as follows:
DSL modem--->router/switch/WAP into which all the clients and the server are
daisy-chained and couple of laptops access wirelessly.
I guess, it's possible to fix my problem by running DHCP by my DC and have
it disabled on the router. Is it possible with present topology?

 

[Dana Brash]

Yes. In a domain environment you should have the clients all use the DC for
DNS resolution, and using DHCP on the server will help you make sure that
all your clients are registered properly in DNS so that they can communicate
properly with each other, network printers, the internet, etc. Using the DC
for client DNS resolution will also result in faster resolution for the
clients because you will be taking advantage of cached lookups locally. Use
the Router/Switch/etc... device as the default gateway.

Here are some good instructions:
How To Install and Configure a DHCP Server in an Active Directory Domain in
Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300429

Make sure you understand some key points about DHCP in W2k/2003:

* You must authorize the server in Active Directory.
* Understand the relationship between DHCP and DNS: setting DHCP to update
DNS is very helpful.
* Use DHCP to set the IP's on the wirelesss clients. You may need to enable
to scope to support BOOTP as well as DHCP to get the addresses past the
AP/Router device
* Use DHCP to configure all clients to use the DC as DNS. Have the DC's DNS
server use the root hints to resolve addresses, or forward requests to your
ISP's DNS Server. (NOT to the router)
* Make sure to turn DHCP off on the router

I'm a big fan of DHCP. I can almost never imagine a scenario where you
wouldnt' want to use Windows DHCP for your clients, it's just too well
integrated. In such a small environment, you could easily get away with
assigning all the clients static IP's. But if you know what you're doing,
you can probably configure DHCP faster anyway. ;-)

HTH
=d=

 

[Richard G. Harper]

Not only is it possible, but it's the best solution to your current
problems. Here is how I would handle the situation:

1. Disable DHCP on the router
2. Make sure the AD server is on a fixed IP address (preferably lock it
down on the same IP address it's on now, otherwise you're in for some fun)
3. Set up and authorize DHCP on your AD server
4. Set the default gateway in the DHCP options as the router's IP address,
also set DNS to the AD server's IP address
5. Release and renew IP addresses for all clients
6. Check DNS to be sure that all clients are registered there
7. Configure AD DNS to auto-forward requests to your ISP's DNS server

That should resolve all your problems.

--
Richard G. Harper [MVP Shell/User] (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.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Guest]

Thanks Dana and Richard. I am going to try setting up DHCP on DC. The
question that I have remaining is:

Can I use the present networking equipment to do this? Presently I have DSL
modem that's connected to one-piece router/switch/WAP. Do I need to install
a second NIC on the server?

Not only is it possible, but it's the best solution to your current
problems. Here is how I would handle the situation:

1. Disable DHCP on the router
2. Make sure the AD server is on a fixed IP address (preferably lock it
down on the same IP address it's on now, otherwise you're in for some fun)
3. Set up and authorize DHCP on your AD server
4. Set the default gateway in the DHCP options as the router's IP address,
also set DNS to the AD server's IP address
5. Release and renew IP addresses for all clients
6. Check DNS to be sure that all clients are registered there
7. Configure AD DNS to auto-forward requests to your ISP's DNS server

That should resolve all your problems.

--
Richard G. Harper [MVP Shell/User] (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.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Presently we have a w2k server running as DC. DHCP is provided by a
one-piece router/switch/wireless-access-point. there are 5 clients: 4
win2k,
one winxp As such, my clients are set up to have primary DNS as IP of the
router, which is DHCP server and alternate DNS as IP of the DC. This
works
ok on w2k clents, but poorly on WinXP as it can't reliably either get onto
domain or the internet. I want to set my DC to also be my DHCP server.
So presently topology is as follows:
DSL modem--->router/switch/WAP into which all the clients and the server
are
daisy-chained and couple of laptops access wirelessly.
I guess, it's possible to fix my problem by running DHCP by my DC and have
it disabled on the router. Is it possible with present topology?

 

[Dana Brash]

Hi Alex,

You don't need another NIC on your server. You want to make sure that the
server and the clients are all on the same subnet, and the server should
continue to use it's current IP address.

Richard's instructions should get you where you need to go, but there's
always room to learn more....

Here is a good planning document for 2003:
http://www.microsoft.com/resources/...ddocs/en-us/sag_DHCP_imp_PlanningNetworks.asp

Here is some good overview of DHCP for 2000 (concepts are identical):
http://www.microsoft.com/resources/...00/server/reskit/en-us/cnet/cncb_dhc_KLOM.asp

--
HTH,
=d=


Dana Brash
MCSE, MCDBA, MCSA

(e-mail address removed)

Thanks Dana and Richard. I am going to try setting up DHCP on DC. The
question that I have remaining is:

Can I use the present networking equipment to do this? Presently I have
DSL
modem that's connected to one-piece router/switch/WAP. Do I need to
install
a second NIC on the server?

Not only is it possible, but it's the best solution to your current
problems. Here is how I would handle the situation:

1. Disable DHCP on the router
2. Make sure the AD server is on a fixed IP address (preferably lock it
down on the same IP address it's on now, otherwise you're in for some
fun)
3. Set up and authorize DHCP on your AD server
4. Set the default gateway in the DHCP options as the router's IP
address,
also set DNS to the AD server's IP address
5. Release and renew IP addresses for all clients
6. Check DNS to be sure that all clients are registered there
7. Configure AD DNS to auto-forward requests to your ISP's DNS server

That should resolve all your problems.

--
Richard G. Harper [MVP Shell/User] (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.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Presently we have a w2k server running as DC. DHCP is provided by a
one-piece router/switch/wireless-access-point. there are 5 clients: 4
win2k,
one winxp As such, my clients are set up to have primary DNS as IP of
the
router, which is DHCP server and alternate DNS as IP of the DC. This
works
ok on w2k clents, but poorly on WinXP as it can't reliably either get
onto
domain or the internet. I want to set my DC to also be my DHCP server.
So presently topology is as follows:
DSL modem--->router/switch/WAP into which all the clients and the
server
are
daisy-chained and couple of laptops access wirelessly.
I guess, it's possible to fix my problem by running DHCP by my DC and
have
it disabled on the router. Is it possible with present topology?

 

[Richard G. Harper]

I agree with Dana - only one NIC is necessary, your current setup will
handle your needs just fine. And by all means, do some reading before you
start so you're familiar with the basic process - my quick guide does cover
all the relevant steps but you can never know enough.

--
Richard G. Harper [MVP Shell/User] (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.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Thanks Dana and Richard. I am going to try setting up DHCP on DC. The
question that I have remaining is:

Can I use the present networking equipment to do this? Presently I have
DSL
modem that's connected to one-piece router/switch/WAP. Do I need to
install
a second NIC on the server?

Not only is it possible, but it's the best solution to your current
problems. Here is how I would handle the situation:

1. Disable DHCP on the router
2. Make sure the AD server is on a fixed IP address (preferably lock it
down on the same IP address it's on now, otherwise you're in for some
fun)
3. Set up and authorize DHCP on your AD server
4. Set the default gateway in the DHCP options as the router's IP
address,
also set DNS to the AD server's IP address
5. Release and renew IP addresses for all clients
6. Check DNS to be sure that all clients are registered there
7. Configure AD DNS to auto-forward requests to your ISP's DNS server

That should resolve all your problems.

--
Richard G. Harper [MVP Shell/User] (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.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Presently we have a w2k server running as DC. DHCP is provided by a
one-piece router/switch/wireless-access-point. there are 5 clients: 4
win2k,
one winxp As such, my clients are set up to have primary DNS as IP of
the
router, which is DHCP server and alternate DNS as IP of the DC. This
works
ok on w2k clents, but poorly on WinXP as it can't reliably either get
onto
domain or the internet. I want to set my DC to also be my DHCP server.
So presently topology is as follows:
DSL modem--->router/switch/WAP into which all the clients and the
server
are
daisy-chained and couple of laptops access wirelessly.
I guess, it's possible to fix my problem by running DHCP by my DC and
have
it disabled on the router. Is it possible with present topology?