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?

[admin]

Hi damiandavis,

I don't recall any changes in vSphere 4.1 in regards to how it works with DNS.

There are a number of possible causes for the issue you are seeing, so we would need to isolate the issue further in order to fully understand what is going on.

Can you please provide the answers to the following questions:

1. Is this issue only being noticed with this one virtual machine, or are you seeing this with other virtual machines too?

2. Are you seeing this issue across mutliple virtual machines across multiple ESX hosts, or is this the only ESX server which is showing the issue?

3. If you connect to the specific ESX host using the VI Client and specifying the IP address for the server as opposed to the DNS name, are you able to open the virtual machine console?

Can you attach the "vmware.log" and the vmx configuration for this specific virtual machine as per the screenshot you attached already?

Regards,

Graham Daly

Knowledge Champion

VMware Inc.

[damiandavis]

Hi Graham,

In Reply,

1. Is this issue only being noticed with this one virtual machine, or are you seeing this with other virtual machines too? all virtual machines act the same way

2. Are you seeing this issue across mutliple virtual machines across

multiple ESX hosts, or is this the only ESX server which is showing the

issue? ALL Hosts are affected in the same manner.

3. If you connect to the specific ESX host using the VI Client and

specifying the IP address for the server as opposed to the DNS name, are

you able to open the virtual machine console? Direct IP address connections don't work over Direct access - you have to use dns resolution.

Can you attach the "vmware.log" and the vmx configuration for this

specific virtual machine as per the screenshot you attached already? Attached

Regards

Damian

[admin]

Hi Damian

I'm not to familar with Microsoft Direct Access. This is some new Windows feature that was introduced as of the Windows 7 and Windows 2008 operating systems, right?

So I am guessing that this "Direct Access" application or protocol is specific to the client machine which you are using to launch the vSphere client and attempting to connect to your virtual machines.

Do you have any other machines available to you on your network which you could use to try to connect to your virtual machines?

Just curious to see if the issue you are seeing is only visible when this "Microsoft Direct Access" feature/protocol is involved.

If you dont encounter the same problems when you exclude the "Direct Access", then it is quite possible that this "Direct Access" feature is not playing to well with vSphere. As a result, this should be investigated further by a VMware Technical Support engineer.

Do you have a vSphere support entitlement with VMware?

If yes, then I would strongly advise that you open a support request with our Technical Support team so that one of our engineers can work with you to isolate the cause for the issue you are currently seeing.

Once the root cause has been identified, I can work on getting this information captured in a Knowledge Base article within our Knowledge Base. I know that won't to much of a help to you per se, but at least we will be able to prevent other users from hitting this problem too.

Regards,

Graham Daly

Knowledge Champion

VMware Inc.

[damiandavis]

Direct access is providing a remote connection to vCenter as if the client is LAN based. All works well in that the connection is established to vCenter and all usual tabs are active. The guest connection function is the problem. If the client is on the internal LAN then no problem occurs

The crux of the issue is that the Direct Access solution using vSphere 4.0 is perfectly fine. The problem seems to have been introduced by upgrading to 4.1

Clearly the enablement of IPv6 may be a factor, as Direct Access uses IPv6 and tunnels IPv4. However enabling IPv6 on the hosts doesn't seem to resolve the issue.

I will raise a case, and if successfully resolved post the resolution here.

Thanks for your suggestions so far Graham

Damian Davis

Silversands Ltd

UK

[admin]

Yeah, sounds to me like some change between vSphere 4.0 and 4.1 is what is causing the issue, but what that change exactly is, unfortunately I have no idea at this moment in time.

Open the support request with our Technical Support team, include a link to this forum thread in the support request and provide as much information as you can in the support request. That way the engineering who gets assigned the ticket will be able to progress the issue as fast as possible.

When you get some further information via the support request, post it here and I will work on getting it documented in our Knowledge Base.

Hopefully this issue will be resolved for you shortly Damian

Regards,

Graham Daly

Knowledge Champion

VMware Inc.

[damiandavis]

Update:

Call progressing with VM support.

They have asked me to setup a test as they do not have a lot of experience of Direct Access.

Test goes as follows

1. install ESXi 4 Update 2 on a Server and Download VI 4.0 client to a direct access laptop that has not had the 4.1 client installed - Completed and connection to the console of a guest works.

2. upgrade client on laptop to 4.1 and test against ESXi 4 update 2 host - testing to happen today when VM support get in touch

3. connect 4.1 client back through to 4.1 host and troubleshoot DNS issue.

