Additional DC not functioning if the Primary DC is down !!
-
type in the name or IP of the new DC.
-
i think since the OK button is not activated, the DC2 is not seeing itself as a DC
-
Did you run DCPromo on the new Domain Controller so that it actually became a DC?
-
With the working DC online, when you go to ADUC and look under the Domain Controllers OU, do you see both servers?
-
@Dashrender said:
Did you run DCPromo on the new Domain Controller so that it actually became a DC?
yeah off course, and choose it to be global catalog and DNS
-
@Dashrender said:
With the working DC online, when you go to ADUC and look under the Domain Controllers OU, do you see both servers?
yeah in DC1, i can see in both DC in domain controllers OU
-
now the DC2 is offline and i set a static IP to it and set DNS to point to himself (because it is offline)
after i enter his ip, it shows online but giving me error message
-
-
@IT-ADMIN said:
@Dashrender said:
With the working DC online, when you go to ADUC and look under the Domain Controllers OU, do you see both servers?
yeah in DC1, i can see in both DC in domain controllers OU
Can you switch to DC2 when DC1 is online?
-
The preferred DNS server of the network card in your domain controllers should always point to themselves. Well, assuming that you are using standard Windows DNS.
The alternate should then be the other DC.
On DC 1
DNS Preferred: 127.0.0.1
DNS Alternate: 192.168.1.XX <- IP of DC2On DC 2
DNS Preferred: 127.0.0.1
DNS Alternate: 192.168.1.XX <- IP of DC1 -
@Dashrender said:
@IT-ADMIN said:
@coliver said:
What version of AD/Windows Server are you running?
both are windows server 2008 entreprise R2
Wow - hefty licenses there.
No, we already now that about his organization.
-
@JaredBusch said:
The preferred DNS server of the network card in your domain controllers should always point to themselves. Well, assuming that you are using standard Windows DNS.
The alternate should then be the other DC.
On DC 1
DNS Preferred: 127.0.0.1
DNS Alternate: 192.168.1.XX <- IP of DC2On DC 2
DNS Preferred: 127.0.0.1
DNS Alternate: 192.168.1.XX <- IP of DC1I typically point to the other DC for my Preferred DNS, and myself second. This allows for faster booting, but I see reasons for either way.
-
i'm so sorry for this delay, because it is midnight here, so do you think DNS setting make sense even if the DC2 is offline ??
-
Best explanation regarding this that I've seen. See Jay's response:
http://community.spiceworks.com/topic/post/4301599 -
let us suppose that DC2 is offline and cannot see DC1 (which is the main reason i want to make DC2 for high availability) how DNS setting make any difference ??
-
Yes.
Let's assume DC2 is offline, but you want to see if you can run ADUC on DC2. When you run ADUC it uses DNS to try to open and failes.
But if you put in 127.0.0.1 as JB suggests, then it will still work, even with the network card unplugged.
-
@Dashrender said:
Yes.
Let's assume DC2 is offline, but you want to see if you can run ADUC on DC2. When you run ADUC it uses DNS to try to open and failes.
But if you put in 127.0.0.1 as JB suggests, then it will still work, even with the network card unplugged.
i tried that, i put the primary DNS as 127.0.0.1 but still cannot open ADUC,
-
While you had both DCs on the network together, where you able to connect ADUC to DC2?
-
i have a question please : do i have an issue or not, in another word: does DC1 (who has FSMO) should be online in order for DC2 to work properly or it is not a condition ???
-
@Dashrender said:
While you had both DCs on the network together, where you able to connect ADUC to DC2?
i'm able to open ADUC in DC2 only if DC2 can see DC1, as soon as i unplug DC2 from the network i cannot open ADUC
DC2 it is kind of a mirror right now, it is useless, it is nothing without DC1
