After upgrading to firefox 3.6 I can't open up my virtual machine through the browser.
I downgraded to 3.5 and it worked.
This is the message I get:
Cannot access virtual machine console. The request timed out
The attempt to acquire a valid session ticket for * took longer than expected. If this problem persists, contact your system administrator.
Anyone know how to fix this?
You should read supported host OS on specifications. Vmware supports only legacy OS and their browsers. Vmware Server does not work at all with lates stable kernels etc... So this issue may be solved in next release of vmware Server 2.0.x when ever it will be out... Vmware can do a lot of good work, but they have a lot of problems to support latest stable releases of OS's, kernels and browsers. So - you should use Win2000 and IE 6.0 and it might work or Suse 9.0.
Me too.
I'm seeing the same issue. Access to localhost:8222 works, but attempts to bind to a running Guest OS give the error message: "The
attempt to acquire a valid session ticket for "XP Pro Services Image"
took longer than expected. If this problem persists, contact your system
administrator." Access to https://localhost:8333 do not work. In the/var/log/vmware/hostd.log file, the log entries read: "'Proxysvc' ........ warning] SSL Handshake on client connection failed: SSL Exception:" for every attempt to access the web page on 8333.
In my case running on Gentoo Linux 2.6.30-r6, x86 32-bit system. Firefox 3.6...
As for waiting for another release from VMware, I grow old and tired of waiting. Considering making the shift elsewhere, if there is not a quick resolution to this issue.
Same issue here since the latest Firefox update. Disabled all add-on with no change.
I got this problem on FF 3.6 also, the only work-around way is downgrade to FF 3.5.x. I really hope VMWare to provide an updated FF Add-On to us ASAP. Does anyone know the best way to push VMWare development team to do so?
Same problem, management and console not working with Firefox 3.6 while still working on machines with 3.5.x.
Other workaround, start-stop Guest with command lines on Windows or Linux ![]()
A first step you can take is, to activate ssl2 in firefox:
Open about:config
-> security.enable.ssl2 from false to true
Thus we could use the Webinterface again, but not the Console Plugin.
I am having the same problem.
I have the same problem, but it work ok in IE or Maxthon etc.
hope new release.
I am having the same problem. It works in IE8 and it worked in FF 3.5.7. It doesn't in FF3.6. Having the same error message.
I am using IE for the moment to access my vm's but would go back to FF as soon as this is fixed.
I have the same problem, that vmware and FF 3.6 do not co-operate.
Solution: Download VMWare-Player 3.0 and use it instead of vmware.
Once VMWare-Player 3.0 is installed all vmware, vmware-config.pl scripts are replaced by vmplayer.
So far it works quite nicely.
Good luck
Johannes.
Did you download VMware Player to the Host or to another PC?
Normally you don't access the Webfrontend from the host, but rather from another PC.
Sorry, I have a very simple setup. A PC with Linux OS and Windows running on a VM. So far, I accessed the VM through the firefox plug-in which was called automatically by 'vmware'. This doesn't work anymore, which is the reason for this thread. On workaround for such a simple setup is provided by the VMPlayer. It allows to open the VM independently of firefox.
However, if it is possible to access the vmdisk-file through the network, then it is still possible to use VMPlayer. One should install it on the remote computer and tell the Player, where to find the vmdisk-file.
OK, this doesn't work for us. We're running our whole system with VMs and they must keep running, not stop, if I close the Player-Window ![]()
But thanks for testing with VMware Player, but this is probably the same like using the vmware-vmc.exe.
If i know the ID of the VM, I can access them over starting the vmware-vmc.exe with the VM-ID, this works, but this is a little circuitous
Obviously, development on a free product like VMware Server 2 is not going to keep up with the hundreds of new releases from software companies. They are focusing on maintaining their core competencies.
Anyone stating that "VMware should fix this or I will go elsewhere" needs to remember that this product is FREE. May I also remind you that ESXi can be had for FREE as well, and with that you get the Enterprise level Hypervisor and IMO much better setup.
So, here are options that I'm aware of for those with VMware Server 2 problems on Firefox 3.6:
Downgrade to Firefox 3.5.7 or earlier
Access using Internet Explorer
Install the VI Client (Virtual Infrastructure Client) and connect to the <IP_ADDRESS>:8333
Migrate to an Enterprise level setup using ESXi (available for free)
Again, VMware Server 2 is a free product, and it works well for what it is, but ESXi would definitely be something worth looking at for a production environment - free. Check it out.