VMware Cloud Community
billz0r
Contributor
Contributor

Blank console in VIClient and error in web view

Hi,

We have 1 ESX 3.5 server but can't view any of the consoles of the VM's running inside it. There is no firewalls or natting going on. I can telnet to port 902 and 903 ok. It's the same fault from all PC's and servers on our network. I've been through the KB article 749640 and everythig checks out fine there. I have tried accessing the ESX Host using IP and hostname. All PC's and servers are on the same subnet as the service console. I added a new service console to a 2nd NIC and tried in via that way with the same result. The VM's are a mixture of MS and Linux boxes, some with and some without VMTools. If I create a new VM I can't see the BIOS screen either. This means we can't create any new VM's either as I can't see anything on the screen.

When I access any console via the web page view I get an error "The following errors occured while processing your request: A general system error occurred: Internal error"

It worked about 3 weeks ago and can't think of any changes that have occurred since.

I've googled till I'm blue in the face but keep turning up just network and nat related issues.

Daniel

Tags (2)
0 Kudos
7 Replies
AndreTheGiant
Immortal
Immortal

You have the same problem both with VIC and Web Console?

Also on a new VM?

Have you tried to restart the hostd service?

/etc/init.d/mgmt-vmware restart

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
billz0r
Contributor
Contributor

Yes, same on both VIC and Web and with a new VM.

Yes I have tried that command.

I've also done a full reboot of the VM Host just to be sure.

0 Kudos
AndreTheGiant
Immortal
Immortal

Could be a firewall problem (maybe also a personal firewall).

Which client are you using?

For connect to your ESX are you using a FQDN or a IP?

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
billz0r
Contributor
Contributor

It's VIC 2.5 currently. I've also tried the newer VSphere 4 VIC with same results.

We don't run any firewall software and I've disabled the XP firewall.

I've connected to the ESX host using IP and hosname. I've also tried through VCenter using IP and hostname with no change.

0 Kudos
AndreTheGiant
Immortal
Immortal

Have you also tried from a "clean" PC?

Install the client from http://ESX_IP/

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
billz0r
Contributor
Contributor

As a matter of fact I have a fresh load on a laptop right in front of me so I'll try it. I doubt it will work though as I have tried this from my PC (XP Pro), the directors PC (XP Pro), Server 2008, SBS 2003 and Server 2003.

Update: No difference, still buggered. It's gotta be a server thing rather than a client thing.

Any1 else out there have any ideas? I also had 1 of our other admins try from his PC with the same thing.

0 Kudos
billz0r
Contributor
Contributor

I ended up fixing this but unsure how.

I found out our ESX 3.5 host had never been patched so I d/led Update 4 and started shutting down VM's put the machine into maintanence mode. I had 1 more VM to go when I thought I'd look at the console 1 last time and what do ya know, it was there. Looks like 1 of the VM's was somehow stopping the console working for all oher VM's. I ended up doing my Update 4 upgrade and starting 1 VM back up at a time and all is still well. I've even loaded 2 more new VM's from the console (1 was 2008 and 1 was Linux) and works perfectly. Go figure.

0 Kudos