ESX VC connection failure after domain migration

Posted on 2009-04-16
Last Modified: 2012-08-14
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.  
Question by:Jurinnov
    LVL 21

    Accepted Solution

    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?
    LVL 7

    Expert Comment

    Under the Configuration -> DNS and Routing Option, change the FQDN of the Server and reboot the ESX for the changes to take place.


    Author Comment

    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.

    Author Comment

    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.

    Author Comment

    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 .

    Author Comment

    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.

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Join & Write a Comment

    First I will try to share a design of a Veeam Backup Infrastructure without Direct NFS Access backup.  ( Note: Direct NFS Access backup …
    This article is an update and follow-up of my previous article:   Storage 101: common concepts in the IT enterprise storage This time, I expand on more frequently used storage concepts.
    Teach the user how to use configure the vCenter Server storage filters Open vSphere Web Client:  Navigate to vCenter Server Advanced Settings: Add the four vCenter Server storage filters: Review the advanced settings: Modify the values of the four v…
    This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.

    755 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    21 Experts available now in Live!

    Get 1:1 Help Now