The following problem only occurs with one of my servers.
When I press "Open Console" (in Virtual Infrastructure client 2.0.2) to open the server console it takes about 30 seconds before it opens the console window. During the 30 seconds my vi client and the server freeze.

Tried reinstalling the vmtools but no change. The server works fine and this problem does not occur on with other servers.

Does anybody have a clue what happening and how I could possibly solve this?

Thanks.

What do you mean with server? Do you mean it only happens with a certain VM (guest) or only on a certain ESX Server (host)?

What OSes are you running in your VMs?

Are you using Virtual Center?

Do the versions of the VI Client, Virtual Center and the ESX Hosts match?

Sorry about that, here are some more details.

With server, I mean: one VM (Guest), so no problem on the ESX host.
All VM's are running Windows Server 2003 + sp2 and patches.

We are using Virtual Center and the versions match. Version 2.0.2, Build 50618

I haven't seen this issue, and don't know the solution, but I've got some more questions.

Did you try to reboot the VM?

Are you running anything peculiar in the service console, eg. back-up agents?

BTW: My VI Client and Virtual Center server report Version 2.0.2, Build 62327...

I tried a reboot of the VM but no change, also tried removing and then reinstalling the VMtools but again no luck.

There's also nothing peculiar or out of the ordinairy running on the vm.

btw. we're running ESX 3.0.x and Virtual Center 2.0.2 can I upgrade Virtual Center to 2.5 or would I then also need to upgrade the ESX server to 3.5?

For the reboot of the VM, did you completely power off the VM or did you just do a Restart from Windows? In the last case, try completely shutting down the VM.

You can upgrade to VC 2.5, but if you don't plan to upgrade your ESX Hosts, I don't think you will gain anything by doing so.

I'm fairly sure I tried both a restart and a power off... but I'll give it another go this weekend now that I've reinstalled the vmtools.

Did the reboot help?

I did a power off rather then a warm reboot.
But it didn't help.

problem is still there