vSphere Web Access

[steveharder]

Hi,

for some reason standard users are able to enter the web access and see the vm machines I gave them permissions on but the remote console is not working for them.

Of course if I give them admin rights on the vcenter server they can work with the remote console but then they can do more then they should.

I gave them the role of administrator but nothing unless I add them to the admin group of the vcenter server itself.

This is the error -

Cannot access virtual machine console. The request timed out. Try Again CloseThe attempt to acquire a valid session ticket for "Linux-Jboss" took longer than expected. If this problem persists, contact your system administrator.

[byoung111]

We ran into the same problem yesterday.

We gave the user Virtual Machine user rights on the vcenter server, did not propagate the permission, then gave them Virtual Machine User rights on the VM's we wanted them to use. Then they were able to logon to web access and access the VM's console without having any extra access. I'm guessing this is a bug in the permissions setup as I haven't found anything regarding changes to permissions on an object.

[ESXDevil]

Hi

We have the same problem. Your workaround has solved the issue.

Thanks

ESXDevil

[PaulB2]

Cannot access virtual machine console. The request timed out.

The attempt to aquire a valid session ticket for "servername" took longer than expected.

This worked for me also. Solution was hard to find.

pb

[dear123]

Hi steve,

Can you assign a non-root user with the following permission and try:

Virtual Machine -> Interaction

Please let us know the outcome

[exawatt]

Thanks for the post. I have been trying to figure it out since yesterday.

[mudha]

restart the web access service from esx host

[Box293]

byoung111,

Your work around also fixed my problem however I had these additional problems that I thought were worth noting:

• Our domain uses Active Directory List Object Mode. This is because we have a hosted AD environment for all of our customers. This meant that:

• vCenter services need to be set to run with an AD account

• This AD account needs to be setup to be able to read all objects that are "list restricted"

• When adding groups to the top level without propagating I found I needed to restart vCenter services to enforce/make it work. User accounts seemed to work immediately.

VCP3 32846

VSP4 VML-306798

[ealaqqad]

Hi All,

I know this post is old, but as my customers still facing it on daily basis I believe many of you will.

Its worth mentioning that this issue was totally resolved in ESX 4U1, though for those who can't update there is a work around.

I have already documented this error, cause & different type of resolutions for it on the following post:

When trying to access virtual machine using web access you get “Cannot access virtual machine consol...

I hope this help some one, if it does please reward points.

Enjoy,

Eiad Al-Aqqad

System X & Storage Technical Specialist

Founder of http://www.VirtualizationTeam.com

Founder of http://www.TSMGuru.com