Adding a second AD Server to an AD domain?

[Guest]

I am installing Active Directory in my lab before installing it on my network.
I started out with 3 Windows 2000 servers with NO domain controller.
I installed AD on the first server making it the 1st domain controller
installing DNS at the same time.
It is authenticating users and joining the other servers and PC's as member
servers and PC's.
When I try to create a second AD server as a BDC (I know there is no such
thing in AD) it can not find the Domain Controller to join to.
This second server has joined the domain since installing AD and I log into
the domain on it.
What might I be missing that it can not see the PDC (again, I know there is
no such thing as a PDC in AD)
The error was something to do with DNS lookup but I don't have the error
with me.

 

[nitin]

I am installing Active Directory in my lab before installing
it on my network.
I started out with 3 Windows 2000 servers with NO domain
controller.
I installed AD on the first server making it the 1st domain
controller
installing DNS at the same time.
It is authenticating users and joining the other servers and
PC's as member
servers and PC's.
When I try to create a second AD server as a BDC (I know there
is no such
thing in AD) it can not find the Domain Controller to join to.
This second server has joined the domain since installing AD
and I log into
the domain on it.
What might I be missing that it can not see the PDC (again, I
know there is
no such thing as a PDC in AD)
The error was something to do with DNS lookup but I don't
have the error
with me.

If you clould plase tell me the exact error message then it is going
to be easier to answer your query

but if you think that it is something to do with DNS
then make sure that your DNS is working fine
and your machine is pointing to the right DNS server and not any DNS
that is out of your network

check if you can ping the first DC with name

and try to promote the other DC again
get the error message then put it here

 

[Cary Shultz [A.D. MVP]]

Steve,

As nitin correctly stated, it is most probably a DNS problem. However,
since you are not currently able to provide us with the error message that
is simply an educated guess. It could also be a 'delegated for trust'
problem.

Make sure that on the to-be-dcpromo'd-server that the TCP/IP settings
reflect 'DC01' as the DNS Server....

If 'DC02' is not pointing to the internal DNS Server in your environment (
read: DC01 ) then it will have a problem finding 'the domain stuff', which
will cause a big problem for it trying to become a Domain Controller!

Does this help?

--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com