<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>LAMP with ·dotmanila &#187; Virtualization</title>
	<atom:link href="http://dotmanila.com/blog/category/virtualization/feed/" rel="self" type="application/rss+xml" />
	<link>http://dotmanila.com/blog</link>
	<description>Linux, Apache, PHP, MySQL Musings</description>
	<lastBuildDate>Wed, 01 Feb 2012 23:32:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>VMWare: Windows 2003 Host, CentOS 5 Guest &#8211; Bridged Networking</title>
		<link>http://dotmanila.com/blog/2009/10/vmware-windows-2003-host-centos-5-guest-bridged-networking/</link>
		<comments>http://dotmanila.com/blog/2009/10/vmware-windows-2003-host-centos-5-guest-bridged-networking/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 18:17:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[static IP]]></category>
		<category><![CDATA[vmware bridging]]></category>
		<category><![CDATA[vmware windows host + linux guest]]></category>

		<guid isPermaLink="false">http://dotmanila.com/blog/?p=96</guid>
		<description><![CDATA[We would usually just setup a NAT based VM appliance for any new requirement. Most of the time, access is limited to ones desktops. When the need arise for a shared Linux VM on our local Windows 2003 server, the inexperienced may find it trouble setting up the CentOS guest as a reachable application server [...]]]></description>
			<content:encoded><![CDATA[<p>We would usually just setup a NAT based VM appliance for any new requirement. Most of the time, access is limited to ones desktops. When the need arise for a shared Linux VM on our local Windows 2003 server, the inexperienced may find it trouble setting up the CentOS guest as a reachable application server just like its host OS.</p>
<p>To achieve this, make sure the following items a re true:</p>
<ul>
<li>HOST » VMWare » Edit » Virtual Network Editor</li>
</ul>
<blockquote>
<ol>
<li>Automatic Bridging &#8211; &#8220;Automatically choose an available physical network adapter to bridge to VMNet0&#8243; is UNCHECKED</li>
<li>Host Virtual Network Mapping &#8211; VMNet0 is mapped to you chosen physical adapter, NOT automatically.</li>
<li>You can disable NAT, DHCP and Host Virtual Network Adapters</li>
</ol>
</blockquote>
<ul>
<li>HOST » Control Panel » Network Connections</li>
</ul>
<blockquote>
<ol>
<li>Right click your chosen physical adapter, then Properties. Make sure &#8220;VMWare Bridge Protocol&#8221; is CHECKED.</li>
</ol>
</blockquote>
<ul>
<li>GUEST &#8211; Assign an unused static IP, the same network/netmask and gateway that is used on your host&#8217;s physical adapter.</li>
</ul>
<p>Other items worth checking when inbound and outbound connections from the guest OS:</p>
<ul>
<li>Host firewall</li>
<li>Guest DNS server settings, resolv.conf.</li>
</ul>
<p>This checklist should get you up and running with a virtualized development platform with the same network visibility as a physical machine in your office.</p>
]]></content:encoded>
			<wfw:commentRss>http://dotmanila.com/blog/2009/10/vmware-windows-2003-host-centos-5-guest-bridged-networking/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
	</channel>
</rss>

