Domain Controller Down (VM)
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch It has both. I set a static IP on the computer I am on currently and can connect to the internet.
There we go. Now the answer comes out.
The server holding DHCP and DNS roles is down.
This is the problem.
-
@coliver said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@coliver said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@coliver Can't I use one domain as the primary (FSMO)? Why is that not an issue. I'm sure I'm not understanding something about this.
One domain as the primary? There is no more primary or secondary domain controller all of them are now master/master.
Only one has FSMO roles though and that is the server that is down
That's fine. That shouldn't matter you can have the domain controller fail without issues for a little while. Generally a good amount of time as the Master/Master synchronization does its job.
In theory, weeks or more, but.... it sounds like his DCs were not set up properly and don't fail over.
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch It has both. I set a static IP on the computer I am on currently and can connect to the internet.
There we go. Now the answer comes out.
The server holder DHCP and DNS roles is down.
This is the problem.
Exactly as predicted, simple network configuration error. Not even domain related.
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch It has both. I set a static IP on the computer I am on currently and can connect to the internet.
Now that you are online again, is DNS working on the DC that is up? If so, good. If not, why not?
-
@scottalanmiller said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch It has both. I set a static IP on the computer I am on currently and can connect to the internet.
There we go. Now the answer comes out.
The server holder DHCP and DNS roles is down.
This is the problem.
Exactly as predicted, simple network configuration error. Not even domain related.
Exactly. Seizing FSMO roles would do zero to resolve the issue.
-
@scottalanmiller said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch It has both. I set a static IP on the computer I am on currently and can connect to the internet.
Now that you are online again, is DNS working on the DC that is up? If so, good. If not, why not?
Willing to bet that the second DNS server is not in the DHCP config so the clients only looked to the first.
BUt that is unfixable at the moment.
-
@JaredBusch said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch It has both. I set a static IP on the computer I am on currently and can connect to the internet.
Now that you are online again, is DNS working on the DC that is up? If so, good. If not, why not?
Willing to bet that the second DNS server is not in the DHCP config so the clients only looked to the first.
BUt that is unfixable at the moment.
That's my guess as well.
-
@JaredBusch said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch It has both. I set a static IP on the computer I am on currently and can connect to the internet.
Now that you are online again, is DNS working on the DC that is up? If so, good. If not, why not?
Willing to bet that the second DNS server is not in the DHCP config so the clients only looked to the first.
Which would also explain why he can't rejoin the network.
Would still be good to know if the second DC is up and running.
-
So ignore everything related to omg, it is a DC.
You simply resolve a normal basic VMWare VM issue.
-
@BRRABill said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch It has both. I set a static IP on the computer I am on currently and can connect to the internet.
Now that you are online again, is DNS working on the DC that is up? If so, good. If not, why not?
Willing to bet that the second DNS server is not in the DHCP config so the clients only looked to the first.
Which would also explain why he can't rejoin the network.
Would still be good to know if the second DC is up and running.
Not relevant to resolving the issue at hand.
-
@JaredBusch said in Domain Controller Down (VM):
So ignore everything related to omg, it is a DC.
You simply resolve a normal basic VMWare VM issue.
This ^^^
Time to work through good, old fashioned triage.
-
No redundant DNS and no DHCP failover.... basic networking issues. Now that you've discovered them you can fix them permanently.
-
@JaredBusch said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch It has both. I set a static IP on the computer I am on currently and can connect to the internet.
Now that you are online again, is DNS working on the DC that is up? If so, good. If not, why not?
Willing to bet that the second DNS server is not in the DHCP config so the clients only looked to the first.
BUt that is unfixable at the moment.
How do I make it fixable? This places backups are absolutely horrendous and I'm sure it is not recoverable. I have been fighting with them to change it and then this happens.
-
The fastest thing to do is to do is to simply restore from Veeam/Unitrends/Whatever.
Done up and nothing else matters.
You can then prioritize resolving the fagility in the current setup.
-
If you have no backups then you need to look at DHCP and getting a second/new server set up. Or seeing if your firewall has the ability to hand out addresses that may be the quickest way to do it.
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch It has both. I set a static IP on the computer I am on currently and can connect to the internet.
Now that you are online again, is DNS working on the DC that is up? If so, good. If not, why not?
Willing to bet that the second DNS server is not in the DHCP config so the clients only looked to the first.
BUt that is unfixable at the moment.
How do I make it fixable? This places backups are absolutely horrendous and I'm sure it is not recoverable. I have been fighting with them to change it and then this happens.
If you have no backup, then browse the datastore as we told you and find out if all the VM files are still there.
In terms of DR, the only important one is the VMDK(s)
-
@coliver said in Domain Controller Down (VM):
If you have no backups then you need to look at DHCP and getting a second/new server set up. Or seeing if your firewall has the ability to hand out addresses that may be the quickest way to do it.
That is a step down the road if the VM is completely unrecoverable.
-
@JaredBusch said in Domain Controller Down (VM):
The fastest thing to do is to do is to simply restore from Veeam/Unitrends/Whatever.
Done up and nothing else matters.
You can then prioritize resolving the fagility in the current setup.
So AD on the down DC would not have been syncing with the other DC he has if DNS was set up incorrectly?
-
@BRRABill said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
The fastest thing to do is to do is to simply restore from Veeam/Unitrends/Whatever.
Done up and nothing else matters.
You can then prioritize resolving the fagility in the current setup.
So AD on the down DC would not have been syncing with the other DC he has if DNS was set up incorrectly?
This does not matter FFS, forget about AD.
-
@BRRABill said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
The fastest thing to do is to do is to simply restore from Veeam/Unitrends/Whatever.
Done up and nothing else matters.
You can then prioritize resolving the fagility in the current setup.
So AD on the down DC would not have been syncing with the other DC he has if DNS was set up incorrectly?
This is a down DNS and DHCP server for all intents and purposes at this point. We don't care about AD until he gets DNS and DHCP back up and running.
