Re: DHCP box and Windows 2003 Server Domain Controller documentation
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 10 Mar 2008 16:37:13 -0400
Tarh ik <Tarhik@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Everybody!
Hi - replies are inline.
I'd really appreciate if someone could tell me about some
documentation I could read in the Microsoft Web Site that will help
me understand how the following four items can talk in the same
language:
* A Router/DHCP Box (call it a D-Link, a Cisco, a 3Com, a Linksys,
etc)
Take DHCP off the router and put it on the server (disable it on the router
first or you won't be able to set it up)
* Windows 2003 Server as a Domain Controller (with Active Directory)
* Windows Vista
* Windows XP
The reason I'm asking is because we are doing some weird stuff to
keep our network working, and although it works, these solutions
might generate some issues in the future.
Here is what we did:
* We installed the DNS services in our Domain Controller (Windows 2003
Server)
AD-integrated, one hopes....
so the XP computers could see each other. I feel that this
was a mistake as our Internet Service Provider is providing DNS
services as well.
Ah. No, you definitely needed to do that. This is a big deal. You *have* to
have internal DNS set up properly if you want AD to work. None of your
workstations or servers should have anything other than the *internal*
AD-integrated DNS server IP in their ip config. Your DNS server (your DC)
should use forwarders to your ISP's DNS servers to handle external queries.
This is the first thing you need to fix - make sure you're running
AD-integrated DNS on your DC. Make sure your DC points *only* at its own LAN
IP for DNS and has the correct DNS suffix. Then, make sure your workstations
are set up the same way.
So far, they haven't been in conflict. Not yet,
anyway.
* We assigned a static IP address to our Domain Controller.
I'd sure hope so!
* On the XP Computers, we explicitly set the primary DSN as our Domain
Controller and the secondary DSN as our DHCP/Router box,
No - take this out. Only one DNS server IP (unless you have multiple
internal DNS servers for your AD domain). Not the LAN IP of your router, and
not your ISP's DNS servers.
And you should really use DHCP for this - DHCP running on your DC, not on
your router.
so the
computers could boot in a timely manner (without this, they don't do
a thing for at least 30 seconds right after login). This made me
question the effectiveness of the Dynamic Host Configuration Protocol.
Nothing to do with DHCP - you've got DNS problems.
* On the Vista computer, we had to add the domain name as the suffix
in the DSN configuration, so we could join it to the Domain.
Your DHCP server should be dishing out the primary DNS suffix mydomain.local
(or whatever you use). To *all* workstations.
Someone told me that we needed to install the DHCP services in the
Domain Server. That would mean to have two DHCP entities in the same
network, which usually causes network disconnections - I know that by
experience.
No - see above.
These issues started when we migrated to Windows 2003 Server.
From what? You can't have had a functional AD before. :-)
Any help is greatly appreciated!!!
Best Regards,
Tarh Ik
Hope the above helps.
.
- Follow-Ups:
- References:
- Prev by Date: DHCP box and Windows 2003 Server Domain Controller documentation
- Next by Date: Re: Server won't power up after outage
- Previous by thread: DHCP box and Windows 2003 Server Domain Controller documentation
- Next by thread: Re: DHCP box and Windows 2003 Server Domain Controller documentati
- Index(es):
Relevant Pages
|
