Domain Controller Down (VM)
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 please confirm the subnet mask and DNS on the VMHost in questions.
Subnet Mask is 255.255.255.0 DNS is set to the DC that is inaccessible (primary) with the secondary set to the DC that is on but not working correctly (Secondary).
This host DNS is set to using the VM that is offline.
The fact that this VM is offline is the cause of the DNS related issues he's having.
-
OK ML is no longer showing me the picture of the IP you found this ESXi Host to be.
is it 192.168.10.14?
-
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 please confirm the subnet mask and DNS on the VMHost in questions.
Subnet Mask is 255.255.255.0 DNS is set to the DC that is inaccessible (primary) with the secondary set to the DC that is on but not working correctly (Secondary).
This host DNS is set to using the VM that is offline.
The fact that this VM is offline is the cause of the DNS related issues he's having.
Just stop cluttering the thread. We are resolving a down VM not DNS. We realize there are DNS issues from bad configuration. but nothing currently being worked on has a damned thing to do with that.
-
@Dashrender said in Domain Controller Down (VM):
OK ML is no longer showing me the picture of the IP you found this ESXi Host to be.
is it 192.168.10.14?
He was originally connecting to .14 yes. but found it was actually 12 when he checked physically.
-
@JaredBusch said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 please confirm the subnet mask and DNS on the VMHost in questions.
Subnet Mask is 255.255.255.0 DNS is set to the DC that is inaccessible (primary) with the secondary set to the DC that is on but not working correctly (Secondary).
This host DNS is set to using the VM that is offline.
The fact that this VM is offline is the cause of the DNS related issues he's having.
Just stop cluttering the thread. We are resolving a down VM not DNS. We realize there are DNS issues from bad configuration. but nothing currently being worked on has a damned thing to do with that.
Fair enough, I was looking at the problem of him not being able to access the host from vsphere.
But it's a trivial issue.
-
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 please confirm the subnet mask and DNS on the VMHost in questions.
Subnet Mask is 255.255.255.0 DNS is set to the DC that is inaccessible (primary) with the secondary set to the DC that is on but not working correctly (Secondary).
This host DNS is set to using the VM that is offline.
The fact that this VM is offline is the cause of the DNS related issues he's having.
Sure that's true, but that's not why the VM itself is offline, which is the real issue here. We're trying to figure out why WS can't connect from the fat VMWare client to the ESXi host.
-
@DustinB3403 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 please confirm the subnet mask and DNS on the VMHost in questions.
Subnet Mask is 255.255.255.0 DNS is set to the DC that is inaccessible (primary) with the secondary set to the DC that is on but not working correctly (Secondary).
This host DNS is set to using the VM that is offline.
The fact that this VM is offline is the cause of the DNS related issues he's having.
Just stop cluttering the thread. We are resolving a down VM not DNS. We realize there are DNS issues from bad configuration. but nothing currently being worked on has a damned thing to do with that.
Fair enough, I was looking at the problem of him not being able to access the host from vsphere.
But it's a trivial issue.
DNS has nothing to do with it. He was connecting by IP. 192.168.10.12. DNS is not required for that. only a subnet.
-
JB - could WS be denied direct access to the ESXi host because he's running vSphere Web client (you know the control setup vmware has for multiple VM hosts?)
-
@JaredBusch said in Domain Controller Down (VM):
Alright @wirestyle22
from the VMHost, there is a network diag section. shouold let you input things to ping.Can you ping the gateway?
Can you ping any other device on the LANFailed pinging to the gateway.
Succeeded in pinging the 2008 DC -
@DustinB3403 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 please confirm the subnet mask and DNS on the VMHost in questions.
Subnet Mask is 255.255.255.0 DNS is set to the DC that is inaccessible (primary) with the secondary set to the DC that is on but not working correctly (Secondary).
This host DNS is set to using the VM that is offline.
The fact that this VM is offline is the cause of the DNS related issues he's having.
Just stop cluttering the thread. We are resolving a down VM not DNS. We realize there are DNS issues from bad configuration. but nothing currently being worked on has a damned thing to do with that.
Fair enough, I was looking at the problem of him not being able to access the host from vsphere.
But it's a trivial issue.
he's not trying to connect to vsphere via a hostname though, he's trying to use an IP address.
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
Alright @wirestyle22
from the VMHost, there is a network diag section. shouold let you input things to ping.Can you ping the gateway?
Can you ping any other device on the LANFailed pinging to the gateway.
Succeeded in pinging the 2008 DCThat is a problem.
-
log into the 2008 DC and look at it's IP settings and share them if possible.
-
192.168.10.55
255.255.255.0
192.168.10.1 -
@Dashrender said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 please confirm the subnet mask and DNS on the VMHost in questions.
Subnet Mask is 255.255.255.0 DNS is set to the DC that is inaccessible (primary) with the secondary set to the DC that is on but not working correctly (Secondary).
This host DNS is set to using the VM that is offline.
The fact that this VM is offline is the cause of the DNS related issues he's having.
Just stop cluttering the thread. We are resolving a down VM not DNS. We realize there are DNS issues from bad configuration. but nothing currently being worked on has a damned thing to do with that.
Fair enough, I was looking at the problem of him not being able to access the host from vsphere.
But it's a trivial issue.
he's not trying to connect to vsphere via a hostname though, he's trying to use an IP address.
He was also using the wrong IP address. In either case it means that there is nothing wrong with the equipment between the hypervisor and his workstation (or the rest of the network).
I think I read this already, but is it not possible to restore a backup of this VM. (are there none?)
-
can you log into the vSphere web console?
-
-
@DustinB3403 said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 please confirm the subnet mask and DNS on the VMHost in questions.
Subnet Mask is 255.255.255.0 DNS is set to the DC that is inaccessible (primary) with the secondary set to the DC that is on but not working correctly (Secondary).
This host DNS is set to using the VM that is offline.
The fact that this VM is offline is the cause of the DNS related issues he's having.
Just stop cluttering the thread. We are resolving a down VM not DNS. We realize there are DNS issues from bad configuration. but nothing currently being worked on has a damned thing to do with that.
Fair enough, I was looking at the problem of him not being able to access the host from vsphere.
But it's a trivial issue.
he's not trying to connect to vsphere via a hostname though, he's trying to use an IP address.
He was also using the wrong IP address. In either case it means that there is nothing wrong with the equipment between the hypervisor and his workstation (or the rest of the network).
I think I read this already, but is it not possible to restore a backup of this VM. (are there none?)
None known. At this point we are simply trying to get the VMDK to recreate the VM
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
can you log into the vSphere web console?
No
What is the IP of that?
is the ESXi server with the down VM on it 192.168.10.14?
I'm trying to keep that stuff straight as I help. -
@JaredBusch tested again just to see and the first ping test resolved the hostname the second didn't. unsure if that is relevant
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
can you log into the vSphere web console?
No
How are you trying to access the Web console, via IP in a web browser or by a URL?
