One forest, two child domains, three subnets

I need some serious help.....

I have been charged with setting up two separate domains that will share resources and reside on the same forest yet have thier own subnets.  Is this possible?

I have setup a 2008 forest.  I am trying to set up one of the 2008 child domains but of course during dcpromo, the new dc doesn't see the forest because it is on a different subnet.

I can ping the forest server.  All subnets have been created on the router and all can access the internet.

What am I doing wrong or missing?  Anyone?  Pleeeeeease......
carolinasgirl28Asked:
Who is Participating?
 
Brad HeldConnect With a Mentor Commented:
So on the new server, its dns must only point to DC's in the parent domain.

So if ServerB is the child DC then it's dns must point to ServerA in the Parent.

Once its promoted and child domain is created, then some conditional forwarders need to be in place or the DNS forward lookup zones need to be replicated forest wide. This will allow clients to locate those resources in the other domain(s).
0
 
Sasha KranjacCommented:
You have network connectivity between the servers - the routing is working. Did you run ping using netbios, FQDN or IP address?
Is DNS working? Have you tried nslookup and checked if the name resolution works as it should?
The steps are:
1. verified and working connectivity (addressing, routers, gateways)
2. verified and working name resolution (names, FQDNs, name servers, services, DNS records...)
3. only when 1. and 2. are working flawlessly proceed setting up Active Directory

Please double check steps 1. and 2.

Can you post the error you get when dcpromo fails?
0
 
carolinasgirl28Author Commented:
I am in the process of putting everything back (painstakingly) so that everyone can funcion Monday morning. I will have to try this again next weekend.

All servers are connected via fibre.
Could ping servers via ip address

The error I got from dcpromo was that the forest could not be contacted.  I'm assuming because the server was on another subnet?
0
 
Sasha KranjacCommented:
I suspect that it might be a name resolution issue (DNS) because you have connectivity and DC still could not be contacted.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.