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.
-
@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.
Would you be able to see those restrictions in the DOS-like interface on the server console?
-
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch tested again just to see and the first ping test resolved the hostname the second didn't. unsure if that is relevant
when pinging what?
There is a network test in ESXi that pings 3 IP addresses. 1 is the gateway. 2 is the 2003 DC which isnt on, 3 is the 2008 DC and 4 is the hostname. the 2008 DC is the only successful now although the first test the hostname did resolve.
You're having DNS issues, so it's expected that DNS would fail eventually.
How are you trying to access the Web Console?
Are you using
https://SERVER-NAME:9443/vsphere-client/orhttps://ip address:9443/vsphere-client/I specifically have him not using the web client to avoid DNS issues. 5.1 was still fully dependant on the thick client as well. It was 5.5 i think when feature started not being available in the thick client.
-
@Dashrender 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.
Would you be able to see those restrictions in the DOS-like interface on the server console?
Been too long since I had a live system. I cannot tell you.
-
Seems like avoiding anything but IP addresses and direct access is best. Just too many things going wrong.
-
@JaredBusch said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch tested again just to see and the first ping test resolved the hostname the second didn't. unsure if that is relevant
when pinging what?
There is a network test in ESXi that pings 3 IP addresses. 1 is the gateway. 2 is the 2003 DC which isnt on, 3 is the 2008 DC and 4 is the hostname. the 2008 DC is the only successful now although the first test the hostname did resolve.
You're having DNS issues, so it's expected that DNS would fail eventually.
How are you trying to access the Web Console?
Are you using
https://SERVER-NAME:9443/vsphere-client/orhttps://ip address:9443/vsphere-client/I specifically have him not using the web client to avoid DNS issues. 5.1 was still fully dependant on the thick client as well. It was 5.5 i think when feature started not being available in the thick client.
Ah I missed that you had him download the management client.
-
@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
-
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.
