Finding a DC frm a remote subnet

  • Thread starter Thread starter myrt webb
  • Start date Start date
M

myrt webb

I am trying to create a child domain with a computer on a
separate subnet from the root domain DC.

The connection between the computers is working. I can
ping the DC from the separate computer. But, when I try to
install AD the separate computer cannot find the root
domain DC. I think I need a special entry in the DNS zone
for the root DC but I cannot figure out what form it
should be. I thought it should be a SRV record but not of
the choices for an SRV record seem to fit.

What do I do so the seperate computer can contact the root
DC and I can install the child domain?
 
Is the computer in the remote location poiniting to the DNS server in the
root domain for DNS resolution? It MUST. And it MUST NOT point to any other
DNS. Check that, and if it doesn't help, send us the output of you nslookup
and iponfig /all

HTH
Deji
 
Let me make plain what I am trying to do.

I have a Win2000 standalone server that I want to make a
DC for a child domain of the root domain rwd.com.

The standalone server is on a separate subnet from the
rwd.com DC. The rwd.com DC is entered in the host file of
the standalone server so I can ping successfully from the
standalone to the DC using either the IP address or the
computer name server01.rwd.com. Server01 is also the DNS
server for the domain.

The DNS for the standalone server is pointed to the
rwd.com DC. When I enter "nslookup rwd.com" on the
standalone server it returns "rwd.com 10.10.0.1" which is
the correct IP for the rwd.com DC.

But when I try to install AD on the standalone server and
establish a child domain of rwd.com I get a message that
rwd.com cannot be found.
 
In
myrt webb said:
Let me make plain what I am trying to do.

I have a Win2000 standalone server that I want to make a
DC for a child domain of the root domain rwd.com.

The standalone server is on a separate subnet from the
rwd.com DC. The rwd.com DC is entered in the host file of
the standalone server so I can ping successfully from the
standalone to the DC using either the IP address or the
computer name server01.rwd.com. Server01 is also the DNS
server for the domain.
Click to expand...

Since the DC is on a different subnet is it connecting through a firewall?
If it is you need to setup a VPN to the subnet the parent DC is on.
Preferably to a member but if you have to make it to the DC. There are many
ports required for AD and you do not want to open them all through the
firewall.
The DNS for the standalone server is pointed to the
rwd.com DC. When I enter "nslookup rwd.com" on the
standalone server it returns "rwd.com 10.10.0.1" which is
the correct IP for the rwd.com DC.
Click to expand...
At least you know you have UDP 53.
But when I try to install AD on the standalone server and
establish a child domain of rwd.com I get a message that
rwd.com cannot be found.
Click to expand...
Also read up on this: 255248 - HOW TO Create a Child Domain in Active
Directory and Delegate the DNS Namespace to the Child Domain
http://support.microsoft.com/default.aspx?scid=kb;en-us;255248&FR=1
 
Back
Top