<?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 Fusion and network bridging</title>
	<atom:link href="http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/</link>
	<description>All my stuff in one place</description>
	<lastBuildDate>Fri, 12 Mar 2010 12:36:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: VMWare Fusion &#8211; Network Bridge error finally solved &#124; Ian McShane</title>
		<link>http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/comment-page-2/#comment-978</link>
		<dc:creator>VMWare Fusion &#8211; Network Bridge error finally solved &#124; Ian McShane</dc:creator>
		<pubDate>Fri, 12 Mar 2010 12:34:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/#comment-978</guid>
		<description>[...] couple of years back, I posted this thread about an annoying problem in VMWare Fusion which occasionally stopped me from being able to run an image as in bridge [...]</description>
		<content:encoded><![CDATA[<p>[...] couple of years back, I posted this thread about an annoying problem in VMWare Fusion which occasionally stopped me from being able to run an image as in bridge [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn&#8217;s blog &#187; VMWare fusion bridged network issue :(</title>
		<link>http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/comment-page-2/#comment-378</link>
		<dc:creator>Shawn&#8217;s blog &#187; VMWare fusion bridged network issue :(</dc:creator>
		<pubDate>Fri, 15 Jan 2010 06:43:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/#comment-378</guid>
		<description>[...] Thanks google and credit to this blog owner: http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Thanks google and credit to this blog owner: <a href="http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/" rel="nofollow">http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ammoun</title>
		<link>http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/comment-page-2/#comment-377</link>
		<dc:creator>ammoun</dc:creator>
		<pubDate>Tue, 17 Nov 2009 23:17:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/#comment-377</guid>
		<description>My final comment and the resolution of my problem; as explained to me by the VMware support (very good people indeed); NAT networks use virtual IP addresses assigned by the virtual machine&#039;s DHCP not by the router and hence the virtual machine is not given an IP in the physical local network which explains why NAT networks do not &quot;see&quot; network printers and other computers on the physical network (router and devices connected to it), it only connects to the internet through the NAT (and router) and connects to the MAC of course.
Bridged networks, however, obtain an address from the DHCP of the router and are, therefore, part of the physical network and hence can &quot;see&quot; the local network devices and other computers connected to the router and are on the network along with the MAC of course.
The above has been the case since I changed my router and so I am now OK. Support tells me that some routers act weird and for some reason refuse to assign IPs to some computers on the network and this is documented with several models out there. So, if your computer is not able to get an IP from the router or the router is failing to act as a DNS for your network in Bridged network configuration, then try another router before anything else.
I hope this is useful to someone.
Good luck to all and God bless.</description>
		<content:encoded><![CDATA[<p>My final comment and the resolution of my problem; as explained to me by the VMware support (very good people indeed); NAT networks use virtual IP addresses assigned by the virtual machine&#8217;s DHCP not by the router and hence the virtual machine is not given an IP in the physical local network which explains why NAT networks do not &#8220;see&#8221; network printers and other computers on the physical network (router and devices connected to it), it only connects to the internet through the NAT (and router) and connects to the MAC of course.<br />
Bridged networks, however, obtain an address from the DHCP of the router and are, therefore, part of the physical network and hence can &#8220;see&#8221; the local network devices and other computers connected to the router and are on the network along with the MAC of course.<br />
The above has been the case since I changed my router and so I am now OK. Support tells me that some routers act weird and for some reason refuse to assign IPs to some computers on the network and this is documented with several models out there. So, if your computer is not able to get an IP from the router or the router is failing to act as a DNS for your network in Bridged network configuration, then try another router before anything else.<br />
I hope this is useful to someone.<br />
Good luck to all and God bless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ammoun</title>
		<link>http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/comment-page-2/#comment-376</link>
		<dc:creator>ammoun</dc:creator>
		<pubDate>Tue, 17 Nov 2009 14:11:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/#comment-376</guid>
		<description>I am sorry, I rushed my comment! I restarted and found out my NAT network does not &quot;see&quot; my printer or other computers on my local network! We are back to square one with no help from VMware or Microsoft!</description>
		<content:encoded><![CDATA[<p>I am sorry, I rushed my comment! I restarted and found out my NAT network does not &#8220;see&#8221; my printer or other computers on my local network! We are back to square one with no help from VMware or Microsoft!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ammoun</title>
		<link>http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/comment-page-2/#comment-375</link>
		<dc:creator>ammoun</dc:creator>
		<pubDate>Tue, 17 Nov 2009 13:54:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/#comment-375</guid>
		<description>Guys,
I changed my router to Belkin N1 (from LiveBox that came with my ISP provider&#039;s subscription) and my NAT and BRIDGED networks both worked well!! It seems that neither VMware Fusion v3 nor Windows 7 are at fault, it was my router!! So please try to change your routers or fiddle with the settings!
Bless you all.</description>
		<content:encoded><![CDATA[<p>Guys,<br />
I changed my router to Belkin N1 (from LiveBox that came with my ISP provider&#8217;s subscription) and my NAT and BRIDGED networks both worked well!! It seems that neither VMware Fusion v3 nor Windows 7 are at fault, it was my router!! So please try to change your routers or fiddle with the settings!<br />
Bless you all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ammoun</title>
		<link>http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/comment-page-2/#comment-374</link>
		<dc:creator>ammoun</dc:creator>
		<pubDate>Wed, 11 Nov 2009 22:05:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/#comment-374</guid>
		<description>I just tried a fresh Win 7 installation with Parallels Desktop 5 and it is exactly the same problem as with VMware Fusion 3 with Win 7. So.... it seems that the problem is Win 7 (and Vista before it)! This is as far as my knowledge goes! Anyone with an answer?
Bless you all.</description>
		<content:encoded><![CDATA[<p>I just tried a fresh Win 7 installation with Parallels Desktop 5 and it is exactly the same problem as with VMware Fusion 3 with Win 7. So&#8230;. it seems that the problem is Win 7 (and Vista before it)! This is as far as my knowledge goes! Anyone with an answer?<br />
Bless you all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ammoun</title>
		<link>http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/comment-page-2/#comment-373</link>
		<dc:creator>ammoun</dc:creator>
		<pubDate>Tue, 10 Nov 2009 09:49:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/#comment-373</guid>
		<description>Just to confirm, if I set my own IP address, Gateway IP and DNS IP, my &quot;Bridged&quot; network adapter works fine and I can see my network printer ...etc. If I leave the IP to Automatic then I cannot see the printer, my &quot;Bridged&quot; network adapter setting does not connect to the internet, my &quot;NAT&quot; connects, however it fails to see local network, only the internet! This is weird and most definitely has to do with the VMware/Win 7 combo failing to obtain and IP address (register on the network) properly. Any suggestions from anyone? I do not wish to keep my IP set as I move from one WiFi network to another at different venues.</description>
		<content:encoded><![CDATA[<p>Just to confirm, if I set my own IP address, Gateway IP and DNS IP, my &#8220;Bridged&#8221; network adapter works fine and I can see my network printer &#8230;etc. If I leave the IP to Automatic then I cannot see the printer, my &#8220;Bridged&#8221; network adapter setting does not connect to the internet, my &#8220;NAT&#8221; connects, however it fails to see local network, only the internet! This is weird and most definitely has to do with the VMware/Win 7 combo failing to obtain and IP address (register on the network) properly. Any suggestions from anyone? I do not wish to keep my IP set as I move from one WiFi network to another at different venues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ammoun</title>
		<link>http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/comment-page-2/#comment-372</link>
		<dc:creator>Ammoun</dc:creator>
		<pubDate>Sun, 08 Nov 2009 23:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/#comment-372</guid>
		<description>Macca, I also ran Fusion 2 for 18 months without ever encountering the NAT/Bridged connection errors. However, I was running Win XP not Vista nor Win 7. With Win 7 and Fusion 2 I could connect only in NAT network type not Bridged, no matter what I did.
Now in Fusion 3 and Win 7 it is even worse, it is erratic and I cannot figure out what is happening! I only know it is a DHCP problem because when I use a VPN or set my own IP and specify the Gateway and DNS servers, I connect to the Internet with no problems as the VPN assigns me an IP and somehow things work fine.
As I am no expert in networking, Win 7 or Fusion I can only state my observations and hope they are of use to some guru out there who may come up with an answer for those of us suffering from this incompatibility or whatever you may call it.
I only wish I was as lucky as you with this issue.
Regards.</description>
		<content:encoded><![CDATA[<p>Macca, I also ran Fusion 2 for 18 months without ever encountering the NAT/Bridged connection errors. However, I was running Win XP not Vista nor Win 7. With Win 7 and Fusion 2 I could connect only in NAT network type not Bridged, no matter what I did.<br />
Now in Fusion 3 and Win 7 it is even worse, it is erratic and I cannot figure out what is happening! I only know it is a DHCP problem because when I use a VPN or set my own IP and specify the Gateway and DNS servers, I connect to the Internet with no problems as the VPN assigns me an IP and somehow things work fine.<br />
As I am no expert in networking, Win 7 or Fusion I can only state my observations and hope they are of use to some guru out there who may come up with an answer for those of us suffering from this incompatibility or whatever you may call it.<br />
I only wish I was as lucky as you with this issue.<br />
Regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Macca</title>
		<link>http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/comment-page-1/#comment-371</link>
		<dc:creator>Macca</dc:creator>
		<pubDate>Sun, 08 Nov 2009 21:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/#comment-371</guid>
		<description>@ammoun

For clarity, I&#039;m running Win7 in VMWare Fusion 3.0 and have no problems with DHCP allocation either from my DHCP server or from the VMNet process.
I was also running it upon Fusion 2.x for quite some time without this issue showing up again.</description>
		<content:encoded><![CDATA[<p>@ammoun</p>
<p>For clarity, I&#8217;m running Win7 in VMWare Fusion 3.0 and have no problems with DHCP allocation either from my DHCP server or from the VMNet process.<br />
I was also running it upon Fusion 2.x for quite some time without this issue showing up again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ammoun</title>
		<link>http://www.ianmcshane.org/2007/12/13/vmware-fusion-and-network-bridging/comment-page-1/#comment-370</link>
		<dc:creator>ammoun</dc:creator>
		<pubDate>Sun, 08 Nov 2009 02:18:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.maccarocks.com/2007/12/13/vmware-fusion-and-network-bridging/#comment-370</guid>
		<description>Guys, try setting an IP address in the IPv4 of your local area network using the router info for gateway and DNS. I did that and I am able to work with the &quot;Bridged&quot; network setting just fine. I believe there is something wrong with VMware 3 and Win 7 not obtaining an IP from the router when selecting a &quot;Bridged&quot; network type. Even NAT type was not working until I used the terminal instruction above. I hope someone can make use of this info and let us know how to fix this once and for all. I can&#039;t believe VMware did not test this basic interaction with of their software with Win 7???</description>
		<content:encoded><![CDATA[<p>Guys, try setting an IP address in the IPv4 of your local area network using the router info for gateway and DNS. I did that and I am able to work with the &#8220;Bridged&#8221; network setting just fine. I believe there is something wrong with VMware 3 and Win 7 not obtaining an IP from the router when selecting a &#8220;Bridged&#8221; network type. Even NAT type was not working until I used the terminal instruction above. I hope someone can make use of this info and let us know how to fix this once and for all. I can&#8217;t believe VMware did not test this basic interaction with of their software with Win 7???</p>
]]></content:encoded>
	</item>
</channel>
</rss>
