Connection to VM fails over a Microsoft Direct Access Session - 4.1 client specific

[damiandavis]

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?

[arkturas]

Got the same problem 'black screen - when opening a new console session',  i'm using Microsoft Direct Access to connect to my vmware infrastructure from an offsite location.

my vCenter server is running 5.0 (my vcenter client is on 5.0) - hopefully 5.0.1 will resolve my problem.

[arkturas]

I found the following in the 5.0 U1 release notes

vCenter Inventory Service does not support binding on IPv6 interfaces by default
When you install vCenter Server, vCenter Inventory Service supports only IPv4 by default.

Workaround: To enable IPv6 support for vCenter Inventory Service, take the following steps.

1. Stop the vCenter Inventory Service.
   1. From the Administrative Tools control panel, select Services.
   2. Right-click vCenter Inventory Service and select Stop.
2. In a text editor, open the following file:
   Inventory_Service_installation_directory/lib/server/config/dataservice.properties
3. Change the value for dataservice.nio.enabled to false.
4. Restart the vCenter Inventory Service.