Clearly there have been changes made in the Host > client relationship that seem to be forcing a direct DNS lookup rather than utilise the Direct Access server DNS component. Interesting to see where this goes.

I'll update shortly.

[damiandavis]

Progress update:

Contacted by support today. Seems that they are now convinced that the 4.1 client has been recoded in a way that does not work properly with Direct Access. They recommend using RDP to a suitable server and using a "local" vi client from here.

I have uploaded client logs which support will provide to the client development team - hopefully we will see a DA compatible client for the next release.

For now Direct Access and VI client are not going to work together.

Will update again if any progress occurs - don't expect a quick turnaround

Damian.

[admin]

HI Damian,

Would you be able to private message me your VMware Support Request number for this incident?

I will be able to track it internally as well.

Regards,

Graham Daly

Knowledge Champion

VMware Inc.

[silversandsvm]

Graham, PM sent.

Cheers

Damian

[Nface21]

Hi,

I have the same exact problem. Since I have updated the client I can no longer connect to any hosts. 3.5, 4.0, or 4,1 console are unavailable and all show the same The host name could not be resolved. If there is some need for testing solution I am more than willing!!!

Do we know if there is any word on a possible fix for the issues and any idea of a timeframe?

Thanks a lot!!!

[damiandavis]

Hi, thanks for the offer of help with this issue - glad i'm not the only one seeing this issue.

Last update from friday was that the call had been posted from support to the development team. no indication on how long the fault turnaround will be.

I'll keep this thread updated once i hear something.

Damian

[Nface21]

Hi everyone,

It's been one month since last update, has anyone heard about any possible fix for this issues. I can still manage doing RDP onto another server and get the console from there, but its longer, slower and less efficient.

Is VMware planning in releasing any type of patch for the client or server vpshere apps? If so when can we expect to see it?

I understand Direct Access is not widely used yet but still for those of us that have abandon VPN for good it is a bit problematic!

Thanks a lot!!!

Nface

[damiandavis]

No update received as yet. I expect the process will be a long one to resolution.

I will ask for an update under the call ref.

Cheers

Damian Davis

Silversands Ltd

www.silversands.co.uk

[dwisby]

If this issue is going to take a long time to resolve, why has VMware been so vocal about upgrading to 4.1 when not all the kinks have been worked out and is it possible to roll the agents back to 4.0U2 on the hosts so we can manage with vCenter Server 4.0U2?

David

[tjhau]

All,

VMWare has broken the vsphere client at version 258672.

I was running ESXi 4.1 with the 'appropriate' client in a pure IPv6 environment, and could do everything except get a console window up -- the error was "host name could not be resolved".

I opened a SR on 24/11/2010, and last week was told that my IPv6 DNS is broken. It isn't.

Today I downgraded the ESXi to 4.0.0 Update 2 (build 261974) and tried the 4.0.0 VI Clients (running in the same Windows 7 VM that I was using before...)

Client 4.0.0 build 208111 works just fine

Client 4.0.0 build 258672 fails.

I'll update the SR and see what they excuse themselves with.

The irony is that I'm not allowed to bridge the IPv6 and IPv4 networks at the office, and VMware support can only use IPv4 to access Webex to look at my console

(BTW, if you connect 4.1 client -> 4.1 ESXi with IPv6 IP address, all works as expected.)

HTH,

Tim.

[damiandavis]

tjhau, thanks for your comments. I found in testing that 4.1 client wouldn't work over DA even with IPV6 configuration and AAAA records in DNS. I may try this specific test again.

Please keep us posted on your support call. I've asked twice for an update on my call but nothing doing.

I'll call them soon and apply the thumb screws.

Damian

[damiandavis]

Ok so just received an update from vmware support

Hello Damian,

Thank you for your Support Request.

My name is *engineer* from VMware and I have just taken ownership of this SR.

I am sorry for slow response. *engineer* who was working this SR has been out of the office for some time.

I can confirm that *engineer* opened a problem report with Engineering which they have been investigating. The root cause of the issue has been identified and engineering are working towards a fix. However at this time I have no idea of when a fix or work around will be available.

I will update you once I have further details.

Best Regards,

*engineer*

VMware Technical Support

Sounds to me that the resolution may well be in the next client release first.....

Damian Davis

[damiandavis]

Hmm,

Just tested the VI Client 5 with ESXi 5 and vCenter Server 5

specific error has gone in respect to DNS, however guest console is not displayed still - black screen ....

I'll test some more....

[tom_bauer]

FYI - it looks like vSphere client 5 update 1 has solved our black screen issues with direct access.