<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: VMware VIC 2.5 and Server 2.0 Beta 1</title>
	<atom:link href="http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1/feed" rel="self" type="application/rss+xml" />
	<link>http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1</link>
	<description>Adam Bell on Deployment, Automation, PowerShell et al</description>
	<lastBuildDate>Thu, 25 Feb 2010 23:14:19 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mukesh</title>
		<link>http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1/comment-page-1#comment-1022</link>
		<dc:creator>mukesh</dc:creator>
		<pubDate>Wed, 25 Mar 2009 09:35:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1#comment-1022</guid>
		<description>VMware Infrastructure Client could not establish initial connection with server &quot;VC server&quot; Details: The server could not interpret the communication from the client</description>
		<content:encoded><![CDATA[<p>VMware Infrastructure Client could not establish initial connection with server &#8220;VC server&#8221; Details: The server could not interpret the communication from the client</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will</title>
		<link>http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1/comment-page-1#comment-739</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Wed, 22 Oct 2008 22:55:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1#comment-739</guid>
		<description>Alternatively, you can reconfigure VMware to use port 902 for remote administration with http on 80, https on 443.  

Then you can use the VI Client without having to add a specific port.</description>
		<content:encoded><![CDATA[<p>Alternatively, you can reconfigure VMware to use port 902 for remote administration with http on 80, https on 443.  </p>
<p>Then you can use the VI Client without having to add a specific port.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davide77</title>
		<link>http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1/comment-page-1#comment-735</link>
		<dc:creator>davide77</dc:creator>
		<pubDate>Mon, 06 Oct 2008 10:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1#comment-735</guid>
		<description>Hi Adam,

I found THE SOLUTION! :D

To connect with vic to vmware server 2.0 you need to add the :8333 to the hostname, so the magic is, for example, 192.168.1.10:8333 and the connection works.

Best regards,
Davide</description>
		<content:encoded><![CDATA[<p>Hi Adam,</p>
<p>I found THE SOLUTION! :D</p>
<p>To connect with vic to vmware server 2.0 you need to add the :8333 to the hostname, so the magic is, for example, 192.168.1.10:8333 and the connection works.</p>
<p>Best regards,<br />
Davide</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Bell</title>
		<link>http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1/comment-page-1#comment-720</link>
		<dc:creator>Adam Bell</dc:creator>
		<pubDate>Mon, 15 Sep 2008 03:56:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1#comment-720</guid>
		<description>Hi R,

Tbh after the hassles that I had with Server 2.0 I switched to the 6.5 Workstation beta.

I&#039;ve always preferred the Snapshot Manager available in workstation too, but Server is free, so it&#039;s always handy to play with ....

Hope you found a solution to your problem!

Cheers,
Adam</description>
		<content:encoded><![CDATA[<p>Hi R,</p>
<p>Tbh after the hassles that I had with Server 2.0 I switched to the 6.5 Workstation beta.</p>
<p>I&#8217;ve always preferred the Snapshot Manager available in workstation too, but Server is free, so it&#8217;s always handy to play with &#8230;.</p>
<p>Hope you found a solution to your problem!</p>
<p>Cheers,<br />
Adam</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: r</title>
		<link>http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1/comment-page-1#comment-713</link>
		<dc:creator>r</dc:creator>
		<pubDate>Sat, 06 Sep 2008 00:25:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1#comment-713</guid>
		<description>Is there any way to change and forward this port?  Used to be able to in 1.0.......</description>
		<content:encoded><![CDATA[<p>Is there any way to change and forward this port?  Used to be able to in 1.0&#8230;&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: staticsirupflo</title>
		<link>http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1/comment-page-1#comment-615</link>
		<dc:creator>staticsirupflo</dc:creator>
		<pubDate>Mon, 14 Apr 2008 10:46:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1#comment-615</guid>
		<description>Hey,

it&#039;s definitely the SSL port (e.g. 443) to connect to. Thanks to Chrissy!</description>
		<content:encoded><![CDATA[<p>Hey,</p>
<p>it&#8217;s definitely the SSL port (e.g. 443) to connect to. Thanks to Chrissy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chrissy</title>
		<link>http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1/comment-page-1#comment-566</link>
		<dc:creator>Chrissy</dc:creator>
		<pubDate>Sat, 19 Jan 2008 01:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1#comment-566</guid>
		<description>Just as an FYI, I just did a netstat and I&#039;m connected to the VMWare server from my workstation on port 443 a few times and 902 once. When I loaded up https://myserver, it redirected me to /ui/ then said service unavailable. So perhaps VIC does use port 443 still.</description>
		<content:encoded><![CDATA[<p>Just as an FYI, I just did a netstat and I&#8217;m connected to the VMWare server from my workstation on port 443 a few times and 902 once. When I loaded up <a href="https://myserver" rel="nofollow">https://myserver</a>, it redirected me to /ui/ then said service unavailable. So perhaps VIC does use port 443 still.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chrissy</title>
		<link>http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1/comment-page-1#comment-565</link>
		<dc:creator>Chrissy</dc:creator>
		<pubDate>Sat, 19 Jan 2008 01:15:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.leadfollowmove.com/archives/virtualisation/vic-25-and-server-20-beta-1#comment-565</guid>
		<description>Hey Adam,
I believe that the port is on 902, at least it is on the Linux version. I hope it would be the same on Windows! Not sure how that will help, though..since the firewall is disabled on both. I&#039;ve not run VMware Server 2 on Windows but the Web interface seems just as horrible as it is in Linux, eh?

Good luck!</description>
		<content:encoded><![CDATA[<p>Hey Adam,<br />
I believe that the port is on 902, at least it is on the Linux version. I hope it would be the same on Windows! Not sure how that will help, though..since the firewall is disabled on both. I&#8217;ve not run VMware Server 2 on Windows but the Web interface seems just as horrible as it is in Linux, eh?</p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
