Domain Controller Down (VM)
-
I know that when I tried to attach to my 5.5 client with the full thick client After I joined the VM Host to a vSphere web client that it gave me a warning/error about how the server was already joined to a vSphere control server (damn don't know correct name).
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
Not being able to ping the gateway means it sounds like something was restricted on the management network.
Since your 2003 DC is down, give your workstation the IP of the DC and try to connect with the thick client.
Attempted this with the same result
Can you ping your workstation form the host on that IP or the host from your workstation now though?
-
@Dashrender said in Domain Controller Down (VM):
I know that when I tried to attach to my 5.5 client with the full thick client After I joined the VM Host to a vSphere web client that it gave me a warning/error about how the server was already joined to a vSphere control server (damn don't know correct name).
He stated earlier he was connected and saw two hosts.
-
Stupid question, but what would happen if he rebooted the host at this point? @wirestyle22 have you rebooted the host?
Services are down, and he's having basic connectivity issues.
Wouldn't it be prudent to give it a try?
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
Not being able to ping the gateway means it sounds like something was restricted on the management network.
Since your 2003 DC is down, give your workstation the IP of the DC and try to connect with the thick client.
Attempted this with the same result
Can you ping your workstation form the host on that IP or the host from your workstation now though?
Cannot ping the host from my PC. Also cannot ping my workstation from the Host.
-
@JaredBusch said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
I know that when I tried to attach to my 5.5 client with the full thick client After I joined the VM Host to a vSphere web client that it gave me a warning/error about how the server was already joined to a vSphere control server (damn don't know correct name).
He stated earlier he was connected and saw two hosts.
wasn't that from within the vSphere thing though? or was that the thick client?
My thick client for 5.1 and 5.5 only allowed me to log into one at a time. the only 'seeing' the hosts was a drop down list of things I've put in in the past.
https://i.imgur.com/2vEvjce.png -
@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):
Not being able to ping the gateway means it sounds like something was restricted on the management network.
Since your 2003 DC is down, give your workstation the IP of the DC and try to connect with the thick client.
Attempted this with the same result
Can you ping your workstation form the host on that IP or the host from your workstation now though?
Cannot ping the host from my PC. Also cannot ping my workstation from the Host.
Now that sounds as if the network switch is the issue.... Are you sure the network cables are still connected to the host?
-
What other VMs are on that ESXi server?
Can you shut them down?
-
@Dashrender I shouldn't do that until much later in the evening
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I shouldn't do that until much later in the evening
Are you users basically completely down unable to work?
-
put your testing desktop back to .253 in case your DC come sup
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I shouldn't do that until much later in the evening
Why not, if you are having issues that are severely impacting the business. Stopping the other services for a host reboot should be easily accepted.
Especially if it does address the issue.
-
At this point, I'd take a laptop and a cross over cable (or use an extra switch you have lying around) and connect the laptop directly to the server and see if you can ping it.
But when you do that, assuming you only have one network connection from the ESXi server to the switch, you'll take those other VMs offline. -
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I shouldn't do that until much later in the evening
Why not, if you are having issues that are severely impacting the business. Stopping the other services for a host reboot should be easily accepted.
Especially if it does address the issue.
I don't think that we know how much is affected yet. It might be trivial.
-
@Dashrender said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I shouldn't do that until much later in the evening
Are you users basically completely down unable to work?
Yes that is the case. I guess I can do that. Can you explain your reasoning? I'm a little shook right now.
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I shouldn't do that until much later in the evening
Are you users basically completely down unable to work?
Yes that is the case. I guess I can do that. Can you explain your reasoning? I'm a little shook right now.
see two posts above.
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I shouldn't do that until much later in the evening
Are you users basically completely down unable to work?
Yes that is the case. I guess I can do that. Can you explain your reasoning? I'm a little shook right now.
If your users a sitting with thumbs up their butts, then shutting down the other VM's that arent in use at the moment, and rebooting the Hypervisor shouldn't effect them anyways.
They are stuck doing nothing at the moment.
If they aren't doing anything anyways...
-
You need to solve the ESXi host can't talk on the local network problem.
I just though of this.
from the 2008 server, open a browser and put in the IP address of the EXSi host
and download the fat ESXi client to the 2008 server and install it there -
@Dashrender said in Domain Controller Down (VM):
You need to solve the ESXi host can't talk on the local network problem.
I just though of this.
from the 2008 server, open a browser and put in the IP address of the EXSi host
and download the fat ESXi client to the 2008 server and install it thereIf you truly feel you cannot reboot then do this.
This would very much be recommended since it is the only thing you can ping from the VMHost itself.
-
@wirestyle22 said
Cannot ping the host from my PC. Also cannot ping my workstation from the Host.
There is a VM working on the host, right? Can you ping the host from that, and vice versa?
