Promoting server to a DC without disabling router's DHCP role

[Guest]

Hello,
I am having problems setting up a domain due to a DHCP/DNS issue and hope I
explain the issue well enough here for someone to help.

Basically, we have a development server (running Win2K Server, SP4) sitting
behind a router with a small network of Win XP and Mac machines. The router
is enabled as the DHCP server. Not all machines on our network (i.e., the
Macs) will make use of Win 2K server at this time, so I want to leave the
assignment of IP addresses on our LAN up to our router, not up to a
development server.

I ran the Active Directory wizard and successfully promoted the server to a
DC. Then, following earlier success I had with a Win 2003 setup, I set the
client PC's (running XP Pro) 'Preferred DNS server' to the local IP address
of the server. When I then try to join it to the new domain, I immediately
get the "DNS name does not exist" error. The ping tests work on the client
machine and I also tried rebooting all machines but get the same result.

I'm thinking the problem lies in that both the server and router are vying
for the DHCP role and I am not disabling the server role properly.

In short:

What is the easiest way to promote a Win2K server to be a DC and a DNS
server without being the DHCP server as well?

or

What is the proper way to demote the DHCP role in Windows 2K server: Start >
Run > ??? I am afraid I am used to the GUI equivalent in Windows Server
2003...

Thanks in advance for your help!

 

[Kurt]

Hello,
I am having problems setting up a domain due to a DHCP/DNS issue and hope
I
explain the issue well enough here for someone to help.

Basically, we have a development server (running Win2K Server, SP4)
sitting
behind a router with a small network of Win XP and Mac machines. The
router
is enabled as the DHCP server. Not all machines on our network (i.e., the
Macs) will make use of Win 2K server at this time, so I want to leave the
assignment of IP addresses on our LAN up to our router, not up to a
development server.

I ran the Active Directory wizard and successfully promoted the server to
a
DC. Then, following earlier success I had with a Win 2003 setup, I set
the
client PC's (running XP Pro) 'Preferred DNS server' to the local IP
address
of the server. When I then try to join it to the new domain, I
immediately
get the "DNS name does not exist" error. The ping tests work on the
client
machine and I also tried rebooting all machines but get the same result.

I'm thinking the problem lies in that both the server and router are vying
for the DHCP role and I am not disabling the server role properly.

In short:

What is the easiest way to promote a Win2K server to be a DC and a DNS
server without being the DHCP server as well?

They are entirely separate functions. A DC is usually also DNS server. I
recommend this. DHCP doesn't install automatically. You have to install it,
configure a scope, authorize the server and activate the scope before it
will work.

In order for your clients to join a domain, they must use ONLY the DNS
server for that domain (which is usually the DC). Make sure the DNS server
service is running on the server and that you have the proper zone defined.
Make sure you can look up your domain name using nslookup from your client
(nslookup mydomain.local). It should resolve to the IP address of your
domain controller. When all that works you'll be able to join the domain.

....kurt

 

[Herb Martin]

Hello,
I am having problems setting up a domain due to a DHCP/DNS issue and hope
I
explain the issue well enough here for someone to help.

Basically, we have a development server (running Win2K Server, SP4)
sitting
behind a router with a small network of Win XP and Mac machines. The
router
is enabled as the DHCP server. Not all machines on our network (i.e., the
Macs) will make use of Win 2K server at this time, so I want to leave the
assignment of IP addresses on our LAN up to our router, not up to a
development server.

This is not even an issue for the promotion of DCs in general.

I ran the Active Directory wizard and successfully promoted the server to
a
DC. Then, following earlier success I had with a Win 2003 setup, I set
the
client PC's (running XP Pro) 'Preferred DNS server' to the local IP
address
of the server.

This is both correct AND necessary. All domain machines
(and usually all internal machines) must be set STRICTLY
to the "internal (e.g., Domain) DNS servers" which can resolve
ALL names for the clients, including domain specific items.

When I then try to join it to the new domain, I immediately
get the "DNS name does not exist" error. The ping tests work on the
client
machine and I also tried rebooting all machines but get the same result.

The "client" machines (actually ALL domain machines) need their
FULL DNS domain name set in the SYSTEM CONTROL Panel.

The zone that supports AD must be dynamic.

I'm thinking the problem lies in that both the server and router are vying
for the DHCP role and I am not disabling the server role properly.

No. DHCP doesn't matter here in general.

There is however one mistake that DHCP can be helping create
if your "Domain clients" are also DHCP clients:

