Did you ever find the answer you were looking for? I have this exact same issue. Like you I have checked A record, tried both using the host IP and hostname with no luck.

Thanks for the reply

I have tried the following:

hostname.example.com

hostname

IP Address

None of these have produced a successful login for some reason.

Did you try this? kb.vmware.com/kb/1029531 

EricBates wrote:

 

I have successfully joined ESXi to my domain.

 

I can successfully login to ESXi with vSphere Client if I spell the username out: domain\user and explicitly supply the password.

 

I cannot login using the convenient "Use Windows session credentials" check-box. I get the error:

Windows session credentials cannot be used to log into this server. Enter a username and password.

 

The knowledgebase article: Logging on to an ESX host with Windows session credentials fails does not seem to apply because I double checked both the A record and the PTR record for the server from the client machine and they all resolve correctly.

 

During an attempt, /var/log/messages only reports:

Jan 31 23:36:30 Hostd: [2011-01-31 23:36:30.862 4028AB90 verbose 'Proxysvc Req03376'] New proxy client SSL(TCP(local=172.25.33.69:4379, peer=172.25.33.240:443))
Jan 31 23:36:40 Hostd: [2011-01-31 23:36:40.690 4028AB90 verbose 'HTTP server'] Sent response for HEAD /client/clients.xml (from /usr/lib/vmware/hostd/docroot)
Jan 31 23:36:48 Hostd: [2011-01-31 23:36:48.453 3FF81B90 verbose 'Proxysvc Req03377'] New proxy client SSL(TCP(local=172.25.33.69:4380, peer=172.25.33.240:443))
Jan 31 23:36:48 Hostd: [2011-01-31 23:36:48.685 3F1D2B90 verbose 'Proxysvc Req03378'] New proxy client SSL(TCP(local=172.25.33.69:4381, peer=172.25.33.240:443))
Jan 31 23:36:51 Hostd: [2011-01-31 23:36:51.712 3F1D2B90 verbose 'Proxysvc Req03379'] New proxy client SSL(TCP(local=172.25.33.69:4382, peer=172.25.33.240:443))
Jan 31 23:36:51 Hostd: [2011-01-31 23:36:51.716 FFEC0B90 verbose 'HTTP server'] Sent response for HEAD /client/clients.xml (from /usr/lib/vmware/hostd/docroot)

I don't really see anything in there that helps me understand. 172.25.33.69 is the client and 172.25.33.240 is the ESXi server.

 

I know this is just a nicety; but anyone have any thots?

 

Thanks.

Hi if able to ping domin try diffrent way of login

1-\\domain \username

2-usernam@domin.com

3-only user & password

_________________________________

Good luck!

This is the answer to your query. Don't forget to give feedack , which help to others.

Don't know if anyone is still having this issue, but here is my scenario, and what I found...

I have my ESXi machine joined to my domain: DOMAINA.COM

Domain A has a trust with Domain B, Domain C and Domain D

I can log into the ESXi box manually with any credentials from any of those domains

When I run the client as a user from DOMAIN A, the checkbox works just fine.

If I run it as a user from any of the other 3 domains, it fails.

So, I think it is something to do with the way that the domain trust works, and how the credentials are passed into the client login screen.

Hope this helps someone...

JP

my experience for esx 4.1:

- I had forgotten that I had put the domain name in domain box in "Configuration" -> "DNS and Routing" to same as name of the esx server

- The reason why I did that was the box would not let me NOT specify domain name after I changed the machine name.

- Funny thing it let me join esx to domain; I could even log in using domain user\password. But when I tried with VI client "Windows session credentials cannot be used to log into this server".

- I tried everything NTP, PTR \ A records, DNS entries nothing worked.

- Finally I removed esx from domain.

- changed the domain name in the "DNS and Routing" box to the domain name I wanted esx to join

- joined the domain again and hurrrray!

Of course this is my mistake but I would have thought I would see that kind of errors..

- V