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):
Didn't allow me to access it
DId you try by DNS name? that won't work.
\\192.168.10.X\c$not `\server2008\c$I'm really distracted and I apologize guys. There are way too many people around me currently. I can access the sysvol folder
Tell them all to go to hell. Seriously.
I know your office number, I can call and tell them that if you want.
I'm at my wits end honestly but no, thanks. I appreciate everyone's help. I hope you guys know that. Unsure of how I came across in this thread.
I learned a long time ago to tell a superior to go to hell because I was doing my damned job. You need to do the same. Because making you not think straight is just prolonging things.
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender 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):
Didn't allow me to access it
DId you try by DNS name? that won't work.
\\192.168.10.X\c$not `\server2008\c$I'm really distracted and I apologize guys. There are way too many people around me currently. I can access the sysvol folder
probably not in a write-able fashion though. so no good
so \192.168.10.x\c$ doesn't prompt you for a password of a network admin.
no it doesn't
So seriously, at this point, just reboot the host. You have no access to the proper tools and no way to change anything.
-
@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):
Didn't allow me to access it
DId you try by DNS name? that won't work.
\\192.168.10.X\c$not `\server2008\c$I'm really distracted and I apologize guys. There are way too many people around me currently. I can access the sysvol folder
Tell them all to go to hell. Seriously.
I know your office number, I can call and tell them that if you want.
I'm at my wits end honestly but no, thanks. I appreciate everyone's help. I hope you guys know that. Unsure of how I came across in this thread.
I learned a long time ago to tell a superior to go to hell because I was doing my damned job. You need to do the same. Because making you not think straight is just prolonging things.
And it makes you look like you've lost control, which you have. Don't be rude, but sit them down and explain - THEY are part of the problem. Are they going to sabotage the company? If this matters, they need to stop interrupting. If it doesn't matter, why are they bothering? In neither case is interrupting good for the company. You aren't going to forget that this is happening.
It's okay to have one single person assisting you that feeds updates out to other people, but they need to keep everyone else at bay and they need to keep the interrupts to a minimum. The company needs status, but if there isn't one person handling that status, it's just children playing at being managers who think it's funny that the business is losing money. Don't let them suck you into that game, be the professional.
-
@JaredBusch Rebooting.
-
-
@JaredBusch 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 said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
Didn't allow me to access it
DId you try by DNS name? that won't work.
\\192.168.10.X\c$not `\server2008\c$I'm really distracted and I apologize guys. There are way too many people around me currently. I can access the sysvol folder
probably not in a write-able fashion though. so no good
so \192.168.10.x\c$ doesn't prompt you for a password of a network admin.
no it doesn't
So seriously, at this point, just reboot the host. You have no access to the proper tools and no way to change anything.
Well still before this, i'd change the DNS of the 2008 server and try to download the installer
-
DO you have an office, a cubicle? Put up a sign that says that there is an outage and you are working on it and ANY interruption will stop you from working on it. So only interrupt if what you need is more important than fixing the servers and are prepared to report such to management.
-
@scottalanmiller said in Domain Controller Down (VM):
DO you have an office, a cubicle? Put up a sign that says that there is an outage and you are working on it and ANY interruption will stop you from working on it. So only interrupt if what you need is more important than fixing the servers and are prepared to report such to management.
I'm in the server room. Virtually no one has the key thank god.
-
@wirestyle22 said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
DO you have an office, a cubicle? Put up a sign that says that there is an outage and you are working on it and ANY interruption will stop you from working on it. So only interrupt if what you need is more important than fixing the servers and are prepared to report such to management.
I'm in the server room. Virtually no one has the key thank god.
Still, a sign is good
-
@wirestyle22 said in Domain Controller Down (VM):
@scottalanmiller said in Domain Controller Down (VM):
DO you have an office, a cubicle? Put up a sign that says that there is an outage and you are working on it and ANY interruption will stop you from working on it. So only interrupt if what you need is more important than fixing the servers and are prepared to report such to management.
I'm in the server room. Virtually no one has the key thank god.
rebooting from the console?
-
Same situation after reboot. Tested from the other host next to it, exact same situation. Cannot ping gateway etc
-
@wirestyle22 said in Domain Controller Down (VM):
Same situation after reboot. Tested from the other host next to it, exact same situation. Cannot ping gateway etc
what is the other host?
-
Reboot the network switch
-
@Dashrender said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
Same situation after reboot. Tested from the other host next to it, exact same situation. Cannot ping gateway etc
what is the other host?
I have ESX01 and ESX02 in this particular building
-
@wirestyle22 said in Domain Controller Down (VM):
Same situation after reboot. Tested from the other host next to it, exact same situation. Cannot ping gateway etc
Are you able to ping the DC's IP or get into it via RDP now that you have rebooted ?
-
-
Assuming ESX01 is the one we have all the trouble accessing, can you connect the vSphere client to ESX02?
-
@JaredBusch said in Domain Controller Down (VM):
Assuming ESX01 is the one we have all the trouble accessing, can you connect the vSphere client to ESX02?
I actually can access ESX02. This was not the case before I rebooted.
-
@JaredBusch Actually, totally randomly it's working now. I'm at a loss. I can remote into either of them now.
-
So is the switch rebooted? any change?
