Domain Controller Down (VM)
-
FOrked the topic about the DCs because it's not helping the OP during an outage.
-
This post is deleted! -
@JaredBusch said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
@BRRABill said in Domain Controller Down (VM):
No he said he can't access it.
He did?
He did not. You are not crazy.
He said
"I'm assuming we must have had a domain syncing problem before this occurred, otherwise the other domain should have picked everything up as it is round robin. I attempted to disconnect my PC from the domain and reconnect. It claims there are no active directory controllers found." -
@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):
@coliver said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 is the VMDK there?
When I attempt to browse it kicks back an error stating "the server could not interpret the users request. the server is unavailable"
You're browsing in the VMWare console? The easiest way to get to it is via:
I'm running version 5.1.0 and I just click on Datastores
So you are using the fat client on your workstation?
Are you logged in with VMWare local account or a domain account?
Because obviously you have domain issues because of the bad DNS setup.
log in to the VMWare client with root and the local password.
I'm logging in with root and the local password actually on the server itself.
No you are not. You said you are using a client. The VMWare server itself only provides a command line interface.
They created a VM called vcenter that uses the client so yes you are correct.
That's not what anyone means when we say to log into the VMware ESXi server itself. That's a client on a VM. Very, very different.
Log into the actual server to remove any unnecessary points of complexity.
That VM is likely jsut running the VMWare vCenter web thing or whatever it is called.
Install the old thick client on your desk and connect to the server directly and browse the data store.
Very close to a breakdown, not that that is any of your problems.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2089791 is this what you are referring to? If not, where can I locate the thick client?
-
@wirestyle22 said in Domain Controller Down (VM):
@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):
@coliver said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 is the VMDK there?
When I attempt to browse it kicks back an error stating "the server could not interpret the users request. the server is unavailable"
You're browsing in the VMWare console? The easiest way to get to it is via:
I'm running version 5.1.0 and I just click on Datastores
So you are using the fat client on your workstation?
Are you logged in with VMWare local account or a domain account?
Because obviously you have domain issues because of the bad DNS setup.
log in to the VMWare client with root and the local password.
I'm logging in with root and the local password actually on the server itself.
No you are not. You said you are using a client. The VMWare server itself only provides a command line interface.
They created a VM called vcenter that uses the client so yes you are correct.
That's not what anyone means when we say to log into the VMware ESXi server itself. That's a client on a VM. Very, very different.
Log into the actual server to remove any unnecessary points of complexity.
That VM is likely jsut running the VMWare vCenter web thing or whatever it is called.
Install the old thick client on your desk and connect to the server directly and browse the data store.
Very close to a breakdown, not that that is any of your problems.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2089791 is this what you are referring to? If not, where can I locate the thick client?
Yes
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@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):
@coliver said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 is the VMDK there?
When I attempt to browse it kicks back an error stating "the server could not interpret the users request. the server is unavailable"
You're browsing in the VMWare console? The easiest way to get to it is via:
I'm running version 5.1.0 and I just click on Datastores
So you are using the fat client on your workstation?
Are you logged in with VMWare local account or a domain account?
Because obviously you have domain issues because of the bad DNS setup.
log in to the VMWare client with root and the local password.
I'm logging in with root and the local password actually on the server itself.
No you are not. You said you are using a client. The VMWare server itself only provides a command line interface.
They created a VM called vcenter that uses the client so yes you are correct.
That's not what anyone means when we say to log into the VMware ESXi server itself. That's a client on a VM. Very, very different.
Log into the actual server to remove any unnecessary points of complexity.
That VM is likely jsut running the VMWare vCenter web thing or whatever it is called.
Install the old thick client on your desk and connect to the server directly and browse the data store.
Very close to a breakdown, not that that is any of your problems.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2089791 is this what you are referring to? If not, where can I locate the thick client?
Yes
Downloading. Thanks.
-
@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):
@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):
@coliver said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 is the VMDK there?
When I attempt to browse it kicks back an error stating "the server could not interpret the users request. the server is unavailable"
You're browsing in the VMWare console? The easiest way to get to it is via:
I'm running version 5.1.0 and I just click on Datastores
So you are using the fat client on your workstation?
Are you logged in with VMWare local account or a domain account?
Because obviously you have domain issues because of the bad DNS setup.
log in to the VMWare client with root and the local password.
I'm logging in with root and the local password actually on the server itself.
No you are not. You said you are using a client. The VMWare server itself only provides a command line interface.
They created a VM called vcenter that uses the client so yes you are correct.
That's not what anyone means when we say to log into the VMware ESXi server itself. That's a client on a VM. Very, very different.
Log into the actual server to remove any unnecessary points of complexity.
That VM is likely jsut running the VMWare vCenter web thing or whatever it is called.
Install the old thick client on your desk and connect to the server directly and browse the data store.
Very close to a breakdown, not that that is any of your problems.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2089791 is this what you are referring to? If not, where can I locate the thick client?
Yes
Downloading. Thanks.
You may well hav issues connecting without the right version.
When I was managing a number of ESXi hosts, I had to install that thing 4 times on my laptop for it to properly connect to each version
-
@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):
@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):
@coliver said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 is the VMDK there?
When I attempt to browse it kicks back an error stating "the server could not interpret the users request. the server is unavailable"
You're browsing in the VMWare console? The easiest way to get to it is via:
I'm running version 5.1.0 and I just click on Datastores
So you are using the fat client on your workstation?
Are you logged in with VMWare local account or a domain account?
Because obviously you have domain issues because of the bad DNS setup.
log in to the VMWare client with root and the local password.
I'm logging in with root and the local password actually on the server itself.
No you are not. You said you are using a client. The VMWare server itself only provides a command line interface.
They created a VM called vcenter that uses the client so yes you are correct.
That's not what anyone means when we say to log into the VMware ESXi server itself. That's a client on a VM. Very, very different.
Log into the actual server to remove any unnecessary points of complexity.
That VM is likely jsut running the VMWare vCenter web thing or whatever it is called.
Install the old thick client on your desk and connect to the server directly and browse the data store.
Very close to a breakdown, not that that is any of your problems.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2089791 is this what you are referring to? If not, where can I locate the thick client?
Yes
Downloading. Thanks.
You may well hav issues connecting without the right version.
When I was managing a number of ESXi hosts, I had to install that thing 4 times on my laptop for it to properly connect to each version
Good to know. Thank you.
-
@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):
@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):
@coliver said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 is the VMDK there?
When I attempt to browse it kicks back an error stating "the server could not interpret the users request. the server is unavailable"
You're browsing in the VMWare console? The easiest way to get to it is via:
I'm running version 5.1.0 and I just click on Datastores
So you are using the fat client on your workstation?
Are you logged in with VMWare local account or a domain account?
Because obviously you have domain issues because of the bad DNS setup.
log in to the VMWare client with root and the local password.
I'm logging in with root and the local password actually on the server itself.
No you are not. You said you are using a client. The VMWare server itself only provides a command line interface.
They created a VM called vcenter that uses the client so yes you are correct.
That's not what anyone means when we say to log into the VMware ESXi server itself. That's a client on a VM. Very, very different.
Log into the actual server to remove any unnecessary points of complexity.
That VM is likely jsut running the VMWare vCenter web thing or whatever it is called.
Install the old thick client on your desk and connect to the server directly and browse the data store.
Very close to a breakdown, not that that is any of your problems.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2089791 is this what you are referring to? If not, where can I locate the thick client?
Yes
Downloading. Thanks.
You may well hav issues connecting without the right version.
When I was managing a number of ESXi hosts, I had to install that thing 4 times on my laptop for it to properly connect to each version
Good to know. Thank you.
You have 5.1 but there are multiple versions of 5.1 just FYI.
-
@BRRABill said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
@BRRABill said in Domain Controller Down (VM):
No he said he can't access it.
He did?
He did not. You are not crazy.
He said
"I'm assuming we must have had a domain syncing problem before this occurred, otherwise the other domain should have picked everything up as it is round robin. I attempted to disconnect my PC from the domain and reconnect. It claims there are no active directory controllers found."That, in no way, suggests that he cant access it.
-
My fingers are numb. I hope I don't have an aneurysm
-
@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):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@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):
@coliver said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 is the VMDK there?
When I attempt to browse it kicks back an error stating "the server could not interpret the users request. the server is unavailable"
You're browsing in the VMWare console? The easiest way to get to it is via:
I'm running version 5.1.0 and I just click on Datastores
So you are using the fat client on your workstation?
Are you logged in with VMWare local account or a domain account?
Because obviously you have domain issues because of the bad DNS setup.
log in to the VMWare client with root and the local password.
I'm logging in with root and the local password actually on the server itself.
No you are not. You said you are using a client. The VMWare server itself only provides a command line interface.
They created a VM called vcenter that uses the client so yes you are correct.
That's not what anyone means when we say to log into the VMware ESXi server itself. That's a client on a VM. Very, very different.
Log into the actual server to remove any unnecessary points of complexity.
That VM is likely jsut running the VMWare vCenter web thing or whatever it is called.
Install the old thick client on your desk and connect to the server directly and browse the data store.
Very close to a breakdown, not that that is any of your problems.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2089791 is this what you are referring to? If not, where can I locate the thick client?
Yes
Downloading. Thanks.
You may well hav issues connecting without the right version.
When I was managing a number of ESXi hosts, I had to install that thing 4 times on my laptop for it to properly connect to each version
Good to know. Thank you.
You have 5.1 but there are multiple versions of 5.1 just FYI.
Installed. Logged in using root.
-
@wirestyle22 said in Domain Controller Down (VM):
My fingers are numb. I hope I don't have an aneurysm
Take a step back, breath, and focus. This isn't anything to be stressed THAT much over. At the end of the day it's all just a heap of metal. You've isolated your problem, you're just working on what you need to do to fix it.
- restore the original failed VM to working order
If that doesn't pan out all you need to do is get a DHCP server up and running and point it at your secondary DC for DNS.
The more stressed you are the more that stress is going to reverberate through your office/users. You've got quite a few people here to help with the troubleshooting, you'll get through it.
-
@wirestyle22 said in Domain Controller Down (VM):
My fingers are numb. I hope I don't have an aneurysm
Get a beer, relax. Seriously, or decaf tea or something. Take the time to breath. You should not be overly stressed here.
-
@RamblingBiped said in Domain Controller Down (VM):
The more stressed you are the more that stress is going to reverberate through your office/users. You've got quite a few people here to help with the troubleshooting, you'll get through it.
This is important. Your calm, confident air is what will keep things in order.
-
@scottalanmiller said in Domain Controller Down (VM):
@RamblingBiped said in Domain Controller Down (VM):
The more stressed you are the more that stress is going to reverberate through your office/users. You've got quite a few people here to help with the troubleshooting, you'll get through it.
This is important. Your calm, confident air is what will keep things in order.
Yeah you couldn't be at a better place for help. (With the exception of me gumming up the works and requiring a thread fork.)
Take a quick walk outside if you need to clear your head. Breathe in for 5 seconds. Hold for 5 seconds. Breathe out for 5 seconds. Repeat.
-
What are my next steps?
-
@wirestyle22 said in Domain Controller Down (VM):
What are my next steps?
Can you see the datastore contents with that?
-
@scottalanmiller said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
What are my next steps?
Can you see the datastore contents with that?
I do not have it anywhere any longer to make a screenshot for you..
but right click on the datastore and choose browse
-
@JaredBusch said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
What are my next steps?
Can you see the datastore contents with that?
I do not have it anywhere any longer to make a screenshot for you..
but right click on the datastore and choose browse
I see ESX01 and ESX02. ESX01 has the vcenter file, which is what I am accessing to view the VM's typically but nothing else
