Adding a second domain controller to exsiting Win 2000 AD

[Pete]

Recently I upgraded our WinNT 4 PDC to Windows 2000, which is running
Active Directory in the 'Active Directory-integrated' mode becuase we
still have WinNT 4 BDC. I do however have two other servers that are
running Win2000 and I would like to install Active Directory on either
on of them, but I cannot. What am I doing wrong and how do I fix it?
Below is a more detailed description of what happens a long with the
log file entries.

This is what happens:

In the Network Credentils dialog I can't using the Windows 2000 FQDN
(ebtech.net). When I try it I get a message saying 'The domain
"ebtech.net" is not and Active Directory domain, or an Active
Directory domain controller for the domain could not be contracted'.
However if I use ebtech then it works.

In the Additional Domain Controller dialog I can't using the Windows
2000 FQDN (ebtech.net). If I do I get this error message 'The domain
"ebtech.net" cannot be contracted. Ensure that the DNS domain anme is
type correctly. This condition may be caused by a DNS lookup problem.
If this domain was recnetly created, its name may not yet be
registered with the Domain Naming Serivce. For information about
troubleshooting common DNS lookup problems, plase see the following
Microsoft Web Site: http://go.microsoft.com/fwlink/?LinkID=5171'.
Again I can use EBTECH and I can get to the next dialog.

In the Summary dialog I get this error message 'The operation failed
becuase; Failed finding a suitable domain controller for the domain
ebtech.net. "The specified domain either does not exsists or could not
be contracted."'

Below is what is found in the DCPROMO.LOG file
08/09 16:38:30 [INFO] Promotion request for replica domain controller
08/09 16:38:30 [INFO] DnsDomainName ebtech.net
08/09 16:38:30 [INFO] ReplicaPartner (NULL)
08/09 16:38:30 [INFO] SiteName (NULL)
08/09 16:38:30 [INFO] DsDatabasePath C:\WINNT\NTDS, DsLogPath
C:\WINNT\NTDS
08/09 16:38:30 [INFO] SystemVolumeRootPath C:\WINNT\SYSVOL
08/09 16:38:30 [INFO] Account ebtech\ebtechadmin#17
08/09 16:38:30 [INFO] Options 196
08/09 16:38:30 [INFO] Validate supplied paths
08/09 16:38:30 [INFO] Validating path C:\WINNT\NTDS.
08/09 16:38:30 [INFO] Path is a directory
08/09 16:38:30 [INFO] Path is on a fixed disk drive.
08/09 16:38:30 [INFO] Validating path C:\WINNT\NTDS.
08/09 16:38:30 [INFO] Path is a directory
08/09 16:38:30 [INFO] Path is on a fixed disk drive.
08/09 16:38:30 [INFO] Validating path C:\WINNT\SYSVOL.
08/09 16:38:30 [INFO] Path is on a fixed disk drive.
08/09 16:38:30 [INFO] Path is on an NTFS volume
08/09 16:38:30 [INFO] Start the worker task
08/09 16:38:30 [INFO] Request for promotion returning 0
08/09 16:38:30 [INFO] Searching for a domain controller for the domain
ebtech.net that contains the account MARS$

08/09 16:38:30 [ERROR] Failed to find a DC for domain ebtech.net: 1355
08/09 16:38:30 [ERROR] Failed to get domain controller for account
MARS$ (1355)
08/09 16:38:30 [INFO] Error - Failed finding a suitable domain
controller for the domain ebtech.net
(1355)
08/09 16:38:30 [INFO] The attempted domain controller operation has
completed

08/09 16:38:30 [INFO] DsRolepSetOperationDone returned 0

When I run this command dcdiag.exe /shoenix I get the following
Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\PHOENIX
Starting test: Connectivity
e265e51e-a9d0-4270-9349-98d996e5643b._msdcs.ebtech.net's
server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(e265e51e-a9d0-4270-9349-98d996e5643b._msdcs.ebtech.net)
couldn't be

resolved, the server name (phoenix.ebtech.net) resolved to
the IP

address (206.186.35.16) and was pingable. Check that the IP
address

is registered correctly with the DNS server.
......................... PHOENIX failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\PHOENIX
Skipping all tests, because server PHOENIX is
not responding to directory service requests

Running enterprise tests on : ebtech.net
Starting test: Intersite
......................... ebtech.net passed test Intersite
Starting test: FsmoCheck
......................... ebtech.net passed test FsmoCheck

 

[Herb Martin]

Recently I upgraded our WinNT 4 PDC to Windows 2000, which is running
Active Directory in the 'Active Directory-integrated' mode becuase we
still have WinNT 4 BDC.

ADIntegrated relates to "Dynamic DNS" you likely mean
"mixed mode" (two modes, mixed supporting older BDCs
and Native which only allows Win2000+ DCs.)

I do however have two other servers that are
running Win2000 and I would like to install Active Directory on either
on of them, but I cannot. What am I doing wrong and how do I fix it?
Below is a more detailed description of what happens a long with the
log file entries.

Usually this is a DNS issue...

This is what happens:

In the Network Credentils dialog I can't using the Windows 2000 FQDN
(ebtech.net). When I try it I get a message saying 'The domain
"ebtech.net" is not and Active Directory domain, or an Active
Directory domain controller for the domain could not be contracted'.
However if I use ebtech then it works.

"then it works" What "it" works? DCPromo works?

Is your domain named ebtech.net? Do all the DCs have this in their
system properties as the domain name?

Ace keeps reminding me you need at least TWO tags in your domain
name and the DCs/machines need to use this in their System identity
properties.

In the Additional Domain Controller dialog I can't using the Windows
2000 FQDN (ebtech.net). If I do I get this error message 'The domain
"ebtech.net" cannot be contracted. Ensure that the DNS domain anme is
type correctly. This condition may be caused by a DNS lookup problem.

