vmware server 2.0 in intrepid ibex

[SpUpUz]

vmware server 2.0 console keaybord not working!!

all works cool except the keybords on virtual machine console, for example direction key are not mapped correctly.

[Delvien]

Originally Posted by SpUpUz vmware server 2.0 console keaybord not working!! all works cool except the keybords on virtual machine console, for example direction key are not mapped correctly.

Couldn't get mine to configure.

[SpUpUz]

Originally Posted by Delvien Couldn't get mine to configure.

what do you mean?

[Delvien]

Originally Posted by SpUpUz what do you mean?

Theres... no other way to say it... vmware wont configure for me

[SpUpUz]

Originally Posted by Delvien Theres... no other way to say it... vmware wont configure for me

for me eveything seems ok but going in console for the up arrow key it corresponds the "*" and also for down arrow, so i can't use ctrl alt del and cant select a diffrent hardware profile in my windows box

[SpUpUz]

any other one as tested this environment

[SpUpUz]

ok tested the same environment at home and as a result i have got the same issue arrow key are not usable!! and can't login correclty!

[jms-ubuntu-en]

My problem is that I can't log in to virtual machine (xp) because I can't enter ctrl-alt-del. Ctrl-alt is reserved for remote console's "Release Input"
Any suggestions?

[dabl]

I'm not sure about VMware server, but there's a new VMware Player, ver. 2.5, which installs on the 2.6.27-5 kernel with no problem. 2.0.5 won't configure on kernels after 2.5.26, AFAIK.

http://www.vmware.com/download/player/

However, after setting up my Win XP VM, it also exhibits a keyboard problem -- the arrow keys don't function. All other keys appear to work correctly. The same VM works perfectly on 2.0.5, which is running on a 2.6.25 kernel. The keyboard and driver is the same in Windows device manager. The mouse works correctly.

[jms-ubuntu-en]

I just remembered that I had enabled RDP in my virtual XP. So I created new port forwarding rule to /etc/vmware/vmnet8/nat/nat.conf

# RDP
2289 = 192.168.65.128:3389

After restarting vmware service it was possible to use tsclient to connect localhost:2289