Link to home
Start Free TrialLog in
Avatar of GDC4S1
GDC4S1

asked on

Powering up a Domain Controller in Isolation

Hi Experts ----

I have an environment where I have to power-down my domain controllers on a regular basis (nuts...I know) and I have spotty network connectivity.  I have noticed that when I try to power-up a domain controller that is not a forest or domain root and I do not have connectivity to the WAN, I cannot logon to the domain controller.  This domain controller has replicated with the domain and forest.  Is there any way I can power-up and have operational this isolated domain controller?
Avatar of Rajith Enchiparambil
Rajith Enchiparambil
Flag of United Kingdom of Great Britain and Northern Ireland image

Is this domain controller in a branch office with a DC in the head office?

Is the DC in question a GC as well?
Avatar of GDC4S1
GDC4S1

ASKER

The DC is a branch office and I do have it configured as a GC.  It may not be able at times to reach the root at HQ.
Is the DC an additional DC for the domain or is it a DC in it's own child domain/ domain?
Avatar of GDC4S1

ASKER

I have both cases.  The branch is part of a child domain and I have a child root domain not at the HQ that has the same power and connectivity issues.  In summary I have two DCs each at remote sites one is the child root and the other is a member of the child domain.  The forest root is at HQ.
What is the DC's DNS server settings in ipconfig /all?
Avatar of GDC4S1

ASKER

The child peer (not root) points to himself, followed by the child domain root, followed by the forest root.  The child domain root points to himself and the forest root.
ASKER CERTIFIED SOLUTION
Avatar of LauraEHunterMVP
LauraEHunterMVP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial