Cannot join a member server to Domain

[Guest]

Hi all experts, I tried to run the dcpromo of a member server in a site that has already had a AD controller. I run dcpromo and giving all the login password to it. Then it gives an error "The wizard cannot gain access to the list of the domains in the forest...... The RPC Server is unavailable
I tested the AD controller itself, and the DNS looks ok and can browse the domain in the network neighborhood as well
I also found that all the clients (win2k professional) cannot browse the network neigh. I also cannot join the clients to the domain with the similar symptom as above

Many Thanks for your support~!

Tim

 

[SaltPeter]

Hi all experts, I tried to run the dcpromo of a member server in a site

that has already had a AD controller. I run dcpromo and giving all the login
password to it. Then it gives an error "The wizard cannot gain access to the
list of the domains in the forest...... The RPC Server is unavailable"

I tested the AD controller itself, and the DNS looks ok and can browse the

domain in the network neighborhood as well.

I also found that all the clients (win2k professional) cannot browse the

network neigh. I also cannot join the clients to the domain with the similar
symptom as above.

Many Thanks for your support~!!

Tim

You mentioned that DNS "looks OK" from the DC, but are your clients using
it? Including the soon-to-be-joined-and-promoted stand-alone server?

If your clients are obtaining ip_address via a dhcp scope, configure the
scope options to include the DNS server's ip_address. The stand-alone server
is probably using a static address, in which case you need to specify the
DNS server's ip explicitly in its tcp/ip properties.

Needless to say, if DC and stand-alone + clients reside in seperate physical
subnets, connection can't be achieved without the presence of a router.

It's discouraged to attempt running dcpromo on a stand-alone server. You
should first join the domain, which generates a member server, then promote.
None of which can occur if name resolution fails.

Network neighbourhood is not populated by dns, but rather by netbios.
Assuming that nbt is running.