The DNS server (we discussed above) must be set to use the
one (or set) which can resolve the domain zone.

IF the DHCP server gives out a DIFFERENT address for DNS
then those clients must also OVERRIDE the DNS setting on the
NIC->IP settings for "DNS Server".

Such clients may remain DHCP clients but they must override
that DNS server setting (manually.)

You can also adjust the DNS setting being given from the DHCP
server to the clients to just give out the "correct" DNS address to
ALL clients -- as long as your non-Domain machines can tolerate
that (which they usually can.)

In short:

What is the easiest way to promote a Win2K server to be a DC and a DNS
server without being the DHCP server as well?

No special action is required since DHCP is neither part of
DCPromo nor required for a domain to function. No DC ever
becomes a DHCP server automatically -- that is YOUR choice
which you must actively perform to have it become a DHCP
server.

DHCP has no concept of Domain from the AD perspective.*

(DHCP server might give out the DNS domain name, or even
register the clients IN DNS but there is no real knowledge of
"domains" nor "authentication" in DHCP -- also DHCP running
on a Windows Server may need to be AUTHORIZED in AD
but that is an entirely different issue and has no effect on older
or non-MS DHCP servers.)

or

What is the proper way to demote the DHCP role in Windows 2K server: Start
Run > ??? I am afraid I am used to the GUI equivalent in Windows Server
2003...

Removing the service will work in ADD/REMOVE Programs->
Windows Components.

You could however just turn off the service (Services control
panel) and set it to either "Manual" or "Disabled" (for next
reboot so it won't come back on.)

You also just remove or disable every Scope in the DHCP
server. No scope means it will not actually function as a
DHCP server. Nearly the same as being turned off.

Thanks in advance for your help!

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Guest]

Kurt and Herb,

Thank you for your help. Problem solved. As you guys indicated, my DNS
Server was not configured properly.

For neophytes like myself, I also found the following website helpful in
solving my issues:

http://www.petri.co.il/create_a_new_dns_server_for_ad.htm

Thanks again.

--
Carl

Hello,
I am having problems setting up a domain due to a DHCP/DNS issue and hope
I
explain the issue well enough here for someone to help.

Basically, we have a development server (running Win2K Server, SP4)
sitting
behind a router with a small network of Win XP and Mac machines. The
router
is enabled as the DHCP server. Not all machines on our network (i.e., the
Macs) will make use of Win 2K server at this time, so I want to leave the
assignment of IP addresses on our LAN up to our router, not up to a
development server.

This is not even an issue for the promotion of DCs in general.

I ran the Active Directory wizard and successfully promoted the server to
a
DC. Then, following earlier success I had with a Win 2003 setup, I set
the
client PC's (running XP Pro) 'Preferred DNS server' to the local IP
address
of the server.

This is both correct AND necessary. All domain machines
(and usually all internal machines) must be set STRICTLY
to the "internal (e.g., Domain) DNS servers" which can resolve
ALL names for the clients, including domain specific items.

When I then try to join it to the new domain, I immediately
get the "DNS name does not exist" error. The ping tests work on the
client
machine and I also tried rebooting all machines but get the same result.

The "client" machines (actually ALL domain machines) need their
FULL DNS domain name set in the SYSTEM CONTROL Panel.

The zone that supports AD must be dynamic.

I'm thinking the problem lies in that both the server and router are vying
for the DHCP role and I am not disabling the server role properly.

No. DHCP doesn't matter here in general.

There is however one mistake that DHCP can be helping create
if your "Domain clients" are also DHCP clients:

The DNS server (we discussed above) must be set to use the
one (or set) which can resolve the domain zone.

IF the DHCP server gives out a DIFFERENT address for DNS
then those clients must also OVERRIDE the DNS setting on the
NIC->IP settings for "DNS Server".

Such clients may remain DHCP clients but they must override
that DNS server setting (manually.)

You can also adjust the DNS setting being given from the DHCP
server to the clients to just give out the "correct" DNS address to
ALL clients -- as long as your non-Domain machines can tolerate
that (which they usually can.)

In short:

What is the easiest way to promote a Win2K server to be a DC and a DNS
server without being the DHCP server as well?

No special action is required since DHCP is neither part of
DCPromo nor required for a domain to function. No DC ever
becomes a DHCP server automatically -- that is YOUR choice
which you must actively perform to have it become a DHCP
server.

DHCP has no concept of Domain from the AD perspective.*

