[Synt4xerror]

Hello,

I am trying to delete my child domain DC within my lab. I am experiencing a error when I try. It seems that the domain controller can't speak to my forest root domain. I have them both running and look at both and do not see any errors. Reason I am deleting this DC which is a part of a child domain is so I can start over with a certain step. Any help is appreciated!

Domain: rutech.local
Child: Operations.rutech.local

Error:
The operation failed because:
A domain controller could not be contacted for the domain operations.rutech.local that contained an account for this computer.

"The specified domain either does not exist or could not be contacted"

- I can access the forest root domain by UNC path: \\dc-name\c$ - I can use my credentials from the forest root domain and it allows me to log on. So I don't see why my child domain cannot contact the forest root!

Thanks,
Synt4x

 

[Wand3r3r]

Re: Deleting a Domain Controller Error

where is the child domain pointed to for dns? The ms dns server or the gateway/internet?

 

[Synt4xerror]

Re: Deleting a Domain Controller Error

Primary DNS is its self, Secondary is my router. I do have NS records on both DNS servers (Forest Root and Child). Should I point it to the forest root domain instead of its self?

Thanks for replying Wand3r3r

 

[Wand3r3r]

Re: Deleting a Domain Controller Error

Yes point it to the main dns server. Error indicates its not seeing a record to the root dc.

 

[Synt4xerror]

Re: Deleting a Domain Controller Error

I just checked and the primary DNS was set to loopback address 127.0.0.1 and secondary was set to my forest root domain. I decided to change the primary to my forest root, and the secondary to the child domain (itself). Still getting this error.

Attached is a photo of error.

 

[Wand3r3r]

Re: Deleting a Domain Controller Error

Looks like its already removed. You did dcpromo it down?

 

[djaburg]

Re: Deleting a Domain Controller Error

Perhaps the account was manually deleted on the DC and that's why the error comes up on the CDC machine when trying to "unjoin" the domain?

 

[Synt4xerror]

Re: Deleting a Domain Controller Error

I never manually deleted the DC. I am trying to DCPromo it now so I can demote it. This is where I get the error.

 

[Wand3r3r]

Re: Deleting a Domain Controller Error

lets see a ipconfig /all from both the child and root DCs

 

[Synt4xerror]

Re: Deleting a Domain Controller Error

Attached are the ipconfigs from both servers. I have labeled them at the bottom of each photo in the command prompt.

Thanks for the help guys

 

[Synt4xerror]

Re: Deleting a Domain Controller Error

Ok, now I am thinking there is a DNS problem. When I do nslookup on both machines they can see each other. ANy ideas?

 

[Synt4xerror]

Re: Deleting a Domain Controller Error

As I am doing some more digging, I come to find that my CO-01svr (CHild Domain) can talk to CA-HQ (FOrest Root) just fine. But, when I try to contact CO-01svr from CA-HQ, I get errors. I am trying to add a name server within CA-HQ for CO-01svr and get a non authoritative error.

 

[djaburg]

Re: Deleting a Domain Controller Error

How are they navigating the different subnets with a 255.255.255.0 mask? Is there a router between nets? I'll assume you've changed IP's after you setup the domain(s)?

 

[Synt4xerror]

Re: Deleting a Domain Controller Error

I have setup NAT on the main machine. These DCs are running off Hyper-V, I have created multiple virtual NICs within Hyper-V, assigned them appropriately. This is where NAT comes into play for my machines. I wanted to make it so I run 4 different DCs on the same machine without a physical router.

The IPs were assigned before I promoted the DCs to their roles.

 

[Synt4xerror]

Re: Deleting a Domain Controller Error

I figured it out........

I don't know how I over looked this. So, the Child Domain was able to speak to the Forest Root, but not the other way around. I looked at the trust relationship, replication process, and name servers. All looked A O K. So, I went into the Forest Root and checked the primary and secondary DNS settings. I noticed for the Forest Root had my main router as the primary DNS server, and then the Forest Root (itself) for the secondary DNS server. I did not see it pointing to the Child Domain. I made the Primary the Forest Root (itself) and the secondary the Child Domain.

I was successfully able to demote the DC and start over again. I have been very determined to get this resolved without deleting and starting all over again. It is helping me understand how this all works more and more. The little things are what is overlooked by me and I have to stop that.

I am sorry if I wasted any of your time, I appreciate you guys trying to help me out.

 

[Tomshawk]

Interesting set up you have there. I don't think I've seen anything like it before even in my past studies.

The way you have nated your servers is quirky, I'm tempted to give it a try just so I can see if I can duplicate your results

well done

 

[Synt4xerror]

Yeah, I had to find a way to do this since I am using my only computer at home. I had to shrink my hard drive and install server 08 r2. If you want I can tell you my steps for the networking aspects.

 

[Tomshawk]

Please, when you have time, I'd be most interested.

 

[Synt4xerror]

I save this in a text incase I forget


1) I created four internal network adapters within Hyper-V.

2) I gave each network adapter the IP address on the subnet I wanted.
- 192.168.0.254
- 192.168.2.254
- 192.168.4.254
- 192.168.6.254

3) I installed the Network Policy and Access Services role within Server Manager

4) I Configured and Enabled Routing and Remote Access
- I chose custom settings and just checked off LAN Routing

5) I expanded the views of the role and the options below, right clicked on General under IPv4 and selected 'New Routing Protocol" and chose NAT.

5) Within the NAT section I right clicked and chose 'New Interface', I then started adding my Network Adapters.
- In my case I have to add 5 things under NAT
- 1) Private Interface connected to Private Network - Network Adapter Chosen 192.168.0.0
- 1) Private Interface connected to Private Network - Network Adapter Chosen 192.168.2.0
- 1) Private Interface connected to Private Network - Network Adapter Chosen 192.168.4.0
- 1) Private Interface connected to Private Network - Network Adapter Chosen 192.168.6.0
- 1) Public Interface connected to the Internet - Make sure you select 'Enable NAT on this Interface' - Also, this is where the Network Adapter I use for the internet on the main server where hyper-V is installed.

6) I assigned each Hyper-V Virtual Machine a NIC card by going to each of their settings and under Network Adapters giving the correct option.

7) Booted it up each machine and did the following for the static IP address
- IP: 192.168.0.1
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.254
Preferred DNS: 192.168.1.1

I repeated step 7 four times and used the default gateway as the network adapter I had setup previously in Network Manager. I also used my router as the DNS server, which may change when I install DNS and configure it correctly.

 

[Tomshawk]

Thank you sir, I look forward to giving this a try.