Domain Controller Down (VM)
-
@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.
-
@wirestyle22 and you still have not answered the question. What is the network configuration of the VMHost.
-
@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?
Who is "they" and why are there people messing with the systems without coordinating with the people in charge of them? Are these your staff, random managers?
-
@scottalanmiller 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):
@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?
Who is "they" and why are there people messing with the systems without coordinating with the people in charge of them? Are these your staff, random managers?
predecessors
-
@scottalanmiller 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):
@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?
Who is "they" and why are there people messing with the systems without coordinating with the people in charge of them? Are these your staff, random managers?
Prior IT or prior MSP if I recall his employer correctly.
-
@wirestyle22 said in Domain Controller Down (VM):
I see my DC as having a similar IP as my hosts.
What does the term "similar IP" mean to you?
-
@JaredBusch said in Domain Controller Down (VM):
@scottalanmiller 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):
@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?
Who is "they" and why are there people messing with the systems without coordinating with the people in charge of them? Are these your staff, random managers?
Prior IT or prior MSP if I recall his employer correctly.
Oh, so someone a while ago, not like someone behind his back this morning.
-
@wirestyle22 said in Domain Controller Down (VM):
@scottalanmiller 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):
@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?
Who is "they" and why are there people messing with the systems without coordinating with the people in charge of them? Are these your staff, random managers?
predecessors
Gotcha. I thought this was going on since you were last in the office or something.
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 and you still have not answered the question. What is the network configuration of the VMHost.
@wirestyle22 do you know how to get this info?
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 and you still have not answered the question. What is the network configuration of the VMHost.
I want to answer your question but I do not have the right credentials. The list I was given at hire is incorrect and I am trying to contact the previous director. The root password is not correct.
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 and you still have not answered the question. What is the network configuration of the VMHost.
I want to answer your question but I do not have the right credentials. The list I was given at hire is incorrect and I am trying to contact the previous director.
They are the same credentials as you used to log in with the thick client. just the normal root account.
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 and you still have not answered the question. What is the network configuration of the VMHost.
I want to answer your question but I do not have the right credentials. The list I was given at hire is incorrect and I am trying to contact the previous director.
They are the same credentials as you used to log in with the thick client. just the normal root account.
I understand but it's not working. Is there a different way for me to confirm the settings until I hear back from this guy?
-
Not being familiar ... is it listed int he console?
For example, in XS, you can see all the networking stuff right from the console screen.
is there such a thing?
-
@BRRABill There is no console option to interact with the ESXi host in that way as far as I can see. I have XS at home.
