Domain Controller Down (VM)
-
@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):
What are my next steps?
Can you see the datastore contents with that?
I do not have it anywhere any longer to make a screenshot for you..
but right click on the datastore and choose browse
I see ESX01 and ESX02. ESX01 has the vcenter file, which is what I am accessing to view the VM's typically but nothing else
Screenshots help. install greenshot if you have nothing else.
show us what you see.
-
@JaredBusch said in Domain Controller Down (VM):
@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):
What are my next steps?
Can you see the datastore contents with that?
I do not have it anywhere any longer to make a screenshot for you..
but right click on the datastore and choose browse
I see ESX01 and ESX02. ESX01 has the vcenter file, which is what I am accessing to view the VM's typically but nothing else
Screenshots help. install greenshot if you have nothing else.
show us what you see.
I say that because those sound like the names of the VM hosts themselves.
-
@JaredBusch said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@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):
What are my next steps?
Can you see the datastore contents with that?
I do not have it anywhere any longer to make a screenshot for you..
but right click on the datastore and choose browse
I see ESX01 and ESX02. ESX01 has the vcenter file, which is what I am accessing to view the VM's typically but nothing else
Screenshots help. install greenshot if you have nothing else.
show us what you see.
I say that because those sound like the names of the VM hosts themselves.
I can't access the internet from the computers I can access the server from, which is where the screenshot would be taken. I have no cell data. I can't do it
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@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):
What are my next steps?
Can you see the datastore contents with that?
I do not have it anywhere any longer to make a screenshot for you..
but right click on the datastore and choose browse
I see ESX01 and ESX02. ESX01 has the vcenter file, which is what I am accessing to view the VM's typically but nothing else
Screenshots help. install greenshot if you have nothing else.
show us what you see.
I say that because those sound like the names of the VM hosts themselves.
I can't access the internet from the computers I can access the server from, which is where the screenshot would be taken. I have no cell data. I can't do it
take the one computer that you are working from and update the DNS to point to the 8.8.8.8 and you will. you have no need for local DNS on that machine right now.
Just don't do anythig silly agian like disjoin from the domain.
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@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):
What are my next steps?
Can you see the datastore contents with that?
I do not have it anywhere any longer to make a screenshot for you..
but right click on the datastore and choose browse
I see ESX01 and ESX02. ESX01 has the vcenter file, which is what I am accessing to view the VM's typically but nothing else
Screenshots help. install greenshot if you have nothing else.
show us what you see.
I say that because those sound like the names of the VM hosts themselves.
I can't access the internet from the computers I can access the server from, which is where the screenshot would be taken. I have no cell data. I can't do it
take the one computer that you are working from and update the DNS to point to the 8.8.8.8 and you will. you have no need for local DNS on that machine right now.
Just don't do anythig silly agian like disjoin from the domain.
I attempted that just now and cannot connect to the VM host machine using the client that way.
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@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):
What are my next steps?
Can you see the datastore contents with that?
I do not have it anywhere any longer to make a screenshot for you..
but right click on the datastore and choose browse
I see ESX01 and ESX02. ESX01 has the vcenter file, which is what I am accessing to view the VM's typically but nothing else
Screenshots help. install greenshot if you have nothing else.
show us what you see.
I say that because those sound like the names of the VM hosts themselves.
I can't access the internet from the computers I can access the server from, which is where the screenshot would be taken. I have no cell data. I can't do it
Another thing to fix. I hope you are keeping a notepad handy so that you are not stressing trying to remember all these breaks for later. At least this thread will be here.
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@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):
What are my next steps?
Can you see the datastore contents with that?
I do not have it anywhere any longer to make a screenshot for you..
but right click on the datastore and choose browse
I see ESX01 and ESX02. ESX01 has the vcenter file, which is what I am accessing to view the VM's typically but nothing else
Screenshots help. install greenshot if you have nothing else.
show us what you see.
I say that because those sound like the names of the VM hosts themselves.
I can't access the internet from the computers I can access the server from, which is where the screenshot would be taken. I have no cell data. I can't do it
take the one computer that you are working from and update the DNS to point to the 8.8.8.8 and you will. you have no need for local DNS on that machine right now.
Just don't do anythig silly agian like disjoin from the domain.
I attempted that just now and cannot connect to the VM host machine using the client that way.
Not possible. You are doing something else wrong then.
Change that machine to a static IP
point gateway to your router
point DNS to google.
confirm dns resolution and internet accessping google.com
confirm local network connectivityping 192.168.10.1(or whatever your router is)
confirm connectivity to the VMHostping 192.168.10.14 -
@wirestyle22 you can also go physically to the VMHost and log in to the console and confirm the network settings.
-
-
That's a Windows machine. We need it from ESXi.
-
@wirestyle22 said in Domain Controller Down (VM):
Go log in to the VMHost physically and verify the networking. Something is wrong there. likely the subnet.
-
@scottalanmiller said in Domain Controller Down (VM):
That's a Windows machine. We need it from ESXi.
yes, but that is what i told him to do first and proves the machine functionality.
-
@JaredBusch said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
That's a Windows machine. We need it from ESXi.
yes, but that is what i told him to do first and proves the machine functionality.
OH okay. I missed that request earlier.
-
@scottalanmiller said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
That's a Windows machine. We need it from ESXi.
yes, but that is what i told him to do first and proves the machine functionality.
OH okay. I missed that request earlier.
Basically confirming 100% setup of the windows machine he is using to attempt access to the VMHost
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
Go log in to the VMHost physically and verify the networking. Something is wrong there. likely the subnet.
I can still connect to it using the client on the VM previously mentioned though which is using the same ip/subnet. Wouldn't that not be possible?
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
Go log in to the VMHost physically and verify the networking. Something is wrong there. likely the subnet.
I can still connect to it using the client on the VM previously mentioned though which is using the same ip/subnet. Wouldn't that not be possible?
Depends on the subnets involved. just verify the host itself.
-
@JaredBusch said in Domain Controller Down (VM):
Depends on the subnets involved. just verify the host itself.
@wirestyle22 no update in 15 minutes? cannot help with no information.
-
@JaredBusch said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
Depends on the subnets involved. just verify the host itself.
@wirestyle22 no update in 15 minutes? cannot help with no information.
Maybe he fixed it and is out having a celebratory beer!
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
Go log in to the VMHost physically and verify the networking. Something is wrong there. likely the subnet.
I can still connect to it using the client on the VM previously mentioned though which is using the same ip/subnet. Wouldn't that not be possible?
Depends on the subnets involved. just verify the host itself.
I think they tried to setup replication on the ESXi hosts and when the domain went down it attempted to bring it back up unsuccessfully. I see my DC as having a similar IP as my hosts. Is this proper thinking?
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
Go log in to the VMHost physically and verify the networking. Something is wrong there. likely the subnet.
I can still connect to it using the client on the VM previously mentioned though which is using the same ip/subnet. Wouldn't that not be possible?
Depends on the subnets involved. just verify the host itself.
I think they tried to setup replication on the ESXi hosts and when the domain went down it attempted to bring it back up unsuccessfully. I see my DC as having a similar IP as my hosts. Is this proper thinking?
You are back to using improper terms and not logically troubleshooting.
ESXi does not even know or care about your domain.
ESXi only knows and cares about the VM guests configured on it.
