Domain Controller Down (VM)
-
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch No I can't
Did you verify the subnet mask on the host?
-
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch No I can't
Does the host network connection on this host have any activity lights?
good call - check the network connection from that server to the switch.
try pinging it from another computer on the network.
-
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch No I can't
Does the host network connection on this host have any activity lights?
Yes and they are lit up
-
@Dashrender said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch No I can't
Does the host network connection on this host have any activity lights?
good call - check the network connection from that server to the switch.
try pinging it from another computer on the network.
No, once he verifies the subnet he needs to begin testing from the ESXi host and not the rest of the network. We have likely finally found the problem.
-
@wirestyle22 please confirm the subnet mask and DNS on the VMHost in questions.
-
@wirestyle22 said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch No I can't
Does the host network connection on this host have any activity lights?
Yes and they are lit up
OK so then the hypervisor hardware appears to be working. From the hypervisor console you need to check the NIC settings and make sure the netmask, gateway IP address are all accurate.
As a last step if you still can't access the system, check to make sure the switch is working. Connect a laptop to the same switch, with an IP address in the same range as the hypervisor and see if you can ping the hypervisor from that laptop.
-
damn can't do pictures.
From the ESXi server console - do what JB asked - get the full Network information. You'll have to log into the ESXi console and navigate the DOS like interface to show it.
-
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch No I can't
Does the host network connection on this host have any activity lights?
Yes and they are lit up
OK so then the hypervisor hardware appears to be working. From the hypervisor console you need to check the NIC settings and make sure the netmask, gateway IP address are all accurate.
As a last step if you still can't access the system, check to make sure the switch is working. Connect a laptop to the same switch, with an IP address in the same range as the hypervisor and see if you can ping the hypervisor from that laptop.
This is already what he has been doing.
-
@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).
-
@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 with the secondary set to the DC that is on but not working correctly.
That is the issue why none of your clients machines can get online.
-
@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 with the secondary set to the DC that is on but not working correctly.
That is the issue why none of your clients machines can get online.
What? Not it's not.
-
@Dashrender 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 with the secondary set to the DC that is on but not working correctly.
That is the issue why none of your clients machines can get online.
What? Not it's not.
All of the clients in the network are pointing to a DNS/DHCP server that is offline. The secondary server is pointing to the server that is also offline.
-
@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 with the secondary set to the DC that is on but not working correctly.
That is the issue why none of your clients machines can get online.
No it is not. WTF are you tlaking about. this is the VMhost. It could care less about the DNS as far as the guests are concerned.
-
@DustinB3403 said in Domain Controller Down (VM):
@Dashrender 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 with the secondary set to the DC that is on but not working correctly.
That is the issue why none of your clients machines can get online.
What? Not it's not.
All of the clients in the network are pointing to a DNS/DHCP server that is offline. The secondary server is pointing to the server that is also offline.
Not what was said at all.
-
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 LAN -
@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.
