Comments on: Use Infrastructure Client to manage VMware Server

By: Derek Shaw

Derek Shaw — Fri, 16 Jul 2010 01:32:23 +0000

vmware infrastructure client could not establish a connection with server "192.168.254.99″. Details: The server closed the connection.

– never mind!
– re-read the (correct) log and noticed the 'App' service was reporting problems with the /usr/lib/vmware/settings.

By: Derek Shaw

Derek Shaw — Fri, 16 Jul 2010 01:12:18 +0000

vmware infrastructure client could not establish a connection with server "192.168.254.99″. Details: The server closed the connection.

By: Richie Cunningham

Richie Cunningham — Fri, 04 Jun 2010 00:43:11 +0000

Thank you for your post. In the back of my mind I wondered. Your post gave me the motivation I needed! ip:8333 worked for me.

By: Gleb Reys

Gleb Reys — Wed, 24 Mar 2010 11:13:14 +0000

Thanks so much for your comment, Glen – fixed

By: Glen Pyle

Glen Pyle — Sun, 14 Mar 2010 15:22:56 +0000

Irregardless is not a word, thanks for the great tip!

By: muchas

muchas — Thu, 17 Dec 2009 12:17:59 +0000

Muchas gracias!

By: seven

seven — Tue, 15 Dec 2009 10:44:08 +0000

hi,
Can you tell more about security and comfortable in that solution vs web interface (use https)

By: VI Client and VMware Server | From thoughts to text

VI Client and VMware Server | From thoughts to text — Fri, 16 Oct 2009 18:31:32 +0000

[...] a nice tip for using VMwares Infrastructure Client to manage VMware Server, a product which is usually managed via web interface. The tip is to simply add the port number of [...]

By: Clayton

Clayton — Fri, 04 Sep 2009 13:54:32 +0000

This didn't work for me, so I tried https://server:8333 instead of just server:8333 and it worked. Thanks!

By: Gleb Reys

Gleb Reys — Sat, 09 May 2009 00:46:14 +0000

Hi Catemaco,

I haven't used VMware Converter lately so wouldn't know the answer yet, but see no reason why this would be impossible. A VMware Server host is nothing but a Windows or Linux OS, so it should be easily convertable.