[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 733
  • Last Modified:

ESX VC connection failure after domain migration

We migrated our domain to another by removing the machines and adding them to the existing domain.  Before addressing any needs of the ESX host machine the domain controller was migrated.  This left the ESX Host in the now invalid domain. I changed the FQDN of the ESX host (Ver 3.5) via the VIC (Ver 2.5).  I rebooted the ESX machine and verified the files on the ESX host and connected directly to the ESX host with the new name to verify that I could see it. (Yes I know you have to connect to the VIC machine) That worked, however when I try to connect to the VIC machine it still sees the ESX host under the old domain and therefore everything is showing as disconnected and I do not have the ability to administer the ESX machine as I did before the move (go figure.).  Is there a file I must modify to get the VIC client to see the new change?  Is there a way to correct the problem I am having.  
0
Jurinnov
Asked:
Jurinnov
  • 4
1 Solution
 
za_mkhCommented:
If you right click your ESX server in the the VIC cosole, you should be able to update the ESX host settings so that it matches it's new FQDN?
 
 
0
 
kumarnirmalCommented:
Under the Configuration -> DNS and Routing Option, change the FQDN of the Server and reboot the ESX for the changes to take place.

DNS.JPG
0
 
JurinnovAuthor Commented:
Well I changed its info under config and rebooted both the ESX box and the VIC machine that seemed staright forward.  I don't have an option that stands out that allows me to update.  Under DNS and Routing I see that it has the new domain name, maybe it's something screwy in DNS as it is still pointing to the other server, and that IP has not changed I am wondering if I point it to the new domains DNS server and have it update if that would fix it.
0
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

 
JurinnovAuthor Commented:
Yes, that is what I did this morning to change things, however the VIC client still points to the previous domain.  It appears that the problem is on the VIC client side as I can ping and connect to the ESX host in its new domain.
0
 
JurinnovAuthor Commented:
The VIC client does see the ESX host as I can ping in both directions.  Seems to be a pointer on the VIC client itself.  Host.olddomain is in the VIC client still and it should be host.newdomain.  Now I can point the VIC Client directly to the ESX host, but then I don't have full admin access .
0
 
JurinnovAuthor Commented:
GOT IT!  Because this was not properly handled upfront the fix is to remove the host from the VIC and add it back in with the correct FQDM.  Everything comes back in and you have full admin privileges.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now