(DHCP server might give out the DNS domain name, or even
register the clients IN DNS but there is no real knowledge of
"domains" nor "authentication" in DHCP -- also DHCP running
on a Windows Server may need to be AUTHORIZED in AD
but that is an entirely different issue and has no effect on older
or non-MS DHCP servers.)

or

What is the proper way to demote the DHCP role in Windows 2K server: Start
Run > ??? I am afraid I am used to the GUI equivalent in Windows Server
2003...

Removing the service will work in ADD/REMOVE Programs->
Windows Components.

You could however just turn off the service (Services control
panel) and set it to either "Manual" or "Disabled" (for next
reboot so it won't come back on.)

You also just remove or disable every Scope in the DHCP
server. No scope means it will not actually function as a
DHCP server. Nearly the same as being turned off.

Thanks in advance for your help!

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Herb Martin]

Kurt and Herb,

Thank you for your help. Problem solved. As you guys indicated, my DNS
Server was not configured properly.

For neophytes like myself, I also found the following website helpful in
solving my issues:

The built-in help has full information on most every element
of this, including "checklists" for DNS Servers (and practically
everything else in the OS.)

Hint: Search help for both 'checklist' and KEYWORD

For example: [ DNS checklist ]

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

http://www.petri.co.il/create_a_new_dns_server_for_ad.htm

Thanks again.

--
Carl

Hello,
I am having problems setting up a domain due to a DHCP/DNS issue and
hope
I
explain the issue well enough here for someone to help.

Basically, we have a development server (running Win2K Server, SP4)
sitting
behind a router with a small network of Win XP and Mac machines. The
router
is enabled as the DHCP server. Not all machines on our network (i.e.,
the
Macs) will make use of Win 2K server at this time, so I want to leave
the
assignment of IP addresses on our LAN up to our router, not up to a
development server.

This is not even an issue for the promotion of DCs in general.

I ran the Active Directory wizard and successfully promoted the server
to
a
DC. Then, following earlier success I had with a Win 2003 setup, I set
the
client PC's (running XP Pro) 'Preferred DNS server' to the local IP
address
of the server.

This is both correct AND necessary. All domain machines
(and usually all internal machines) must be set STRICTLY
to the "internal (e.g., Domain) DNS servers" which can resolve
ALL names for the clients, including domain specific items.

When I then try to join it to the new domain, I immediately
get the "DNS name does not exist" error. The ping tests work on the
client
machine and I also tried rebooting all machines but get the same
result.

The "client" machines (actually ALL domain machines) need their
FULL DNS domain name set in the SYSTEM CONTROL Panel.

The zone that supports AD must be dynamic.

I'm thinking the problem lies in that both the server and router are
vying
for the DHCP role and I am not disabling the server role properly.

No. DHCP doesn't matter here in general.

There is however one mistake that DHCP can be helping create
if your "Domain clients" are also DHCP clients:

The DNS server (we discussed above) must be set to use the
one (or set) which can resolve the domain zone.

IF the DHCP server gives out a DIFFERENT address for DNS
then those clients must also OVERRIDE the DNS setting on the
NIC->IP settings for "DNS Server".

Such clients may remain DHCP clients but they must override
that DNS server setting (manually.)

You can also adjust the DNS setting being given from the DHCP
server to the clients to just give out the "correct" DNS address to
ALL clients -- as long as your non-Domain machines can tolerate
that (which they usually can.)

In short:

What is the easiest way to promote a Win2K server to be a DC and a DNS
server without being the DHCP server as well?

No special action is required since DHCP is neither part of
DCPromo nor required for a domain to function. No DC ever
becomes a DHCP server automatically -- that is YOUR choice
which you must actively perform to have it become a DHCP
server.

DHCP has no concept of Domain from the AD perspective.*

(DHCP server might give out the DNS domain name, or even
register the clients IN DNS but there is no real knowledge of
"domains" nor "authentication" in DHCP -- also DHCP running
on a Windows Server may need to be AUTHORIZED in AD
but that is an entirely different issue and has no effect on older
or non-MS DHCP servers.)

or

What is the proper way to demote the DHCP role in Windows 2K server:
Start

Run > ??? I am afraid I am used to the GUI equivalent in Windows Server
2003...

Removing the service will work in ADD/REMOVE Programs->
Windows Components.

You could however just turn off the service (Services control
panel) and set it to either "Manual" or "Disabled" (for next
reboot so it won't come back on.)

You also just remove or disable every Scope in the DHCP
server. No scope means it will not actually function as a
DHCP server. Nearly the same as being turned off.

Thanks in advance for your help!

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]