Excessively (unuseably) slow remote console connection

[OuttaCyTE]

Hi all, I'm desperate for a solution to this problem.

I have a very nice machine running two guests and the guests are running fantastic. The host is a Dell 2950 with 12 GB ram running two guests. One is Win Server 2008 R2 and the other is Win Server 2003 R2. Each has 4 GB ram and two processors. The performance tools show nothing obvious and as I say, the machines themselves are performing great.

I can remote to them via RDP and my performance is fantastic.

However, when I open vSphere, direct it to my ESXi 4 host and then tell it to open the console of the same guest, I can't hardly move the mouse. 10 seconds per inch movement speed. or pressing enter takes 5 seconds just for the box to depress, much less do anything.

What is wrong here and what can I do about it? It's HORRIBLE. It's so bad, it's quicker for me to release via Ctl-Alt, move the mouse over the spot I'm interested in, click once and wait while mouse positions, then click again. This way it only takes me about 4 seconds per click.

Yes, I have VMTools installed and Full hardware acceleration is set. The Adapter Type shows Standard VGA Graphics Adaper and the Chip Type shows "V M ware, Inc. VBE support 2.0" with 8MB graphics memory. Resolution is set to 1024 x768. 32 bit color.

I have a VPN between me and the host and as I say, RDP is blazingly fast over the connection while the vSphere remote console is glacially slow!

I have resorted to RDP into my guest, then install vSphere on the guest, then run the remote console from the guest and that performance is ok (still not good, still jerky, but useable). That works ok until I need to manipulate the console for the guest I am using to RDP. I can't be signed on to the console at the same time I'm signed on via RDP.

I see lots and lots and lots of complaint in this area, but I see zippo in solutions.

Is any kind sole willing to help me out here? I'm so frustrated I've ended up screaming at my monitor!

This is no way to operate and I really need some help here.

I really (really, REALLY) want this (VMware) to work.

-greg

[OuttaCyTE]

Er, Kind SOUL... Not kind sole !

[DSTAVERT]

There is far too much going on in the client for it to be useful across a VPN tunnel. Set up a workstation specifically for managing the host remotely and then RDP to that. You won't find a satisfactory answer for this using a wan link and or vpn with the vSphere client.

[OuttaCyTE]

Well,

I guess it's helpful and I really appreciate the response.

Basically it's just not going to work and not a setting or configuration problem.

The problem with the whole set up a physical thing is that the site is going to be lights out & unattended. I was hoping to be able to run all of my systems at the site as guests and be able to use the console for interaction when I needed.

Shucks,

-g

[DSTAVERT]

When operated that way I would absolutely set up a dedicated workstation. An old laptop or small atom based pc. You could also look at an IP KVM switch. Add a remote power switch. I don't know what your host hardware is but if you have a baseboard controller (ILO for HP, DRAC in Dell, BMC in IBM) you can usually get remote console access and power control.

[OuttaCyTE]

David, Thank you very much for your response.

I have been looking at the DRAC for the server to get the console of the VM Host but there's not much there with ESXi. I've also been looking at a remote accessible switched power unit (more than just the Dell there).

Didn't want to put another piece of equipment in the mix, but it looks like I might have to.

Thank you again,

-greg

[DSTAVERT]

I don't use Dell but with HP the ILO access gives me power control as well as console and various under neath access to disks and controllers (SNMP). Console can give you access to the unsupported console and the command line. A IP KVM switch would give you access to both management machine and ESXi. I manage everything I have through a several WAN links and very rarely need to visit the equipment. Needing to powercycle once at 3AM will make it all clear.

[OuttaCyTE]

The client can't afford much at this new location curerntly. Just setting up their first remote location has had several hidden costs and we're not likely to get more $$ for equipment at this point (despite my wanting it - perhaps later). I'll see if I can scratch up a laptop that I can use for RDP. Power switching will have to be manual at first, fortunately there are some of the staff who can be trusted to do that if/when necessary.

-g