Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

ESXi host does not retain Active Directory membership after a reboot (2005012)

Symptoms

  • An ESXi host can join Active Directory (AD), but AD authentication always fails
  • Using Windows Authentication to connect to the host with the vSphere Client fails
  • Using an AD account with Remote Tech Support mode (SSH) fails
  • The host is no longer joined to the AD domain after a reboot

Resolution

To troubleshoot this issue, check that the host meets basic requirements to be joined to Active Directory:
  1. Check the DNS and routing configuration and ensure that a valid host name and domain name are entered.
  2. Ensure that the configured DNS servers are valid for Active Directory and can resolve other Active Directory systems (the Domain Controllers).
  3. Ensure that the search domain(s) includes the host domain name, as well as any other required domains for the network.
  4. Ensure that the Time Configuration on the host is configured to sync with a Domain Controller.
  5. Ensure that the host is configured to use a static IP address.
  6. Ensure that the Domain Controller host name and the ESX/ESXi host name are resolvable by the configured DNS servers.

See Also

Update History

11/26/2012 - Added ESXi 5.0 and 5.1 to Products

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 1 Ratings
Actions
KB: