Posted on : 03-09-2010 | By : DamianD | In : Direct Access, VMware Virtualisation, vSphere 5, vsphere4.1
Update News! : a fix is on the cards – see here: http://www.justhyp.com/2011/11/01/vsphere-client-over-microsoft-direct-access-pt2/
Updated: Support have confirmed my suspicion that Direct Access and VI client 4.1 are not compatible. Have passed client logs on to VM which will be provided to the client development team for consideration. Ho Hum
Just posted this on the VM community forum.
All, since upgrading out internal infrastructure to vSphere 4.1 we have not been able to connect to the guest vm console from either vCenter or direct to ESX using the vSphere 4.1 client. This was working in vSphere 4.0.
The error returned is “the hostname could not be resolved”.
A network trace indicates that although the initial connection to vCenter or the Host is successful (DNS resolves) the connection made within the application to the console fails as a dns call is made to the external dns server ignoring with windows dns resolution order!
Has something changed in the vSphere 4.1 client?
We have enabled IPv6 on the host and registered the AAAA record in DNS bit no improvement. Anyone else seen this?
Heres an extract of the network trace error received
blanked section displays the dns name of the vCenter Server.
Anyone got a clue what is going on here?