Otherwise, it is almost always because of one of these:
1) DNS is not dynamice
2) The existing DCs don't have the dynamic DNS (set) listed as their
ONLY DNS, in their own client properties: NIC\IP\DNS server.
3) New DC or other machines don't have the dynamic DNS set as
their ONLY DNS

If you change #1 or #2, restart the NetLogon service on each DC so the DC
will
register properly (or reboot each DC.)

 

[Pete]

ADIntegrated relates to "Dynamic DNS" you likely mean
"mixed mode" (two modes, mixed supporting older BDCs
and Native which only allows Win2000+ DCs.)



Usually this is a DNS issue...


"then it works" What "it" works? DCPromo works?

I can get to the next dialog in the DCPromo wizard

Is your domain named ebtech.net? Do all the DCs have this in their
system properties as the domain name?

Is your domain named ebtech.net? Yes my domain is called ebtech.net.

Do all the DCs have this in their system properties as the domain
name? My Windows 2000 Servers do, my WinNT 4 DBC does not and I can't
change it

Ace keeps reminding me you need at least TWO tags in your domain
name and the DCs/machines need to use this in their System identity
properties.

What does the previous sentence refer to/mean?

Otherwise, it is almost always because of one of these:
1) DNS is not dynamice
2) The existing DCs don't have the dynamic DNS (set) listed as their
ONLY DNS, in their own client properties: NIC\IP\DNS server.
3) New DC or other machines don't have the dynamic DNS set as
their ONLY DNS

If you change #1 or #2, restart the NetLogon service on each DC so the DC
will
register properly (or reboot each DC.)

#1 Has already been taken care of
#2 I need to have Dynamic DNS installed on my WinNT4 PDC?
#3 I cannot install DNS on my Windows 2000 system unless it has Active
Directory setup

I only have four systems in total to work with
1 Windows 2000 with Active Directory already setup becuase it was a
WinNT 4 PDC
1 Windows NT4 BDC
2 Windows 2000 servers without Active Directory setup

 

[Herb Martin]

Is your domain named ebtech.net? Yes my domain is called ebtech.net.

Do all the DCs have this in their system properties as the domain
name? My Windows 2000 Servers do, my WinNT 4 DBC does not and I can't
change it

Right, NT machines use just the SHORT NetBIOS format.
When you do a NEW domain, it always asks for the NetBIOS
name but defaults to the first tag of the DNS name so most
people don't even notice the choice.

When you upgrade (NT->2000) domains, it MUST use the
old NetBIOS name even if you alter the DNS (bad idea)

Chances are that you are resolving through NetBIOS and DNS
is Broken.

Yes, for WIN2000 machines. You said above that all DCs were
properly named though.

What does the previous sentence refer to/mean?

It means:
You can use ebtech.net for the DNS name, but not ebtech for the DNS
name -- the NetBIOS legacy name will still be ebtech though.

2 tags for the domain or more, e.g,. domain name child.domain.com is
fine too.

You are looking in System Control Panel to check the name right?
(You can type anything in the NIC properties but that's not the "real"
name.)

System Control Panel\Network Identification\ Network Domain Name
(notice that on a DC the change button is disabled -- that's why Ace
focuses on this -- it's hard to change if you get it screwed up with ONE
tag for the domain name part.)

#1 Has already been taken care of
#2 I need to have Dynamic DNS installed on my WinNT4 PDC?

No, it doesn't support it with MS DNS, so the NT has to be a
secondary if it runs DNS.

#3 I cannot install DNS on my Windows 2000 system unless it has Active
Directory setup

No, you can install DNS and make it dynamic on ANY Win2000+
SERVER.

I only have four systems in total to work with
1 Windows 2000 with Active Directory already setup becuase it was a
WinNT 4 PDC

Then it almost certainly has Dynamic DNS on it, right?

1 Windows NT4 BDC
2 Windows 2000 servers without Active Directory setup

All/Any of these can be secondaries (but you don't need 4 DNS servers.)

What is the Zone name in DNS? It must have those SAME two tags:
ebtech.net

 

[Pete]

Sorry for the slow response. My was called ebtech when we were running
all WinNT 4 system, with a PDC called phoenix and a BDC called triton.
I upgraded the PDC (phoenix) from WinNT 4 to Win2000 and the system
became know as phoenix.ebtech.net. I now have another windows 2000
system called mars which I would like to install Active Directory on
so I can removed triton from being the BDC for the Win2000 domain
which is called ebtech.net. Prior to the upgrade I had my two linux
servers listed as the DNS servers, afterwards I have the Windows 2000
server listed as the primary DNS server, and then I list my two linux
servers. In order to get Active Directory installed on my second
Windows 2000 Server what do I need to do?

Pete

 

[Herb Martin]

Sorry for the slow response. My was called ebtech when we were running
all WinNT 4 system, with a PDC called phoenix and a BDC called triton.
I upgraded the PDC (phoenix) from WinNT 4 to Win2000 and the system
became know as phoenix.ebtech.net. I now have another windows 2000
system called mars which I would like to install Active Directory on
so I can removed triton from being the BDC for the Win2000 domain
which is called ebtech.net. Prior to the upgrade I had my two linux
servers listed as the DNS servers, afterwards I have the Windows 2000
server listed as the primary DNS server, and then I list my two linux
servers. In order to get Active Directory installed on my second
Windows 2000 Server what do I need to do?

Presumably you have setup the Win2000 primary as DYNAMIC and
the linus servers as secondaries (or removed them from the zone.)

Point the client settings on the New-DC-to-be (NIC\IP\DNS Server)
at the dynamic Primary and then run DCPromo.