After a lengthy and arduous issue of resolving a virtual machine problem
VM losing connectivity with the domain. It was working fine prior to the VM issues but the following day after the VM was up and running again, I attempted to remote into the server and received the message "There are currently no logon servers available to service the logon request". I resolved this by unjoining the server from the domain and then re-joining it.
This worked like a champ for a few more days and then the problem occurred again yesterday afternoon. No changes have been made to the server whatsoever in this span of time and it gets very little usage other than the occasional remote session just to peek at the VM and make sure everything is working as intended. This time, I deleted the computer account from AD altogether after unjoining the server from the domain and then re-joined it and, as predicted, it's working correctly again now.
What I don't understand is why this issue would resurface without any cause. Is there a way I can look into what exactly initiated this loss of connectivity? Event Viewer doesn't provide much in the way of meaningful info as to what went wrong other than the following Group Policy error:
"The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name Sysytem (DNS) is configured and working correctly."
Apart from this error, nothing else is really showing up around the time that connectivity dropped. While it is working again for now, any assistance in how I can audit this to make sure it won't happen again or to better track down the root of the problem would be greatly appreciated. The VM is a very important component for our finance department and I don't want to leave them high and dry if this goes out again and I'm not here to handle the unjoin/rejoin operation.
For what it may be worth, this server is running Windows Server 2008 SP2. Our primary DC is running Windows Server 2003 and our domain level is set to 2003
SOLUTION
#########################
Ironically - have seen this happen before, and removing and rejoining the domain didn't fix it for long. What did fix this was simply removing and re-adding the NIC drivers in device manager. Don't know why, and I've only seen it happen w/ systems that run VCenter or are actual Virtual Machines.... This has happened more than once, and doesn't seem to matter what flavor of Windows Server is involved 2K3/2K8 x32/x64 makes no difference.
VM losing connectivity with the domain. It was working fine prior to the VM issues but the following day after the VM was up and running again, I attempted to remote into the server and received the message "There are currently no logon servers available to service the logon request". I resolved this by unjoining the server from the domain and then re-joining it.
This worked like a champ for a few more days and then the problem occurred again yesterday afternoon. No changes have been made to the server whatsoever in this span of time and it gets very little usage other than the occasional remote session just to peek at the VM and make sure everything is working as intended. This time, I deleted the computer account from AD altogether after unjoining the server from the domain and then re-joined it and, as predicted, it's working correctly again now.
What I don't understand is why this issue would resurface without any cause. Is there a way I can look into what exactly initiated this loss of connectivity? Event Viewer doesn't provide much in the way of meaningful info as to what went wrong other than the following Group Policy error:
"The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name Sysytem (DNS) is configured and working correctly."
Apart from this error, nothing else is really showing up around the time that connectivity dropped. While it is working again for now, any assistance in how I can audit this to make sure it won't happen again or to better track down the root of the problem would be greatly appreciated. The VM is a very important component for our finance department and I don't want to leave them high and dry if this goes out again and I'm not here to handle the unjoin/rejoin operation.
For what it may be worth, this server is running Windows Server 2008 SP2. Our primary DC is running Windows Server 2003 and our domain level is set to 2003
SOLUTION
#########################
Ironically - have seen this happen before, and removing and rejoining the domain didn't fix it for long. What did fix this was simply removing and re-adding the NIC drivers in device manager. Don't know why, and I've only seen it happen w/ systems that run VCenter or are actual Virtual Machines.... This has happened more than once, and doesn't seem to matter what flavor of Windows Server is involved 2K3/2K8 x32/x64 makes no difference.
No comments:
Post a Comment