nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

All VM Guest Console displays as blank

BroadcastStorm

Hi guys, I am trying to find out why one of our ESX Server 3i, 3.5.0 is not able to show GUI/Console of all VM Guests, we currently have 7 VM Guests hosted on this ESX server none of them displays the GUI/Console.

Thanks in advance for your help.

Find more posts tagged with

SAVE $250 on Your Boot Camp — Use Code "EXAM26"

Exclusively for TechExams members for Infosec Boot Camps starting before April 30, 2026

View Boot Camps

Comments

scott28tt

Try restarting the management agent components on the ESXi host.

Scott.

bertieb

and check any firewall ports between your client and that host are open appropriately, e.g. VMware KB: Cannot open Virtual Machine Console

scott28tt

I was going to suggest firewalls, but it seems to be an issue with one particular host if I read the initial post right...

Scott.

JDMurray

And make sure you have all of the latest fixes for 3.5.0 installed on that server.

BroadcastStorm

The issue is only on a particular workstation running windows 7 if I use the same Vsphere client to connect on a Windows XP to the esxi server it's working fine, there's not error message at all.

MentholMoose

Have you tried to uninstall and reinstall the client on the problematic machine?

scott28tt

BroadcastStorm wrote: »

The issue is only on a particular workstation running windows 7 if I use the same Vsphere client to connect on a Windows XP to the esxi server it's working fine, there's not error message at all.

Well that changes things a lot...

BroadcastStorm

The culprit was Windows 7 64 Bit I provisioned a VM Guest using VM Player using Win XP and it worked...

blargoe

I don't think VI client 3.5 is supported on Win 7.

JDMurray

blargoe wrote: »

I don't think VI client 3.5 is supported on Win 7.

He could retry running it in Windows XP compatibility mode--or just upgrade to 4.x.