Domain Controller Down (VM)

scottalanmiller

@wirestyle22 said in Domain Controller Down (VM):

@scottalanmiller said in Domain Controller Down (VM):

DO you have an office, a cubicle? Put up a sign that says that there is an outage and you are working on it and ANY interruption will stop you from working on it. So only interrupt if what you need is more important than fixing the servers and are prepared to report such to management.

I'm in the server room. Virtually no one has the key thank god.

Still, a sign is good

Dashrender

@wirestyle22 said in Domain Controller Down (VM):

@scottalanmiller said in Domain Controller Down (VM):

DO you have an office, a cubicle? Put up a sign that says that there is an outage and you are working on it and ANY interruption will stop you from working on it. So only interrupt if what you need is more important than fixing the servers and are prepared to report such to management.

I'm in the server room. Virtually no one has the key thank god.

rebooting from the console?

wirestyle22

Same situation after reboot. Tested from the other host next to it, exact same situation. Cannot ping gateway etc

Dashrender

@wirestyle22 said in Domain Controller Down (VM):

Same situation after reboot. Tested from the other host next to it, exact same situation. Cannot ping gateway etc

what is the other host?

Dashrender

Reboot the network switch

wirestyle22

@Dashrender said in Domain Controller Down (VM):

@wirestyle22 said in Domain Controller Down (VM):

Same situation after reboot. Tested from the other host next to it, exact same situation. Cannot ping gateway etc

what is the other host?

I have ESX01 and ESX02 in this particular building

dafyre

@wirestyle22 said in Domain Controller Down (VM):

Same situation after reboot. Tested from the other host next to it, exact same situation. Cannot ping gateway etc

Are you able to ping the DC's IP or get into it via RDP now that you have rebooted ?

dafyre

@Dashrender said in Domain Controller Down (VM):

Reboot the network switch

This too.

JaredBusch

Assuming ESX01 is the one we have all the trouble accessing, can you connect the vSphere client to ESX02?

wirestyle22

@JaredBusch said in Domain Controller Down (VM):

Assuming ESX01 is the one we have all the trouble accessing, can you connect the vSphere client to ESX02?

I actually can access ESX02. This was not the case before I rebooted.

wirestyle22

@JaredBusch Actually, totally randomly it's working now. I'm at a loss. I can remote into either of them now.

Dashrender

So is the switch rebooted? any change?

wirestyle22

@Dashrender view above

Dashrender

did you reboot the switch?

wirestyle22

@Dashrender yes

Dashrender

I bet your switch locked something out. or it was locked up.

JaredBusch

@wirestyle22 said in Domain Controller Down (VM):

@Dashrender yes

What does remote into mean? Are you using the vSphere client you downloaded?

Can you ping everything now then?

wirestyle22

@JaredBusch said in Domain Controller Down (VM):

@wirestyle22 said in Domain Controller Down (VM):

@Dashrender yes

What does remote into mean? Are you using the vSphere client you downloaded?

Can you ping everything now then?

Yes the client. Yeah I can ping everything.

JaredBusch

@wirestyle22 said in Domain Controller Down (VM):

@JaredBusch said in Domain Controller Down (VM):

@wirestyle22 said in Domain Controller Down (VM):

@Dashrender yes

What does remote into mean? Are you using the vSphere client you downloaded?

Can you ping everything now then?

Yeah I can.

So look at the Host with the 2003 DC using the vSphere client.

Can you now start the VM?
If not, can you now at least browse to the datastore.

wirestyle22

Everything just came back online